Reverse Engineer Database
----------------------------------------
This should generate the Stored procedures and Functions BEFORE defining the Tables etc.. Right now it generates the table definitions first, and if a Default column value references a function, the script will abort because the function is not yet defined.

Also the data should only be inserted AFTER the table constraints have been defined. As it stands, the constraints are added after the data is loaded so altering the table with the data already loaded is going to take a lot more time. Also if adding a constraint fails because the data is invalid, the script aborts with invalid data in the table and no constraints. I'd rather have an empty completed database with constraints defined, instead of a database with data and no constraints defined.

Scripts
----------
When executing a script, and there is a script error, pressing Cancel does nothing. I have to press continue to cancel the script which isn't obvious.

Barry

Reverse Engineer is much more complicated than it initially sounds.
What might work for your database might not for mine.  I often use
tables inside stored procedures, so defining stored procedures first
would break for me.


What I've done is a reverse engineer, then try to apply it to a new
database and keep tweaking things to the order I need until I no longer
get errors.  Then save the script!

--
David Cornelius
Cornelius Concepts

On 08/07/2012 09:49 AM, Barry wrote:
> Reverse Engineer Database
> ----------------------------------------
> This should generate the Stored procedures and Functions BEFORE defining the Tables etc.. Right now it generates the table definitions first, and if a Default column value references a function, the script will abort because the function is not yet defined.
>
> Also the data should only be inserted AFTER the table constraints have been defined. As it stands, the constraints are added after the data is loaded so altering the table with the data already loaded is going to take a lot more time. Also if adding a constraint fails because the data is invalid, the script aborts with invalid data in the table and no constraints. I'd rather have an empty completed database with constraints defined, instead of a database with data and no constraints defined.
>
> Scripts
> ----------
> When executing a script, and there is a script error, pressing Cancel does nothing. I have to press continue to cancel the script which isn't obvious.
>
> Barry
>

Barry,

<< This should generate the Stored procedures and Functions BEFORE defining
the Tables etc.. Right now it generates the table definitions first, and if
a Default column value references a function, the script will abort because
the function is not yet defined. >>

The reverse-engineering does not do proper dependency-checking yet.  The
dependency information has been in place for a while now, but I just haven't
had time to get around to implementing the necessary changes in the
reverse-engineering.  Hopefully things will die down a bit and I can spend
some time on this.

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com