search

m4heshd / better-sqlite3-multiple-ciphers

better-sqlite3 with multiple-cipher encryption support 🔒
MIT License
137 stars 27 forks source link

The file is not a database😕. #54

Closed Vanillma closed 1 year ago

Vanillma commented 1 year ago

Hi...I noticed that the flag is also in the beta version, please remove it from there if possible.

But I have a question for another problem! I was able to create a database with table through the API and Multicipher...and also some rows of data.

but the problem is that when I try to open the database with Sqlcipher(on command line), it gives an error and says that it is not a database!

I first created the table with sqlcipher and then tried to connect with the API, I also tried the other way around.

but I always get the same error... is this the expected behavior?

m4heshd commented 1 year ago
  1. Please don't quote old/closed issues in a new issue and mix up the context. It makes it very difficult for the maintainers to debug, for you to get an answer, and for the people who read this in the future. An old issue should only be mentioned in the context of your current issue has a relationship to that.
  2. Please include some debug information, your code, or better, a minimal reproducible repo for your code so the maintainers can quickly debug the issue you're running into. Open-source maintainers hardly have any time to investigate things from scratch.
  3. Always search for old issues before opening a new one because there's a high chance that your issue could already have been debugged in the past.

Continuing from that third point, the issue you're having is both in the documentation and mentioned in multiple issues including Issue #14. Closing the issue as a duplicate.

Vanillma commented 1 year ago
  1. Please don't quote old/closed issues in a new issue and mix up the context. It makes it very difficult for the maintainers to debug, for you to get an answer, and for the people who read this in the future. An old issue should only be mentioned in the context of your current issue has a relationship to that.
  2. Please include some debug information, your code, or better, a minimal reproducible repo for your code so the maintainers can quickly debug the issue you're running into. Open-source maintainers hardly have any time to investigate things from scratch.
  3. Always search for old issues before opening a new one because there's a high chance that your issue could already have been debugged in the past.

Continuing from that third point, the issue you're having is both in the documentation and mentioned in multiple issues including Issue #14. Closing the issue as a duplicate.

I'm so sorry.

But: 1- I have already used the reference feature in other repositories and they had no problem!

2- And Of Course, Github and Microsoft must have put that option for users to use...isn't that right???

In any case, you as the repository owner have options...such as deleting an issue completely...if you need to correct your issue history and are very concerned, please delete this issue completely.