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 <[email protected]>: > > 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 [email protected]. > To unsubscribe from this group, send email to > [email protected]. > 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
