| Project: | Mori |
| Version: | 1.2 |
| Component: | Miscellaneous |
| Category: | bug |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed |
Description
I tried Mori again and again ran into this horrible bug (http://www.hogbaysoftware.com/node/964#comment-1868). This time I took the _default_ notebook, added some entries, added more ... no problems so far. But then I created a custom column and from that moment: "same entryDataID ...." for more than ten items. "Repair" did non fix anything, you get crazy search results, Mori finds entries which have *nothing* to do with the search term and so on.
This is the worst case for a database I think.
Updates
Thanks so much for this report. I've been long aware of the entry-id problem, but didn't realize the custom columns played a part. The problem was pretty simple in the end. When a custom column is created I migrate the document to a new file. The problem was that I was forgetting to copy the nextID value that is used to determine what id to use for the next inserted entry. That meant that the value defaulted to zero, and so new entries that were created after creating a custom column would possibly collide with existing entry ids.
I've fixed the problem locally and will include the fix in the next release. Thanks again.
| Status: | active | » closed |