Well...you don't say what "problem" your customers are having. Would be nice to know for us to help you. But it sounds a LOT like you're not handling SQLITE_BUSY returns. You may be seeing SQLITE_BUSY returns from your "read data...and put" step. But that assumes you're looking for it from the return codes. You could also see SQLITE_BUSY from your CREATE, or your JOIN, or any statement for that matter if you have multiple process hitting the database. Michael D. Black Senior Scientist Northrop Grumman Mission Systems
________________________________ From: sqlite-users-boun...@sqlite.org on behalf of Sam Carleton Sent: Mon 5/17/2010 8:10 AM To: General Discussion of SQLite Database Subject: [sqlite] read only databases and in-memory databases Current situation: 1. Open a DB for read/write 2. Create a temp table 3. Read data from outside source and put into the temp table 4. Do a join on the temp table and another table in the DB 5. Return results This is happening a lot, and it might be the cause customers are having problem. Can the code be changed to open the DB as read only and attach to a :memory: database, or would the :memory: database also be read only? Sam _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
