Martín Schamis said: > Hello, I´ve seen inthe sqllite page that,"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" > > 1 .- This means that I can´t use a php on the web and the users acceding > to that page can`t modify the base ? > > 2.- Or there is a limi of users ? > > 3.- If there is a limit waht is it ?
It means that the file shouldn't live on a network file system. It your web server folder is accessed via NFS or SMB (Windows File Share), SQLite isn't the tool for you. Given the volume of transaction processing you're indicating, you might want to consider if this is the right database for you. Consider if there will really be 300 simultaneous connections (which is different from 300 simultaneous application users) that you might instead be in need of a high availability client/server database model. PostgreSQL fares very well in this category, or some of the heftier commercial database offerings. Clay Dowling -- Lazarus Notes from Lazarus Internet Development http://www.lazarusid.com/notes/ Articles, Reviews and Commentary on web development
