| my experience with DDLs is mostly those of Oracle which have a ton of oracle-specfic keywords in them, like stuff for tablespaces, max extents, etc. I definitely dont want to get into that kind of thing. although someone could come in and contribute all those as arguments which get picked up by the oracle module, as long as those concepts didnt pollute the base schema/type packages....but if someone were going through all that trouble they might just end up doing a separate project so that it could be more tailored towards that kind of thing. im not sure what youve seen in the area of "manage your DDL!", right now SA can print out a DDL, and its expected that some apps would have a bunch of Table definitions that get create()ed when you install the application. is that "manage your DDL!" ? also I created a ticket for the main work involved here, a "table_exists()" function in all the engines. On Jan 1, 2006, at 7:51 PM, Jonathan Ellis wrote:
|
- Re: [Sqlalchemy-users] table create/drop options Michael Bayer
- Re: [Sqlalchemy-users] table create/drop options Jonathan Ellis
- Re: [Sqlalchemy-users] table create/drop options Michael Bayer
- Re: [Sqlalchemy-users] table create/drop options Mark Ramm
- Re: [Sqlalchemy-users] table create/drop optio... Michael Bayer

