Hi Lenster,
For a Web application you are probably better off with MySQL, it runs as
a seperate process and handles multiple threads really well. I'm
probably going to offend the sqlite people out there, but sqlite is
fantastic for an embedded database, and a web app is not what I would
call embedded.
Regards,
Chris
Lenster wrote:
I am investigating which would be the most appropriate RDMS to use for
a new Intranet based application. I have rounded down my choice to two
candidates - SQLite and MySQL.
The application needs to be available to about twenty users on a daily
basis, with most of those users making no more than five 'write'
transactions a day, and around twenty 'read' transactions a day.
Depending upon its success the application may well develop to
incorporate other datasets and users - so the RDMS needs to be able to
develop without difficulty.
IMHO SQLite looks as though it would be the fastest to develop and with
the least resources required but after reading some SQLite
documentation:
"A good rule of thumb is that you should avoid using SQLite in
situations where the same database will be accessed simultaneously from
many computers over a network filesystem."
I am concerned that even though I expect light usage it is likely that
multiple users will access the same database concurrently.
Would I be correct in assuming that MySQL is a safer (longterm) bet?
Thanks for any and all responses
Len
--
View this message in context:
http://www.nabble.com/Most-appropriate-Web-based-database-%28Newbie%29-t1404628.html#a3780531
Sent from the SQLite forum at Nabble.com.
