On 11/6/21 4:48 PM, Tony Arnold wrote: > > > On Sat, 6 Nov 2021 at 18:23, Butch Carpenter <csc...@gmail.com > <mailto:csc...@gmail.com>> wrote: > > > On 11/6/21 12:27 PM, Patrick Shanahan wrote: >> * Butch Carpenter <csc...@gmail.com> <mailto:csc...@gmail.com> [11-06-21 >> 12:12]: >>> Here's what I get from the integrity check: >>> >>> sqlite3 ~/.config/darktable/library.db "PRAGMA integrity_check" >>> ok >>> >>> Then when I start darktable from a terminal and respond with "upgrade >>> database", here's the results: >>> >>> /usr/bin/darktable %U >>> [init] can't drop table images_old >>> [init] FOREIGN KEY constraint failed >>> [init] database `library.db' couldn't be upgraded from version 32 to 34. >>> aborting >>> ERROR : cannot open database > > > My concern here would be the table 'images_old' and why it can't be > dropped. I don't think such a table is normally present. I'd take a > look at the db with a suitable sqlite browser and see if it's there > and what the foreign key constraints are on it. Possibly try and drop > the table manually (take a back up first!) > > Just a thought. > > Regards, > Tony. > There is no image_ old object anywhere within my entire system. That includes / and all connected media. So that is a mystery that the developers would need to investigate. In any case, I have deleted library.db and begun importing my collection. Only 1200 or so more to go.
____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
