tonyp at acm.org wrote: > Doing SQLDIFF against a non-existent database (e.g., due to a typo) produces > a diff which is a series of DROP TABLE ... and also creates an empty file by > that name.
sqlite3_open() automatically creates the database file if it does not yet exist. (This is the only way to create a new database.) > Shouldn?t it instead give an error that there is no such database? Yes. sqlite3_open_v2() would allow to disable this behaviour. Regards, Clemens
