View Single Post
Old 06-07-2020, 02:26 AM   #30
kjdavies
Zealot
kjdavies is no e-book dilettante.kjdavies is no e-book dilettante.kjdavies is no e-book dilettante.kjdavies is no e-book dilettante.kjdavies is no e-book dilettante.kjdavies is no e-book dilettante.kjdavies is no e-book dilettante.kjdavies is no e-book dilettante.kjdavies is no e-book dilettante.kjdavies is no e-book dilettante.kjdavies is no e-book dilettante.
 
Posts: 112
Karma: 53342
Join Date: Jun 2013
Device: Sony PRS-600
Quote:
Originally Posted by kovidgoyal View Post
First off, I find it extremely hard to believe that calibredb performs worse through the server than without it, I certainly cannot replicate that. Do you perchance have an antivirus/firewall getting in the way?

Secondly you dont need multiple set_custom calls, you can set all metadata with set_metadata, including custom columns in a single call. Simply specify --field multiple times.
It could be that other elements are impeding performance, but... yep, about 2-2.5 times as long per title.

And strange, I did try setting multiple metadata (standard and custom) at once, using that syntax... didn't seem to work.

However, I will try again. Perhaps I had it formatted incorrectly.

set_custom doesn't have '--field', though.

calibredb set_custom [options] column id value

I take it I should try

calibredb set_custom [options] [column id value]*
kjdavies is offline   Reply With Quote