I am looking into the best method for implementing a database for a small application that I will most likely be building it in Adobe Air. I looked at "Appropriate Uses For SQLite" on the the SQLite.org website and I got some conflicting info.
for Example I saw the following: "SQLite usually will work great as the database engine for low to medium traffic websites (which is to say, 99.9% of all websites). The amount of web traffic that SQLite can handle depends, of course, on how heavily the website uses its database. Generally speaking, any site that gets fewer than 100K hits/day should work fine with SQLite." this seemed to conflict a little with this: "If you have many client programs accessing a common database over a network, you should consider using a client/server database engine instead of SQLite." My application will be on a local network and only accessed by 10- 20 people at most. I would like to have a non-client/server based solution if possible. I was looking at MySQL originally, but the "embedded into application part of SQLite got my attention as I would not have to have a Apache, PHP an MySQL solution ready at all times. I have no experience with SQLite but some MySQL experience. Is SQLite a good fit for this type of application/situation? thanks -- View this message in context: http://old.nabble.com/appropriate-Uses-For-SQLite-tp29852017p29852017.html Sent from the SQLite mailing list archive at Nabble.com. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
