On 1/1/06, Michael Bayer <[EMAIL PROTECTED]> wrote:
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.
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!" ?
The worst offender is http://www.sqlobject.org/sqlobject-admin.html
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
