Seems a client-server DB like MySQL would be much more practical. Simply append a "User-ID" Column to the DB tables. I doubt the Internet users are going to be hammering on the DB hard enough to cause server/network issues.
But then again, you could front end SQLite with some good thread design, as long as you promise not to start whining about multi user issues. :-) FOOTPRINT, FOOTPRINT, FOOTPRINT... Fred -----Original Message----- From: Christian Smith [mailto:[EMAIL PROTECTED] Sent: Thursday, July 14, 2005 9:23 AM To: [email protected]; Joey Ekstrom Subject: Re: [sqlite] Memory usage and multiple small databases On Wed, 13 Jul 2005, Joey Ekstrom wrote: >Would sqlite perform well in a web application where each user got >their own database to operate on? I know that the size of the sqlite >library is small, but what is the memory footprint after opening the >database? Would it be prohibitive to having a 500+ relatively small >database open concurrently?
