The sequence is: * open a new database file * issue a sequence of several SQL commands in a single transaction (one BEGIN, one COMMIT at the end).
The database ends up as a zero length file. Is this a) a normal consequence of the above if the single transaction is aborted (say due to an SQL error) b) should never happen, and indicates a faulty sequence of API calls c) something else? It just started happening and it would help to know where to look. Regards David M Bennett FACS Andl - A New Database Language - andl.org _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
