ER/Studio - Embarcadero Technologies Product Documentation
ER/Studio - Embarcadero Technologies Product Documentation ER/Studio - Embarcadero Technologies Product Documentation
USING ER/STUDIO > COMMON TASKS Editing the Name of an Object On the Data Model Explorer or Data Model Window, double-click the object that you want to edit and then change the name of the object in the editor. TIP: Alternatively, shift-click the object to change and the object name becomes an editable field. Click Backspace to erase the name, enter a new name, and then click anywhere outside the object to effect the change. Deleting an Object 1 On the Data Model Explorer or Data Model Window, right-click the object to delete, and then click Delete from the shortcut menu. 2 Click Yes. Notes • When you right-click a submodel object, there is no Delete option. Instead, there is an option to Remove. When you remove an object from a submodel, the object remains in the Main model unless you select Delete from Model from the dialog that appears. • To select multiple entities, press and hold CTRL while clicking the entities. • To delete an attribute, select the attribute in the Data Model Explorer or double-click the parent entity or table in the Data Model Window to bring up the entity or table editor. In the editor, you can select the attribute to delete and then click Delete. • When deleting a relationship, you can either delete the relationship entirely or, by selecting Make Foreign Keys Native in the dialog that displays, you can choose to convert the foreign key relationship to an attribute of the child entity or table. Renaming an Object 1 On the Data Model Explorer, right-click the object that you want to rename. 2 From the shortcut menu, click Modify Name. 3 Enter the new name and press Enter. TIP: To rename an attribute, double-click the object or its parent in the Data Model Window to bring up the entity or table editor. In the editor, you can click the attribute and then click Edit. Searching for and Changing Object or Object Attribute Names Using the Universal Naming Utility you can globally search, and replace if desired, names, strings, and attachment value overrides for bound attachments for both your logical and physical models. You define your search, then confine the search to specific objects within your models, or confine the search to specific models only. You can also narrow the search to include only specified objects or object properties or to include only certain models. The results can include model objects such as attachment bindings and table storage parameters. 1 Select Tools > Universal Naming Utility. 2 Complete the String Specifications. TIP: You can limit the scope of the search or search and replace using the Object Scope and Model Scope tabs. EMBARCADERO TECHNOLOGIES > ER/STUDIO® 8.0.3 USER GUIDE 72
USING ER/STUDIO > COMMON TASKS 3 To search for a string, click Search. To replace a string, click Replace. Examine the Search Results and then click Apply to implement the changes. NOTE: Changes are not implemented until you click Apply. 4 To create a report of the search results in RTF or HTML format, click Report. To create a submodel of selected results, select objects in the results window and then click Create Submodel. TIP: RTF-formatted reports are ideal for print distribution, while HTML-formatted reports are better-suited for browser viewing. The following describe options that require additional explanation. Search Results tab Whole Word: Searches for whole words in the search string. For example, if your search string is the word “data,” check the Whole Word check box if you do not want results such as the word “database.” Object Scope tab Lets you narrow your search to specific objects and to specific string usages within the selected objects. Model Scope tab Lets you restrict the search to specific models within the diagram. See Also • For information on using the Submodel Editor, see Creating and Editing Submodels. Creating and Editing Data Base Views A data base view, also known as a materialized view, is a dynamic virtual table that reflects changes made to the entity or table data. In SQL, a view is the set of columns or attributes resulting from a SELECT statement. It is not part of the physical schema of a relational database and does not incur any extra storage overhead. Some of the uses for views include: • Presenting a subset of the data included in a table. • Joining and simplifying tables into a single virtual table. • Hiding the complexity of data. • Depending on the database platform, providing an additional layer of security by restricting user access to specific columns and/or rows. • Acting as aggregated tables, where aggregated data such as sum and average, are calculated and presented as part of the view. • Limiting the amount of exposure of sensitive data in the tables. • Creating a layer of abstraction to simplify complex data, transparently partitioning the actual underlying table. • Facilitating database normalization beyond second normal form. • Making it easier to decompose the underlying table and then join the parts without losing any information. EMBARCADERO TECHNOLOGIES > ER/STUDIO® 8.0.3 USER GUIDE 73
- Page 21 and 22: ER/STUDIO OVERVIEW > APPLICATION IN
- Page 23 and 24: ER/STUDIO OVERVIEW > APPLICATION IN
- Page 25 and 26: ER/STUDIO OVERVIEW > CONFIGURING AN
- Page 27 and 28: ER/STUDIO OVERVIEW > CONFIGURING AN
- Page 29 and 30: ER/STUDIO OVERVIEW > CONFIGURING AN
- Page 31 and 32: ER/STUDIO OVERVIEW > CONFIGURING AN
- Page 33 and 34: ER/STUDIO OVERVIEW > CONFIGURING AN
- Page 35 and 36: ER/STUDIO OVERVIEW > DATA MODELING
- Page 37 and 38: ER/STUDIO OVERVIEW > DEVELOPING A D
- Page 39 and 40: Using ER/Studio This section includ
- Page 41 and 42: USING ER/STUDIO > CREATING AND WORK
- Page 43 and 44: USING ER/STUDIO > CREATING AND WORK
- Page 45 and 46: USING ER/STUDIO > CREATING AND WORK
- Page 47 and 48: USING ER/STUDIO > CREATING AND WORK
- Page 49 and 50: USING ER/STUDIO > CREATING AND WORK
- Page 51 and 52: USING ER/STUDIO > CREATING AND WORK
- Page 53 and 54: USING ER/STUDIO > CREATING AND WORK
- Page 55 and 56: USING ER/STUDIO > CREATING AND WORK
- Page 57 and 58: USING ER/STUDIO > CREATING AND WORK
- Page 59 and 60: USING ER/STUDIO > CREATING AND WORK
- Page 61 and 62: USING ER/STUDIO > CREATING AND WORK
- Page 63 and 64: USING ER/STUDIO > BEST PRACTICES 8
- Page 65 and 66: USING ER/STUDIO > COMMON TASKS Comm
- Page 67 and 68: USING ER/STUDIO > COMMON TASKS Movi
- Page 69 and 70: USING ER/STUDIO > COMMON TASKS Copy
- Page 71: USING ER/STUDIO > COMMON TASKS Chan
- Page 75 and 76: USING ER/STUDIO > COMMON TASKS The
- Page 77 and 78: USING ER/STUDIO > COMMON TASKS 4 Co
- Page 79 and 80: USING ER/STUDIO > COMMON TASKS Sync
- Page 81 and 82: USING ER/STUDIO > COMMON TASKS In c
- Page 83 and 84: USING ER/STUDIO > COMMON TASKS Adva
- Page 85 and 86: USING ER/STUDIO > COMMON TASKS Asso
- Page 87 and 88: USING ER/STUDIO > COMMON TASKS Comp
- Page 89 and 90: USING ER/STUDIO > COMMON TASKS Dime
- Page 91 and 92: USING ER/STUDIO > COMMON TASKS •
- Page 93 and 94: USING ER/STUDIO > COMMON TASKS See
- Page 95 and 96: USING ER/STUDIO > COMMON TASKS The
- Page 97 and 98: USING ER/STUDIO > COMMON TASKS The
- Page 99 and 100: USING ER/STUDIO > COMMON TASKS •
- Page 101 and 102: USING ER/STUDIO > COMMON TASKS 3 In
- Page 103 and 104: USING ER/STUDIO > COMMON TASKS Chan
- Page 105 and 106: USING ER/STUDIO > COMMON TASKS •
- Page 107 and 108: USING ER/STUDIO > COMMON TASKS Shap
- Page 109 and 110: USING ER/STUDIO > COMMON TASKS Addi
- Page 111 and 112: USING ER/STUDIO > DEVELOPING THE LO
- Page 113 and 114: USING ER/STUDIO > DEVELOPING THE LO
- Page 115 and 116: USING ER/STUDIO > DEVELOPING THE LO
- Page 117 and 118: USING ER/STUDIO > DEVELOPING THE LO
- Page 119 and 120: USING ER/STUDIO > DEVELOPING THE LO
- Page 121 and 122: USING ER/STUDIO > DEVELOPING THE LO
USING <strong>ER</strong>/STUDIO > COMMON TASKS<br />
3 To search for a string, click Search.<br />
To replace a string, click Replace. Examine the Search Results and then click Apply to implement the<br />
changes.<br />
NOTE: Changes are not implemented until you click Apply.<br />
4 To create a report of the search results in RTF or HTML format, click Report.<br />
To create a submodel of selected results, select objects in the results window and then click Create Submodel.<br />
TIP: RTF-formatted reports are ideal for print distribution, while HTML-formatted reports are<br />
better-suited for browser viewing.<br />
The following describe options that require additional explanation.<br />
Search Results tab<br />
Whole Word: Searches for whole words in the search string. For example, if your search string is the word<br />
“data,” check the Whole Word check box if you do not want results such as the word “database.”<br />
Object Scope tab<br />
Lets you narrow your search to specific objects and to specific string usages within the selected objects.<br />
Model Scope tab<br />
Lets you restrict the search to specific models within the diagram.<br />
See Also<br />
• For information on using the Submodel Editor, see Creating and Editing Submodels.<br />
Creating and Editing Data Base Views<br />
A data base view, also known as a materialized view, is a dynamic virtual table that reflects changes made to the<br />
entity or table data. In SQL, a view is the set of columns or attributes resulting from a SELECT statement. It is not part<br />
of the physical schema of a relational database and does not incur any extra storage overhead.<br />
Some of the uses for views include:<br />
• Presenting a subset of the data included in a table.<br />
• Joining and simplifying tables into a single virtual table.<br />
• Hiding the complexity of data.<br />
• Depending on the database platform, providing an additional layer of security by restricting user access to<br />
specific columns and/or rows.<br />
• Acting as aggregated tables, where aggregated data such as sum and average, are calculated and presented as<br />
part of the view.<br />
• Limiting the amount of exposure of sensitive data in the tables.<br />
• Creating a layer of abstraction to simplify complex data, transparently partitioning the actual underlying table.<br />
• Facilitating database normalization beyond second normal form.<br />
• Making it easier to decompose the underlying table and then join the parts without losing any information.<br />
EMBARCAD<strong>ER</strong>O TECHNOLOGIES > <strong>ER</strong>/STUDIO® 8.0.3 US<strong>ER</strong> GUIDE 73