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:

I sincerely hope that SA doesn't fall into the "and manage your DDL too!" feature creep that other projects have.
 
On 1/1/06, David Geller <[EMAIL PROTECTED]> wrote:
It would be nice to have a "table create if not exist" and a "table drop
if exist"


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Sqlalchemy-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users



--
Jonathan Ellis
http://spyced.blogspot.com

Reply via email to