move fails for properties when new file exists
|Missing in 1.5.x:|
When performing a MOVE the properties database is adjusted with an )"UPDATE properites SET resource = "new" WHERE resource ="old"). This however fails if there is properties for the new file since there now would be two records with the exactly same columns and sqlite fails the call.
Now I do not know SQL that well, but I think that the UPDATE call should by prefixed with a ("DELETE FROM properties where resource="new"). This worked when I did it offline using the sqlite3 utility.
Besides failing when there is an new file, the current situation also means that we inherit the properties from the existing new file.
Also available in: Atom