On Monday, June 16, 2014 10:35:27 PM UTC-4, Michael Bayer wrote: > > it's unlikely we can do much about that, jython is hardly used at all > and is not a well-maintained platform; it regularly has subtle > interpreter bugs and such. pg8000 is in better shape these days but > tracking down something like this would require careful pdb debugging > and tracing. That it's an intermittent bug makes it that much more > difficult to track. >
FWIW, when i have a repeating intermittent issue like this... I have a separate SqlAlchemy connection to a 'logger' ( db or sqlite ) and log the exception to a table. something like .... timestamp | traceback | query | query_params on web projects, I add in some reports about the 'request' . usually a column for the url ; sometimes another for session data. sometimes i'll add in a report on the contents of the SqlAlchemy session. Once i've got 10 or so errors logged, I can use some quick sql selects to try and find patterns across them. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
