|
ORM Webcast |
|
News
|
By Scot Becker on
12/29/2004
|
|
|
|
SearchDatabase.com has a webcast featuring Terry Halpin titled "Fact-based Database Design".
|
 |
|
|
More...
|
|
|
|
|
Nested Role Readings |
|
Visio Tool Tips
|
By Scot Becker on
11/3/2004
|
|
|
|
You may have noticed than when an object type is the result of a nested predicate, you can specify extra information on the "Nested Roles" tab of the "Database Properties" window. This is provided in case you wish to add extra semantics between the relationship of the nested object type and the object types that make up the fact type that was nested.
|
|
|
|
|
More...
|
|
|
User Defined Types and ORM |
|
Visio Tool Tips
|
By Scot Becker on
11/2/2004
|
|
|
|
User defined types are typically used to express semantic domains that cross multiple attributes. For example, one could create a type named "Phone Number" as some sort of length-limited character type and then use that type as the basis for several attributes such as fax number, mobile number, office number, home number, and so on.
|
|
|
|
|
More...
|
|
|
Visio FAQ: Ordering columns in index creation |
|
Visio FAQ
|
By Scot Becker on
10/22/2004
|
|
|
|
In some DBMS’s, the order in which columns appear in the creation/definition of an index (which spans multiple columns) can have performance impacts. Should you be saddled with such a silly restriction, you might be wondering how to specify the column order within Visio.
|
|
|
|
|
More...
|
|
|
|
N-ary fact verbalizations |
|
Visio Tool Tips
|
By Scot Becker on
10/20/2004
|
|
|
|
For any given fact type, there are n! (read: n factorial) readings of that fact type (where n is the number of roles in the fact type). In a unary fact type, there is exactly one reading, in a binary there are two readings, in a ternary there are six readings (3 x 2 x 1), in a quaternary there are 24 readings (4 x 3 x 2 x 1), and so on.
|
|
|
|
|
More...
|
|
|
|
|
Using Namespaces in ORM Source Models |
|
Visio Tool Tips
|
By Scot Becker on
10/14/2004
|
|
|
|
Many object types have similar (usually, descriptive) properties. For example, People, Animals, Products, and so on, all have names. This poses a choice for the ORM Modeler: do you create one "Name" object type or multiple?
|
|
|
|
|
More...
|
|
|
|
|
|
|
Cloning and Reusing Model Elements in Visio |
|
Visio Tool Tips
|
By Scot Becker on
10/12/2004
|
|
|
|
Although Visio supports the standard cut-copy-paste operations found in most software, the results might not be what you expect because Visio separates the notion of the definition of a model element (e.g. a table, object type, predicate, whatever) from the shape(s) used to display that element.
|
|
|
|
|
More...
|
|
|
|
Visio Bugs |
|
Site Announcements
|
By Scot Becker on
10/7/2004
|
|
|
|
I’ll be adding a new section shortly to catalog bugs related to the database functionality (ORM Source, ER Source, and Database Model Diagrams) in Visio for Enterprise Architects.
|
|
|
|
|
More...
|
|
|
Verbalization of Reference Modes |
|
Visio Tool Tips
|
By Scot Becker on
10/7/2004
|
|
|
|
On the "Ref Mode" tab of the "Database Properties" sheet for an object type, you may have noticed the "Type" drop down list. This list is enabled if the selected object type is an entity type and has a simple (internal) reference mode.
|
|
|
|
|
More...
|
|
|