On Mon, Sep 15, 2008 at 11:49:48PM -0400, [EMAIL PROTECTED] scratched on the wall: > I would like to use SQLite from a network share. I would like to create a > server app that would do all of the writing to the database except for > certain tables, one table per client,the clients would write to their own > table only. The client drops it's data/instructions into it's own table, > the server app would scan all client tables for new data/instructions and > then write the data to the main tables of the database. Would this work > without concurrency issues?
Doubtful. Since the database is one file, it doesn't matter if the clients keep to their own tables. You still have multiple systems trying to write to the same networked database. Now if each client had a completely separate database, that *might* work, but you'd still have concerns about the remote clients and local server accessing the individual databases at the same time. > Another question I have is do I understand correctly that an SQLite > database, on a network share, has no problems with many readers, the > problem starts with many writers. Is this correct? When "many" equals "1 or more", yes. Writes need to be completely exclusive. Even if all the writing is done locally, the networked readers may not be kept out of the way for the critical sections of the write operation. My guess is that the write operation would be correct, but the reads may crash or get bad data. -j -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "Our opponent is an alien starship packed with atomic bombs. We have a protractor." "I'll go home and see if I can scrounge up a ruler and a piece of string." --from Anathem by Neal Stephenson _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
