Upgrade Storage683746970 (Highlight broken in snapshots)
Zotero 3.0: Since upgrading Firefox to release 10, I have not been able to highlight text in snapshots. Old highlights (done prior to upgrade) remain.
Selecting the (1) highlight button prior to selecting text and (2) selecting text before the highlight button both have no effect.
I have not tried annotations.
Selecting the (1) highlight button prior to selecting text and (2) selecting text before the highlight button both have no effect.
I have not tried annotations.
A check of database integrity reported (unspecified) error(s). I did a chkdsk /r, installed a new hard drive, cloned the old disk to the new, rechecked integrity (still error).
I tried Zotero database repair (raw and zipped). Both exceeded limits and returned an empty file.
I did not try the SQLite procedure, since I can not be sure that it represents the current schema.
I concur with the kudos for the 3.0 release. It is much better and indeed faster. (You can tell from the file and folder volumes that I am perhaps pushing on the usual limits; since you are using a relational database, I should be o.k.)
I have run across a couple of minor things that I will put in a separate post FYI.
The integrity check also finds inconsistencies caused by bugs in earlier versions of Zotero, though, so it's possible your database isn't actually corrupt. In a future version we'll be able to fix some of those inconsistencies automatically, and we'll have the integrity check make clear whether the issue is actual corruption or those more minor issues.
In general, though, unless you're experiencing problems you don't need to worry about it (though, Zotero aside, you should of course have daily or hourly backups of your entire hard drive anyway).
It looks like some instances (rows) can be deleted based upon settings by SQL commands or lack of required entries. For the former, I would need the current schema and data definitions. For the latter, I would do well to clean up the values in my data base first (e.g., blank "creator").
Referential integrity can now be enforced in SQLite, including deferral until transaction is complete. Cascade delete of subordinate items is also provided. I assume this was lacking in earlier versions of SQLite, and is the root cause of some of the items needing repair.
The following is in sequence of the SQL commands in Manual Zotero Database Repair Instructions. “// “ is the comment I inserted in a copy for the analysis.
// Appears to delete instances (rows) from tables where the instance has a foreign key not found in table “Items”.
// Appears to delete instances (rows) from table “fulltextItemWords” where the instance has a foreign key not found in table “fulltextItems”. This may be a sequencing constraint
// Appears to delete instances (rows) from tables where the instance has a foreign key not found in table “Items”.
// Appears to delete instances (rows) from tables where the instance has a foreign key not found as primary keys in various other tables. Also deletes “items” that lack “itemTypeID”.
// “Updates” appear to be a cleanup of attachment relationships, including setting the itemTypeID of “items” to ‘14’. Without knowing the current schema / attribute definitions, I have no idea what is done or why it is done. (Also, I do not understand the conditions selecting the “Delete From” statement.)
// These Updates using a Temporary Table may be a correction/deletion of ill-defined Tag values.
// This Update may be a correction of the charsetID attribute value.
// Apparently Groups and Libraries are part of the current schema, but not part of the schema I am looking at.
// Apparently null or blank creator first AND last names are not permitted. Can’t tell whether lack of First and Last Name applies to Standalone Notes.
But we wrote these statements. There's no reason to spend more time evaluating them than every single other SQL command in Zotero.