View Single Post
Old 06-27-2013, 03:45 AM   #2
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,449
Karma: 8012886
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
This is something we would like to do, but unfortunately it isn't straightforward. The first problem is that calibre's device subsystem is not permitted to write information into the database. I can get around that, but I need to be absolutely certain that whatever I do can't corrupt the database. The second problem is "synchronization": how to handle simultaneous changes to the field on the device and in calibre. How does one detect it? Which change wins?

I have had some discussion with Kovid about how I could do this in a way that is general enough to be acceptable yet has behavior that is predictable. I haven't gotten there yet.

Bottom line: we will get there eventually, but I wouldn't hold my breath.
chaley is offline   Reply With Quote