Closed agentydragon closed 1 year ago
Hi, thanks for reporting.
I don't think it's caused by wrong data in the database - this happens because of attribute's name being null/undefined, but the DB has NOT NULL constraint on that column. So it's rather some kind of ephemeral state error in the application, but from looking at the code I did not find where it could originate from (it could come also from user scripts).
I've made the code more robust to not fail on this.
huh, that's weird. i wonder how did it get into my database. i do have a bunch of user scripts, but they all use the trilium script api and/or etapi, so i'd still expect the db-level integrity checks to apply and prevent it. oh well, thanks for looking into it!
i wonder how did it get into my database
I don't think it did. It errors out on the in-memory object. I suspect that the null/undefined sneaked into the in-memory object, but not into the database (because of the DB constraint).
Trilium Version
0.57.5
What operating system are you using?
Ubuntu
What is your setup?
Local + server sync
Operating System Version
Pop!_OS 22.04 LTS
Description
happens to me on some autocomplete queries, see screenshot below. not sure how this happened, perhaps some note in db in a weird state?
persists after both "check database integrity" and "find and fix consistency issues".
db version is 197, sync version 26
Error logs