Anthony Accioly @Anthony Accioly - 6d
Hey Girino, yes. Unfortunately, this is the same error that nostr:nprofile1qqsqxcftp6awpmydxqp3c3qt5zrllx73v2tzmla6fdhqy8ky4lt3y9sprfmhxue69uhkummnw3ezuum4v3hkxctjd3hhxtnrdakszyrhwden5te0dehhxarj9ekxzmnytnk6x3 reported here: https://github.com/bitvora/haven/issues/85 — which I also faced myself. I don't have a better workaround than copying the current database somewhere, starting fresh, and running /haven --import again. (You can even start two instances of Haven and use the second one to import from the first if you don't have a copy of your notes on other relays.) I looked into the possibility of breaking down Khatru migrations into smaller transactions, but it's not a trivial thing to do. After speaking with Fiatjaf, it seems there isn't much appetite to tackle this, as it would substantially complicate the migration logic. In the future, I hope to provide more robust Haven backups along with proper "restore from backup" functionality as an alternative to the current import mechanism. I'm also planning additional support for relational databases such as SQLite and PostgreSQL, where migrations are a much easier problem to solve (and easier to work around on Haven's side if anything breaks in EventStore). Apologies that I don't have a better "solution" for the issue, but hopefully the re-importing gymnastics won't be too bad.
