The event listener functionality you are looking for only takes effect when the QueuePool object's public API of connect() is used. There is no other public method that will invoke the event listeners in their documented way.
On Nov 23, 2010, at 10:56 AM, FrancescaL wrote: > Thank you for your answer. > > If I understood correctly, I can use current implementation of > QueuePool but I have to change my previous example: > * replacing: "get()" with: "do_get()", and > * replacing: "return_conn()" with: "do_return_conn()" > > I did it, but nothing changed. That is, nothing is printed either at > checkin nor at chekout, as I expect. Am I missing something? > > Thank you, > Francesca Leon > > > > On Nov 23, 4:15 pm, Michael Bayer <[email protected]> wrote: >> The events are all initiated by the _ConnectionFairy and _ConnectionRecord, >> which are invoked when pool.connect() is called. pool.get() is an internal >> method and should be named _get(), I consider that a bug in fact so I've >> added ticket 1982 to fix this in 0.7. >> >> The pool object is pretty specific to DBAPI connections so if you need >> something similar, I'd lift its source code and adapt to be something >> simpler. Seems like what you really need is QueuePool.do_get() and >> QueuePool.do_return_conn() and nothing else. >> > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" 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/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 [email protected]. 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.
