Author's Note

[kovidgoyal]

Originally Posted by chaley

In this case the data is in a composite column and won't be used to restore the author's notes.

Are the author's notes actually stored somewhere that restore database uses to repopulate the db? It seems they would need to be kept in export format somewhere in the library.

Yes the notes have their own separate backup and restore mechanism. See the code for details notes/connect.py set_backup_for() function

[DNSB]

Originally Posted by ownedbycats

base64 has an overhead of some 30%, if I remember right.

From my notes when I was playing with Base64, the overhead will be 33% from the encoding and up to 4% for the inserted line breaks for a total of ~37%. So for a 93KB image, the 126KB Base64 encoded size is pretty much as expected.

[BetterRed]

Originally Posted by Karellen

I kind of liked the composite column, but yes I think I will remove it and access it from book details panel.

You could also put Browse notes into a toolbar/menu or use its keyboard shortcut - Ctrl+Shift+N. It's easier than fishing for an icon to click in the embedded BD… which you might have hidden.

Mouse hover over a Pencil icon in BD will display "Show notes for: whatever" tooltip, would it be possible to show the note content a'la Karellen's composite column.

BR

[chaley]

Originally Posted by chaley

I'll take a look at whether it makes sense adding an option to composite column definition to not include the column in an OPF. They are there for clients to use. They aren't much use for backups because (duh) they are computed when needed.

The problem will be getting the details right because OPFs are built in lots of places with differing versions.

I added a checkbox to the composite column definition dialog that controls whether the value for that column is stored in an OPF, default True. If the box is unchecked then the value in the OPF for that column is set to the empty value. This method preserves the data necessary for the distributed backup without putting the large value into the OPF.

The changes are now in calibre source and will be in the next release/preview.

[ownedbycats]

I'll definitely be trying that - due to multiple composites, there's sometimes a bit of a delay as the OPF writes to disk.

[chaley]

Originally Posted by ownedbycats

I'll definitely be trying that - due to multiple composites, there's sometimes a bit of a delay as the OPF writes to disk.

The change might not help. The value is computed then not stored. Doing otherwise requires large changes to the "jobs" flow when converting & sending to device.

[Karellen]

Originally Posted by chaley

I added a checkbox to the composite column definition dialog that controls whether the value for that column is stored in an OPF, default True. If the box is unchecked then the value in the OPF for that column is set to the empty value. This method preserves the data necessary for the distributed backup without putting the large value into the OPF.

The changes are now in calibre source and will be in the next release/preview.

That is great. Thank you @chaley.
I guess that will be in v7.18 in a couple of weeks.

[chaley]

Originally Posted by Karellen

That is great. Thank you @chaley.
I guess that will be in v7.18 in a couple of weeks.

Also will in the preview on Friday.

[Karellen]

Originally Posted by BetterRed

use its keyboard shortcut - Ctrl+Shift+N.

Forgot about that shortcut.
Thanks!!