-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 25/01/13 23:45, abbood wrote: > i fixed it!! you were right! it's not to do with the guts of sql.. > rather it's to do with my incorrect sql statement..
Huh? There is no SQL statement, valid or not, that can cause memory errors. It looks like SQLite is the victim of some other memory mismanagement in your app and changing the SQL has just changed what code will fall victim to it. It is a very good idea to run valgrind before proceeding. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAlEEA6AACgkQmOOfHg372QSswACgoIg1jidTzar4EVVfQmFZlDwb ZuAAn1iIuUz84T4Gpzgv2Q58U1zYq9MR =z+X5 -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
