If you use sqllite thru the web.py API you shouldn't have this problem. On Sun, Mar 2, 2008 at 4:11 PM, Brian Blais <[EMAIL PROTECTED]> wrote: > > Hello, > > I need a database backend for webpy that is easy to deal with. I > thought that buzhug would work for me, and I really like its syntax, > but I get number of files overloads. Anyone else use buzhug with > webpy? I was thinking of using sqlite, as I would like to avoid > having a dedicated sql server. Has someone used sqlite with webpy? > Any issues, or gotchas? I imagine that I could run into the same > problems with open files, because sqlite uses an on-disk method > without a dedicated server, and (as I understand it) every time > someone accesses a URL in webpy it spawns a new thread. Thus, each > time webpy accesses a URL, it reopens the same file, etc... Is there > an example I could follow to using sqlite with webpy which avoids > this problem? Any other recommendations? > > > thanks, > > > Brian Blais > > > >
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
