Trying to set a custom tag got error message in 2.2

[rd4407]

In versions prior to 2.2, I was able to set a custom column tag via its drop down selection.

Now I get an error message:

calibre, version 2.2.0
ERROR: Failed to set data: Could not set data, click Show Details to see why.

Traceback (most recent call last):
File "site-packages\calibre\gui2\library\models.py", line 1031, in setData
File "site-packages\calibre\gui2\library\models.py", line 1057, in _set_data
File "site-packages\calibre\gui2\library\models.py", line 1023, in set_custom_column_data
File "site-packages\calibre\db\legacy.py", line 653, in set_custom
File "site-packages\calibre\db\cache.py", line 1024, in set_field
File "site-packages\calibre\db\write.py", line 513, in set_books
File "site-packages\calibre\db\write.py", line 523, in set_books_for_enum
File "site-packages\calibre\db\write.py", line 290, in many_one
File "site-packages\calibre\db\write.py", line 246, in get_db_id
File "site-packages\calibre\db\backend.py", line 793, in execute
File "c:\cygwin64\home\kovid\sw\build\apsw-3.8.2-r1\src\cursor.c", line 231, in resetcursor
ConstraintError: ConstraintError: UNIQUE constraint failed: custom_column_4.value

Is there anything I need to do to, or is this a bug?

Edited: This problem affects the last item only, which I rarely use, so I don't know how long the problem may have been there.

[BetterRed]

Originally Posted by rd4407

In versions prior to 2.2, I was able to set a custom tag via its drop down selection.

Now I get an error message:

Spoiler:

calibre, version 2.2.0
ERROR: Failed to set data: Could not set data, click Show Details to see why.

Traceback (most recent call last):
File "site-packages\calibre\gui2\library\models.py", line 1031, in setData
File "site-packages\calibre\gui2\library\models.py", line 1057, in _set_data
File "site-packages\calibre\gui2\library\models.py", line 1023, in set_custom_column_data
File "site-packages\calibre\db\legacy.py", line 653, in set_custom
File "site-packages\calibre\db\cache.py", line 1024, in set_field
File "site-packages\calibre\db\write.py", line 513, in set_books
File "site-packages\calibre\db\write.py", line 523, in set_books_for_enum
File "site-packages\calibre\db\write.py", line 290, in many_one
File "site-packages\calibre\db\write.py", line 246, in get_db_id
File "site-packages\calibre\db\backend.py", line 793, in execute
File "c:\cygwin64\home\kovid\sw\build\apsw-3.8.2-r1\src\cursor.c", line 231, in resetcursor
ConstraintError: ConstraintError: UNIQUE constraint failed: custom_column_4.value

Is there anything I need to do to, or is this a bug?

@rd4407 - do you mean a custom column as per attachment

The one you see is working for me.

BR

[rd4407]

Yes, a custom column, that I set up a long time ago.

Now, with 2.2., I can get as far as selecting the item from the drop down, but it doesn't take, giving me an error message instead.

But, testing again, I noticed that it is the last item in the list that gives the error.
Other values don't give the error. I rarely use the last item, so I really don't know how far back this problem may've gone.

So I guess a temporary workaround is to put a dummy item at the end, to allow the real item to be used.

[BetterRed]

Originally Posted by rd4407

Yes, a custom column, that I set up a long time ago.

Now, with 2.2., I can get as far as selecting the item from the drop down, but it doesn't take, giving me an error message instead.

But, testing again, I noticed that it is the last item in the list that gives the error.
Other values don't give the error. I rarely use the last item, so I really don't know how far back this problem may've gone.

So I guess a temporary workaround is to put a dummy item at the end, to allow the real item to be used.

@rd4407 - Can you confirm the Column Type is: Comma separated text, like tags, shown in the tag browser. I may be testing the wrong column type.

The word 'tag' has many meanings in calibre - in the context of the Tag browser everything's a Tag, in the editor one of these <xxx> is a tag

As you say, a value of 'zzzzzzzzzzzzzzz' will work around the problem.

BR

[rd4407]

Column type: Text, but with a fixed set of permitted values

[BetterRed]

Originally Posted by rd4407

Column type: Text, but with a fixed set of permitted values

@rd4407 I can't reproduce the error here with that column type.

The definitions and values are held in the database, maybe they've become 'corrupt' in some way. After backing-up the database library you could try doing a Library Maintenance->Restore Database.

BR

[kovidgoyal]

It would help if you attached the metadata.db file from your calibre library folder.

[rd4407]

Now, a couple of days later, I replaced the last "dummy" entry with a new real item, and selecting the last item worked.

[BetterRed]

Originally Posted by rd4407

Now, a couple of days later, I replaced the last "dummy" entry with a new real item, and selecting the last item worked.

@rd4407 - I venture to suggest that adding that dummy value caused calibre to rewrite your custom column to its Preferences custom-columns table row in metadata.db, and in so doing it 'fixed' the 'corrupt' value. I think its a BLOB hence , hard to debug unless your name is Kovid Goyal

Thanks for letting us know the problem is solved.

BR

[chaley]

Originally Posted by BetterRed

I think its a BLOB, hence hard to debug unless your name is Kovid Goyal

For future reference, custom column definitions are in plain text in the "custom_columns" table. For columns with fixed values, the list of values is the "display" column along with some other stuff. The same information is in the "field_metadata" row in the preferences table and in metadata_db_prefs_backup.json.

[BetterRed]

Originally Posted by chaley

For future reference, custom column definitions are in plain text in the "custom_columns" table. For columns with fixed values, the list of values is the "display" column along with some other stuff. The same information is in the "field_metadata" row in the preferences table and in metadata_db_prefs_backup.json.

For no good reason I was thinking conversion-options table - as always it pays to check before sticking head above parapet - they do both begin with 'c'

BR