saving a new database fails

[Rob Thornton]

Saving a newly created database fails. However, opening an existing database and choosing 'save-as' will save a correct copy of the database, even when overwriting an existing file.

[Rob Thornton (rob-t-telus)]

Both tables are being written. Language data is also being written. It seems that, when writing a new database only, some rows are skipped, namely the first one in each category and at least one category. Oddly, existing databases seem to be copied properly.

[Rob Thornton (rob-t-telus)]

Getting results from a new treeview store which have not been initialized will produce a NULL result. sql_insert_wordset () expects that ALL values passed to it are non-null, however, only the category and the first character set of each language should be required. Change line #140 in src/lib/sqlite.c to:

if (!cat || !n1 || !s1)

Then, if the above fails the returned result (merge pending which adds this feature) the editor should report a warning or write a log entry (or both) letting the user know that a row, or rows, could not be written.