Thanks. I solved it by exposing connection and cursor objects via a Pyro. I don't have any access control for individual rows in tables but it doesn't matter for now. But I have a different problem now. I have a simple pool on the server side where I'm storing connections and cursors and it is growing without closing any cursors or connections. When does the SA call .close() on cursors or connections?
DS iGL píše v Čt 26. 10. 2006 v 16:15 +0000: > Hi, > A scenario and a basic implementation of what you're looking for is > described in "Python and XML", Chaper 10 - "Python and Distributed > Systems Design" ( > http://www.amazon.com/Python-XML-Christopher-Jones/dp/0596001282/sr=8-1/qid=1161878666/ref=pd_bbs_sr_1/002-2193540-4657636?ie=UTF8&s=books > ); this book is published as early as in 2001 and might well be > outdated otherwise, though. > Another option could be to build the server-mediator upon sqlite DB and > make it mirror a DB server. > HTH - I haven't myself found a ready-to-use lib for making that > stuff... > Best wishes, > Giorgi > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy -~----------~----~----~----~------~----~------~--~---
