On 6/30/06, Charles Duffy <[EMAIL PROTECTED]> wrote: > Kevin Dangoor wrote: > > I thought I fixed this, and I "sort of" did. Once you hit the > > database, this shouldn't happen. I just added an explicit call in > > startup.startTurboGears that will hopefully take care of this. > > That doesn't actually appear to resolve the problem. I'm stumped as to > why, though -- since bind_meta_data() is always issuing a new connect() > to the engine, the DynamicMetaData should always have an engine bound if > bind_meta_data() has been called within that thread; however, even > adding a bind_meta_data() call at the top of the method where the > exception is thrown, the issue still occurs.
Odd. That almost makes it sound like it's a different metadata instance, but I'm not sure how that would be possible. I don't seem to see this error if I touch the database soon after starting the server. (At least, I haven't seen this error since last night...) Kevin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk -~----------~----~----~----~------~----~------~--~---
