Re: [Sqlalchemy-users] table create/drop options

Sun, 01 Jan 2006 21:59:18 -0800

ah , well its the "record" and "upgrade" commands there where it goes into "management" territory.  I have no interest in that sort of thing either, its a lot easier to just keep the DDLs in text files.  i dont have any interest getting into versioning/ALTER statement generation.  

the "CREATE" functionality is there for basic application distribution; someone downloads your app, it can set up its tables to start with, in a database agnostic way.  "DROP" functionality is there because, well its just one line of code and also its used in the unit tests to clean up after itself.  Beyond that, the idea of abstracting DDL maintenance operations is way out of this thing's scope, and is better suited for a graphical tool or something.


On Jan 2, 2006, at 12:32 AM, Jonathan Ellis wrote:

On 1/1/06, Michael Bayer <[EMAIL PROTECTED]> wrote:
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!" ?
 

Although to tell the truth I'm not even a fan of "let's duplicate CREATE TABLE functionality in Python" -- this particular wheel reinvention just doesn't strike me as very useful, even if it succeeds in not being horribly cumbersome (compared to just writing the SQL), which I'm not sure is possible.
 
I think this fad must have started with one of the "oh no! let's protect people from sql because sql is hard and python is easy!" projects, because I really don't see the advantage to using a syntax (python's) less-suited for table definition instead of one designed for it.  Obviously it's trivial to embed CREATE TABLE in .py scripts for testing etc so that's not a justification for this feature.  And any real project is eventually going to grow past the original model with ALTER TABLE etc, and that's where you start getting into the realm's of Ian's horrible hacks if you keep trying to control the DDL from your .py definition instead of introspecting.
 
-J

Reply via email to