Eduardo wrote: > On Jul 14, 10:49 am, "King Simon-NFHD78" > <simon.k...@motorolasolutions.com> wrote: > > Eduardo wrote > > > > > > > > > When I use the same script with a standalone application it works > but > > > when I try to run it as a wsgi application it fails (wsgi logs > does > > > not contain any information regarding the failure!) > > > > Try turning on SQL logging (either by passing echo='debug') to > > create_engine, or by configuring the python logging package as > described > > onhttp://www.sqlalchemy.org/docs/core/engines.html#configuring- > logging. > > Then you should see the SQL being issued and the results coming > back > > from the database. > > > > How are you configuring transactions? Is it possible that the > > transaction isn't being committed at the end of the web request, so > any > > changes you've made are being discarded? > > > > Simon > > My application only queries the database there are no inputs and > therefore no transactions involved. >
What was the result of turning on SQL logging? Are you sure you're even pointing at the same database that you were when you ran the standalone script? Try printing the value of session.bind.url (or including it in HTTP response, if you don't have easy access to the stdout from your wsgi script) Simon -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
