>
http://www.levelextreme.com/ViewPageArticle.aspx?Session=4E2B314F346C70334470633D204A5050484E6A716B4572324177484F414D74613237413D3D>
>Thanks.
>
>Someone recommends
>
>
http://sourceforge.net/projects/dbdesigner-fork/Actually I haven't seen much other products, but from what I heard, it seems the VisioModeler uses a different design philosophy from many other products. You start designing, not the tables and their relations, but statements about data - "person has a name", "student has a grade", for example. Relations can be binary (as in these example), ternary, or in fact have any "arity" between 1 and 9. You specify some restrictions (this can be done with examples), to indicate which part of a relation can have duplicates and which not. On the basis of this, the program decides on the table structures and the relations. Now, I don't know how similar or dis-similar this is from other design products, which I know very little.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
