Chris Withers wrote: > Michael Bayer wrote: >> Chris Withers wrote: >>>> Easiest way to trap it is to monkeypatch Session.rollback(), or >>>> whatever >>>> rollback you think you might be calling, with a def that calls >>>> pdb.set_trace() or dumps a stack trace using inspect(). >>> Any chance of SA growing the ability to do the latter itself? >> >> Again, I really don't know what you mean here, unless you're asking for >> a >> "enable_pdb=True" keyword on rollback() or something, which I doubt. > > I'm asking for an "enable_trace=True" which would be like echo=True > except *in addition* would do the equivalent[1] of logging with > exc_info=true. > > cheers, > > Chris > > [1] I'm not sure you could actually use exc_info=True, since no > exception will have been raised at this point, you just need a repr of > the current strack trace.
when is a stack trace emitted ? seems very much like something an external library should be doing. > > -- > Simplistix - Content Management, Batch Processing & Python Consulting > - http://www.simplistix.co.uk > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To post to this group, send email to sqlalch...@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. > > >
-- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalch...@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.
