My aim is to have threads across servers listen on the database for
certain notify events (let's say "insert update"). That code I suppose
can live outside of SQLObject.
Once that event is received in the listening thread, it can open a new
connection to perform an object select. Or can SQLObject take an
existing DB API connection object and use it for subsequent sessions?
If it could, then its a nice way to bridge between stuff that can only
be done outside SQLObject and then perform the cool stuff inside it,
using the same connection.
I'm still reading the docs, so apologies if its on there and I missed it
On Tue, 2008-11-18 at 00:02 +0300, Oleg Broytmann wrote:
> On Mon, Nov 17, 2008 at 08:54:48PM +0300, Oleg Broytmann wrote:
> > On Mon, Nov 17, 2008 at 12:47:36PM -0500, Darren Govoni wrote:
> > > I think I will try to do the listen/notify outside of SQLObject and then
> > > fetch the objects using SQLObject. Should work.
> > There could be a problem with transactions - opening a cursor outside of
> > SQLObject gives you a different transaction.
> Oops, sorry - opening a new *connection* gives you a different
> transaction. But that (opening a new connection) is what you have to do
> anyway to work with the DB outside of SQLObject. Or you can try to use
> a low-level DB API connection hiding in the SQLObject's DBConnection