291823798 Error when deleting a collection
"An error has occurred. Please restart Firefox."
happened twice when deleting empty top level collections.
Ubuntu 8.10, current svn
Thanks,
Kent
happened twice when deleting empty top level collections.
Ubuntu 8.10, current svn
Thanks,
Kent
should be coming down the tubes right now.
[JavaScript Error: "no element found" {file: "https://ktenney%40gmx%2Ecom:********@storage-file-eu.gmx.com/zotero/" line: 1}]
[JavaScript Error: "no element found" {file: "https://ktenney%40gmx%2Ecom:********@storage-file-eu.gmx.com/zotero/" line: 1}]
Console output after the error
zotero(3): [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [mozIStorageConnection.createStatement]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://zotero/content/xpcom/db.js :: anonymous :: line 218" data: no] [QUERY: INSERT INTO syncDeleteLog VALUES (?, ?, ?)] [ERROR: table syncDeleteLog has 4 columns but 3 values were supplied]
For what it's worth, if you want to stay on the trunk, I'd recommend using the dev XPI unless you have a need to use SVN.
Is there a way to force a schema upgrade?
So you might want to check the userdata version stored in the DB. If it's 47 or higher, the upgrade somehow went through without the migration step being processed. If it's lower than 47, it should have offered to automatically upgrade at Firefox startup.
-- 49
Thanks,
Kent
The number in the migration step is the number the 'userdata' value gets set to after that step has completed.
userdata: 49
the case block in schema.js goes to
if (i == 49)
...
Should I change the zotero.sqlite versions table to
userdata: 47 ?
If so, can I do this from Firefox's SQLite Manager, or should
Firefox be closed when the change is made?
Thanks,
Kent
I can't advise you on this, I'm afraid, since you were using a development build and I don't know the state of your database. You'll need to examine your database and compare it to the SQL statements at the end of schema.js. It may be easier to just apply the necessary statements manually.
one from an install using the current .xpi, am looking at
a diff of the sql.
The only *table* change I see is in the syncDeleteLog table,
all the other differences are additional triggers.
to "apply the necessary statements manually" would
I execute sql to create the triggers?
Thanks,
Kent