right... ok, I get that. So, is there a way to connect a new network connection to an existing sqlite db? I tried some suggestion from a posting of a few weeks ago, and it seems to connect, but tables are 'invisible'.
** Note ** some dbs are created from script (no web), still web2py (just no web, like __2py ;)) and others are created/maintained in a deployed web2py environment. Possible? can I for example have a script (DAL stand- alone), connect to a fully deployed web2py's DB? Actually, the scenario can be web2py app connects to another web2py app (on the same or different server), can also be stand alone DAL to stand-alone DAL, or stand-alone-DAL to web2py server, or web2py server to stand-alone DALs db.... Thanks, Mart:) On Jan 31, 9:24 am, Massimo Di Pierro <massimo.dipie...@gmail.com> wrote: > Impossible. You cannot picke a network connection. It more than just > data. > > On Jan 31, 5:30 am, mart <msenecal...@gmail.com> wrote: > > > > > > > > > Hi, > > > I'm looking to try something (again) that has not yet been too > > successful (but I still want to try)... Currently (with stand-alone > > Dal) I am managing by passing 'db' around (or rather self.db) to avoid > > having to create more instances than I have to. Now, to pick up some > > processes where they left off, I would like to try pickling 'self.db' > > to a file, let sys.exit() happen, load the pickle, then debug > > exceptions, but without having to start from scratch ad rely on > > breakpoints to wake me up when I get to troublesome areas (the wait > > can be as long as an hour sometimes). > > > So, has anyone successfully pickled 'db'? Anything fancy that need to > > be done the the attributes (even if only temporary). > > > Thanks, > > Mart :)
