SQL Data Modeler bugs (or only misused?)
stuecklSep 3 2009 — edited Oct 21 2009Hi,
I think I ran into some modeler bugs and missing features ...
BTW: is there a place where all the known bugs are listed?
* although "no action" was selected in "General Options - Model - Relational" for foreign keys all the foreign keys are created with
"not deferrable" (well, why not, if it makes the modeler happy) and
"on delete set null" (thats not what I'd call "no action")
* DDL statements for indexes lack the schema name
* newly generated foreign relations are not always displayed in the relational model
* DDL preview for syncing physical model with relational does not (always) work (well - so far it worked once)
steps taken: File - Import - Data dictionary, selected objects for import, correct target model chosen, "swap target model" checked
* foreign keys in unique constraints are always set to "not null" (in logical and physical model)
* no trigger/constraint created for ARCs (I am not sure about this, but IIRC I did not see anything making an ARC really work)
Or do ARCs simply not work yet?
* modeler hangs sometimes (e.g. when opening "Save as" dialog etc.)
* dialogs are opened outside visible pane when the position of monitors is changed (the dialogs seem to remember their last position)
* sequences (physical model withing relational model) are loosing their user
* missing multi schema capabilities :-(
* the layout capabilities - pardon my french - suck
Especially that the boxes and lines seem to wander around from one usage to the next (entities aligned with grid - next start the entities are no longer aligned).
And if you ever need to save/export the model somewhere else all the references stick to a single connection point.
Not to mention a simple move of a box ...
Thank you for your effort
Peter
Edited by: stueckl on Sep 3, 2009 9:41 PM