So, are you saying I should re-initialize the Manager class each time
and pass it the physical connection I wish to use?
Lee
Nicolas Cannasse wrote:
That's fine, but is there a way to pass the new connection to the
Manager so that it uses that one and not the static one? I don't want
to have to drop SPOD to facilitate this. :-( The way I see it, the main
thread can continue using the static feature of neko.db.Manager, while
I'd like the updater thread to use a new seperate connection, while
still using neko.db.Manager.
It's up to your own abstract connection to define which "real"
connection to use when a call is performed, depending on
neko.vm.Thread.current() for example.
Nicolas
--
Neko : One VM to run them all
(http://nekovm.org)
