hello julien, other friends, the logging was enabled, but info and debug level are the same, since the query returns no result: 11:24:30,872 INFO [sqlalchemy.engine.base.Engine] alter table tblitemcategories add SalePrice float(53) DEFAULT (0) NOT NULL; 11:24:30,872 INFO [sqlalchemy.engine.base.Engine] () 11:24:30,966 INFO [sqlalchemy.engine.base.Engine] alter table tblitemcategories add SaleVipPrice float(53) DEFAULT (0) NOT NULL; 11:24:30,966 INFO [sqlalchemy.engine.base.Engine] ()
other queries, these related to my permissions, did work and their results were logged too, with level DEBUG. as i said, the queries reach the dbms, since it reports sql syntax errors. any other ideas about what is preventing their execution/finalization? best regards, alex On 11/08/2011 04:15 PM, alex bodnaru wrote: > > thanks a lot julien for your answer. > > i did try the first idea, and will try the second right now. > > thank again, > alex > > On 11/08/2011 02:02 PM, julien tayon wrote: >> If you suspect a rollback in the controller why dont you try to force >> the transaction commit ? >> if I remember correctly it could look like : >> import transaction >> transaction.commit() >> >> And why dont you change sqlalchemy log level to debug and echo = True >> to troubleshoot your problems ? >> >> hf, gl >> >> Jul >> 2011/11/8 alex bodnaru <alexbodn.gro...@gmail.com>: >>> >>> hello friends, >>> >>> i'm trying to perform a few ddl actions through sqlalchemy >>> dbsession.execute(sql) >>> >>> if the sql is wrong, i'm getting an error screen with the relevant message >>> from >>> mssql, hence the execute reaches the rdbms (even with no explicit flush). >>> >>> otherwise, with correct sql i get no visible error, but still the actions >>> don't >>> take effect on the server, hence i suspect some kind of rollback follows the >>> execute. >>> >>> i mention that i could do similar actions with the same db-user, even >>> through >>> sqlalchemy, but not turbogears controller. >>> but similar(ddl) sql has been correctly run on setup-app. i'm also trying >>> explicit flushing session and committing the transaction after >>> dbsession.execute >>> like there, but still no result in the db. >>> >>> could you help? >>> >>> thanks in advance, >>> alex >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "TurboGears" group. >>> To post to this group, send email to turbogears@googlegroups.com. >>> To unsubscribe from this group, send email to >>> turbogears+unsubscr...@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/turbogears?hl=en. >>> >>> >> > -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to turbogears@googlegroups.com. To unsubscribe from this group, send email to turbogears+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
