On 25 Apr 2011, at 6:20pm, Mickey Mestel wrote: >> Have you tried removing SQLCipher, and just use standard SQLite, to help >> isolate the source of the problem? > > hmmm... not good. i removed SQLCipher, and am linking with the > standard libsqlite, and the problem persists.
Okay, if you have that problem with standard SQLite then we can probably help you with it. On 24 Apr 2011, at 1:49am, Mickey Mestel wrote: > if i then shut down the app and restart it, the data is retrieved with > no issues. > > so basically a connection is made to the database, the table is created > if it doesn't exist, we go through a loop of processing JSON data read from > the web and inserting it row by row, then close the connection to the > database. if i immediately make another connection, the rows come back empty. > > after the last insertion, i put a breakpoint and checked with an > external tool, and i can see all of my data in the database. but while the > app is running, the rows all return empty. Corrupted database handle. Uncorrupted database handle, but it points to corrupted memory. Your 'SELECT' routine doesn't do what you think it does. The parameters to your SELECT aren't what you think you are. Just for laughs, in your code after you reopen the database, put an extra INSERT before your SELECT. Does your SELECT pick up the INSERT or no data at all ? Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
