Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 2 of 2 total
Thread DeZign for Databases v5 findings
Tue, Mar 18 2008 8:05 PMPermanent Link

"Lance Ras"
I thought I would post some findings with DeZign for Database 5.   I have
had their product for a while and just upgraded to take advantage of their
new support of ElevateDB.

I've reported my findings to them, but wanted to keep all in a loop.  Most
likely their issues, but you should be aware of.

1) Field types of GUID are reverse-engineered correctly as GUID's into
DeZign.   However, this field type will forward-engineer as VARCHAR(38).
While it's the same....   It's not.
2) Tim's reverse-engineer shows Description as the first optional item for a
table being created.  DeZign forward-engineers the description at the end.
3) DeZign forward engineers the description as single qoutes.
4) DeZign forward engineers default value functions like CURRENT_GUID,
CURRENT_TIMESTAMP with a single qoute and should have no qoutes (comparing
to Tim's reverse-engineered stuff)
5) DeZign forward engineers a sting value 'NONE' or 'M' (I'm including the
single qoute, CURRENT_GUID, CURRENT_TIMESTAMP with a single qoute and should
have no qoutes (comparing to Tim's reverse-engineered stuff)
6) Forward engineering of a default GUID value comes out weird.
"ReassignID" VARCHAR(38){ {DEFAULT
'{00000000-0000-0000-0000-000000000000}'}}

Lance Rasmussen
Wed, Mar 19 2008 4:37 PMPermanent Link

"Lance Ras"
Just an FYI.

Rick from Datanamic was VERY responsive in addressing the issues.  There was
a couple typo issues and they also added a reserved word definition list to
know what to qoute or not.   I did, BTW, forgot to RTFM regarding an option
in their definitions which states you can square bracket around the default
value to not qoute it.


Image