UNIQUE constraint failed: children.node_id, after creating a subnode about cherrytree HOT 2 OPEN

[The following has been copied and pasted from an email I just sent]

Hi,

Sorry it took me so long.

I found a way to remove most data in the file, "save and vacuum", and still experience faulty behaviour. You will find the file attached to this message.

If you add a subnode to the "rabbitMQ" node and save the file, you will get the error « UNIQUE constraint failed: children.node_id »
Same error after adding a subnode to some other nodes, like the 8 or 9 lowest nodes in the file.

Two bizarre things I saw in the SQL dump for this file :

• there's a node n. 557 that is not displayed anywhere when I open the file with CherryTree, as is it not referenced in the "children" table
• there are holes in the "sequence" numbers for children of node 190, it seems like this bug is triggered after adding a subnode to one of the nodes that are after this hole (those with "sequence" > 12 in the "children" table)

Anyway, don't worry too much about this, it's probably a result of some kind of corruption that happened with an older release, and cannot happen in current releases, plus I can fix the file by using the "save as" function.

But thanks for looking into it anyway :-)

Cheers,
Sylvain

from cherrytree.

Hi @sylvainfaivre the 'save as' is regenerating a completely new database while the 'save' is only updating the part that you modified, so the save relies on the past. A 'save as' is also regenerating all the node IDs starting from 1. You can send me the misbehaving database via email (see help--about) and explain what to do to reproduce the issue

from cherrytree.