In my ongoing attempt to find the best approach for integrating SQLite into a threaded Web-serving environment, I came upon a truly crude kludge, and I wanted to know if it's bad from an SQLite architectural standpoint. I know it's bad morally and ethically.
Basically, is it bad if I decide to open and close the same database a LOT? For example, rather than opening a database when the server boots and keeping it open for the duration, is it bad if I open it for every query and close it right away? I'd set some sort of open-semaphore so multiple threads wouldn't open it at once, but then, even though different threads would be working on the database, they'd each have their own id. The only gotcha is the bazillion times the db's opened and closed. So, what do you think? Just poor programming or dangerous to do? Also, is there a ton of overhead on open or close? Thanks, David ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
