Thread: uuid isnull
View Single Post
Old 09-26-2010, 04:17 AM   #5
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 11,742
Karma: 6997045
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by jkcoder View Post
Any reason why that might be null on import? Or what might cause them to be null?
Modifying calibre's database outside of calibre is extremely dangerous. Calibre has all sorts of triggers that work to keep the db consistent, and updates are not running these. Look at the calibre files schema_upgrades.py and sqlite.py.

When a book entry is created, a trigger is run that does stuff. One thing it does is call a python-supplied function to set the UUID. That function will not be there, so the trigger is presumably removed.

Fix the script to run in python using calibre's debug facility, 'calibre-debug -e'. Otherwise you are likely to never get things right.

And sorry, but I am not interested in helping get this right. I don't care in the least about ISBNs.
chaley is offline   Reply With Quote