On Thu, Dec 16, 2010 at 9:34 AM, Steve Kieu <[email protected]> wrote: > Hello every one, > > I have an application which does many update in a different set of record > to the same table. With PostgreSQL if run from multiple host at the same > time the server return message: > > could not serialize access due to concurrent update > > but does not throw any Exception - I wish I can catch this after > store.commit() and process (re commit again or rollback etc) > > With MySQL InnoDB the same problem (it says something about deadlock and > quit) and no exception is thrown from storm. > > Is it good to throw exception in that case? Currently I have to use > wherether no transactions (use MyISAM is fine, or in postgres, commit > every-time I update an object). Another possibility is to wrap the py script > in a bash shell check the text output and re run script again if failed - > which is not a good thing IMHO > > Many thanks for your time and help,
Could you provide some more details of what you are trying? Storm shouldn't be eating those sort of exceptions, and while there were some bugs in ancient versions of psycopg2 related to reporting errors from commit, that hasn't been a problem for a long time. James. -- storm mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/storm
