On 10/17/13, Ethan Jucovy <[email protected]> wrote: > On Thu, Oct 17, 2013 at 4:51 PM, Olemis Lang <[email protected]> wrote: > >> On 10/16/13, Olemis Lang <[email protected]> wrote: >> > >> [...] >> > >> > I attribute this to the fact that the DB connection is still bound to >> > the previous DB (<= is that possible ?) which already contains default >> > values ; if so what's the recommended approach to invalidate the >> > DatabaseManager pool ? Shutdown seems too radical . >> > >> >> Fairly easy . JFTR DatabaseManager(env)._cnx_pool = None will released >> connections cache . > > > I started looking into this code today. Not sure how much it matters in > tests, but I believe you want to be doing DatabaseManager(env).shutdown() > instead. That method sets ._cnx_pool to None, but also does some cleanup > on the existing connection pool first which sounds important (for closing > any open connections? I dunno) >
I'll take a look then ... -- Regards, Olemis - @olemislc Apache™ Bloodhound contributor http://issues.apache.org/bloodhound http://blood-hound.net Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: -- You received this message because you are subscribed to the Google Groups "Trac Development" 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/trac-dev. For more options, visit https://groups.google.com/groups/opt_out.
