Quote:
Originally Posted by InAFlap
thanks for the suggestion but would that be sortable.
|
Not as I've presented it - if you used an HTML table in the column then
maybe you could add some javascript to do the sorting within that HTML table.
But sorting/selecting across multiple books so you could get say - a list of books you read for the second time in 1987 - would probably be harder, and very slow.
Quote:
Originally Posted by InAFlap
Up until now I have been using an access database to store my book details and I have a separate table for the dates read linked by a title Id.
when the form is updated with a new date read it updates a field that shows the number of times read and a separate field with the last read date.
|
My perception is that Calibre does not have any 'parent-child/1:N' relationships as you describe, 'essentially' its one table (books), where each row has a bunch of foreign keys referring to simple 'lookup tables'.
Suggestion - copy a calibre database (metadata.db) from a library folder to your desktop, download the sqllite browser from Sourceforge, point it at the copy of the Calibre database on your desktop. This will give you the opportunity to gain a broad brush understanding of 'how calibre works', without having to wrap your mind around any python
My hunch is that Kovid is unlikely to introduce the transaction processing complexities of parent-child relationships any time soon.
davidfor's suggestion is probably the best idea. There may be a way to increment TimesRead automatically when you update LastReadDate. That would allow you to sort on FirstRead, LastRead and TimesRead. You would only use my
card at the back of the book idea - if sighting a reading history for an individual book was of any value.
I don't normally ask this question of an OP - but curiosity has got the better of me -
¿ why would you wanna do that! 
BR