When sqlalchemy flushes pending changes to the database,
sometimes those changes fail and raise a DatabaseError
(eg, trying to delete a row that is referenced by a foreign
key when the ON DELETE action is NO ACTION or RESTRICT).
When that happens sqlalchemy enters a rollback state and
requires
On Sunday, February 17, 2013 10:06:33 AM UTC-7, ru...@yahoo.com wrote:
[...]
My question is how is this normally managed in typical
application code? A flush can potentially occur anytime a
mapped attribute is changed. Do I need to wrap every such
place in my code in a try/except to
just to note, I can't reproduce this, this would be a pretty basic failure as
described, so I really need to see mappings and working code, and it certainly
looks like something is making it do that for you, so really need to know what
it is.0.8.0 is going out very soon. See below where
The TOC is generated correctly for me in 1 pass with invocation of make
latexpdf (I verified with make clean latexpdf). I've attached my make
log. Google groups is not allowing me to attach the generated PDF file or
my make output. Please let me know how we can proceed to debug this issue.
