Re: [Sqlalchemy-users] engine.execute()

2006-09-05 Thread Enrico Morelli
On Mon, 4 Sep 2006 14:48:19 -0400 Michael Bayer <[EMAIL PROTECTED]> wrote: > well if its echoing, its definitely going in. its possible you > might need a "commit" afterwards (the engine does "autocommit" for > most write operations if a transaction is not in session, but > "ALTER" is not on

Re: [Sqlalchemy-users] engine.execute()

2006-09-04 Thread Michael Bayer
well if its echoing, its definitely going in. its possible you might need a "commit" afterwards (the engine does "autocommit" for most write operations if a transaction is not in session, but "ALTER" is not one of the keywords it looks for). try running your operation through a transaction

Re: [Sqlalchemy-users] engine.execute()

2006-09-04 Thread Enrico Morelli
On Mon, 4 Sep 2006 11:18:33 -0400 Michael Bayer <[EMAIL PROTECTED]> wrote: > that should work fine, add "echo=True" to your create_engine() call > and it will show you all the SQL being issued. > Infact, using echo=True I see: In [75]:engine.execute('ALTER TABLE planning_set_2006 ADD COLUMN a

Re: [Sqlalchemy-users] engine.execute()

2006-09-04 Thread Michael Bayer
that should work fine, add "echo=True" to your create_engine() call and it will show you all the SQL being issued. On Sep 4, 2006, at 10:03 AM, Enrico Morelli wrote: > Another question, > > why when I try to use engine.execute() to alter a table nothing > happens? >> From a program that I'm w