Quote:
Originally Posted by Terisa de morgan
Professional curiosity: how will this column be populated when it will be added to the database? Can we expect a small delay in this install?
|
If you are asking about the next calibre install, then yes there will be a small delay after the upgrade. The 'sort' column is already in the series table in metadata.db and has been there for years, so there is no 'alter table' cost. Today that column is populated using triggers that copy the series value unchanged. The new install changes those triggers to copy the value after being processed by the 'generate sort' function that has also been in the database for years, so there is no incompatibility risk in downgrading calibre after an upgrade. The small delay the first time calibre is run after the upgrade is caused by correcting the existing sort values. That delay is proportional to the number of unique series values (not number of books), taking probably around a second per thousand unique values.
If you mean CC then no, there is no database change. The column is already there and populated. The only change to CC is that the correct value will be available in the cloud connection.