Thanks a lot...forking was the problem..it is working now :) Roger Binns wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 21/11/11 23:02, gavyas wrote: >> I dont understand why I am getting this error. > > My best guess would be that a fork is happening after the database has > been opened inserted by the compiler (but not gcc) in order to make things > parallel. If you do a fork after a database has been opened then you are > very likely to get this kind of error in addition to database corruption. > Ensure all open calls happen after forks. > > It is possible to put checking into SQLite to detect when the API has been > used across a fork. I have it as part of the APSW project where it keeps > track of which pid the internal mutexes are called. It incurs about 1% > overhead in a program only doing database calls. Code example is here: > > http://code.google.com/p/apsw/source/browse/src/apsw.c#860 > > Roger > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iEYEARECAAYFAk7LTdQACgkQmOOfHg372QTyZwCfbMHOcLjp9ctFMDvZtMJXu5oC > yW0AoJRRaJtNHB1xQviY00khV79aVIWV > =W5E1 > -----END PGP SIGNATURE----- > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > >
-- View this message in context: http://old.nabble.com/SQLite%3A-Database-or-disk-full-tp32871505p32872174.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
