In article <[EMAIL PROTECTED]>, =?ISO-8859-1?Q?Gregory_Pi=F1ero?= <[EMAIL PROTECTED]> wrote: > >That module deals with accessing data from QuickBooks, marshaling it, >and providing methods to access the marshaled data. Having the server >program keep that module and all of its data in memory makes the >server run really fast, but yeah, it does get complicated now that >it's storing 100's of MB of data. I guess most people go to a >database at this point?
Very, very yes. Try using a SQLite in-memory database, maybe? >It's just so easy to store the data in the Python objects I already >need them in instead of converting to tables in a DB and then >converting back. So maybe this threading will work for me. You might well run into problems with the import lock. I strongly advise against your current approach. -- Aahz ([EMAIL PROTECTED]) <*> http://www.pythoncraft.com/ "I support family values -- Addams family values" --www.nancybuttons.com -- http://mail.python.org/mailman/listinfo/python-list