On Mar 9, 2008, at 5:58 AM, Eric Ongerth wrote:
> Finally after enough hair loss, I stopped poring over the tracebacks > shown in the Pylons error response, and went directly to the paster > debug logs. Hmm! What was actually happening was that a foreign key > relationship was being violated (or i guess you could say just not > satisfied) by the value I was trying to save (update). The foreign > key error message went to the log where I wasn't looking, because I > typically only look there if the in-browser Pylons error response is > absent or otherwise hung up. Meanwhile for some reason the ultimate > result was showing up as Connection Already Closed. So maybe the > underlying Foreign Key error resulted in the connection closing, and > something in the way SA handled that led to the Connection error, and > I only saw the latter because I hadn't thought to look for an error > beneath the error. > this seems like an error in how you are integrating with Pylons, or how Pylons is integrated with exception throws. An exception throw was ignored, and control passed to your regular view template as though it were a successful request. This kind of bug is pretty common in a lot of software but it lies within how SQLA is integrated here. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
