Do you have the 'sqlalchemy.engine' logger set to 'WARN'? I do and I get messages like Mikko Ohtamaa gets. I'm not sure the transaction manager is the right place to log these things because it doesn't know what's wrong, only that an exception occurred. It wouldn't be able to print the SQL command and parameters, for instance. And if you weren't using the transaction manager, you wouldn't get the errors if it was logging them.
I haven't seen an error like Mikko's but I occasionally get errors like 'Integrity error: duplicate primary key' , or something when the database server auto-upgrades itself and restarts. I haven't seen any 'psycopg2' error; maybe I need to configure its logger. If you're using autoincrement primary keys and you're manually inserting the ID into another table, you may have to insert a manual 'session.flush()' to generate the key. Otherwise if you do 'secondtable.first_id = firsttable.id' you'll get None which may cause a null violation in the second table. On Fri, Oct 6, 2017 at 6:33 AM, Srikanth Bemineni <bemineni.srika...@gmail.com> wrote: > Hi, > > I am using Mysql. This is one single insert into a table and its failing for > some reason. I am not able to predict the reason for the failure. sqlalchemy > just prints ROLLBACK. > > INSERT INTO group_message_22f9b36c (group_id, group_topic_id, score, > user_id, uname, msg, created_at, updated_at) VALUES (%s, %s, %s, %s, %s, %s, > %s, %s) > 2017-10-06 00:44:40,883 INFO > [sqlalchemy.engine.base.Engine:1143][b'uWSGIWorker2Core0'] (11, 1, 0, 6, > 'sammy', 'sdfsdf', datetime.datetime(2017, 10, 6, 5, 44, 40, 880935), > datetime.datetime(2017, 10, 6, 5, 44, 40, 880935)) > 2017-10-06 00:44:40,897 INFO > [sqlalchemy.engine.base.Engine:699][b'uWSGIWorker2Core0'] ROLLBACK > > > On Friday, October 6, 2017 at 3:07:47 AM UTC-5, Mikko Ohtamaa wrote: >> >> Hi Srikanth, >> >> Are you using PostgreSQL? Does the transaction fail because of concurrent >> transactions reading or writing same data? >> >> Usually there should be something like this written in the logs: >> >> sqlalchemy.exc.OperationalError: (raised as a result of Query-invoked >> autoflush; consider using a session.no_autoflush block if this flush is >> occurring prematurely) >> >> (psycopg2.extensions.TransactionRollbackError) could not serialize access >> due to read/write dependencies among transactions >> >> -Mikko >> >> On 6 October 2017 at 08:02, Srikanth Bemineni <bemineni...@gmail.com> >> wrote: >>> >>> Hi, >>> >>> Whenever a sqlalchemy commit fails, the transaction will be automatically >>> rolled back. When this does happen the pyramid_tm which commits the >>> transaction should print the message with the reason for rollback. >>> >>> We get one simple message from sqlalchemy. Most of the times we need to >>> guess the reason for the rollback. >>> >>> 2017-10-05 23:56:29,072 INFO >>> [sqlalchemy.engine.base.Engine:699][b'uWSGIWorker1Core0'] ROLLBACK >>> >>> Is there way I can see the error , with the reason for roll back ? >>> >>> Srikanth B. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "pylons-discuss" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to pylons-discus...@googlegroups.com. >>> To post to this group, send email to pylons-...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/pylons-discuss/2fc1209f-f677-4fbe-a572-05517c9e5462%40googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >> >> >> >> >> -- >> Mikko Ohtamaa >> http://opensourcehacker.com >> http://twitter.com/moo9000 >> > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to pylons-discuss+unsubscr...@googlegroups.com. > To post to this group, send email to pylons-discuss@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/pylons-discuss/6d62ae3a-ee7f-42ec-b88a-2610d47d9164%40googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. -- Mike Orr <sluggos...@gmail.com> -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To post to this group, send email to pylons-discuss@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/CAH9f%3Dur0-kMvWjVWQc7iim%2BftPHqwLf1o%2B-A5%2BtyYkWzU4PV0A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
