Vania Smrkovski wrote:
Have you or anyone encountered issues regarding my other questions,
that of using SQLite as a web-served DB system? How do the recently
discussed issues of concurrency and the locking of DB tables and files
affect the use of a web site delivered SQLite DB system, and is the
strategy of using multiple DB files (which is what I understood D.
Richard Hipp's suggestion to be) effective enough if one central table
were to have hundreds of thousands of records?
The www.sqlite.org website is run off of a single SQLite database.
Back before I implemented bandwidth throttling, the site would
sometimes get 50000 hits/day to pages that used the database.
If your website gets fewer than 100000 hits per day, I think SQLite
should work ok (depending on what you are doing, of course). For
more than 1000000 hits per day, you should probably use a client/server
database engine of some kind. For values in between 100K and 1M,
I don't really have enough experience to say. Probably it would
depend on how heavily you are using the database.
--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
