View Single Post
Old 01-18-2011, 10:17 AM   #16
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: 12,495
Karma: 8065348
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by unboggling View Post
Wouldn't it be nice to say to calibre users (particularly power users working with huge datasets) who might want or need it: there is this capabilty to work the SQL thing, and here is how to do it?
Actually, it scares me. I can see the reports now.
1) My database is hosed -- what do I do?
2) What did you do?
3) I was testing an Excel macro that changes the author names in the DB to base64.
4) Oh...

Updating calibre's database from outside of calibre is a bad idea. Unfortunately I don't see any way to prevent it, other than hope that the missing trigger functions would abort the update.
chaley is offline   Reply With Quote