Common questions about jasonisnthappy and how to use it
jasonisnthappy is maintained by Soham and is actively developed. You can track development activity on the GitHub repository and join discussions on Discord.
Yes, jasonisnthappy supports concurrent access from multiple processes to the same database file.
jasonisnthappy uses Write-Ahead Logging (WAL) to ensure durability. If your application crashes during a write, the database will automatically restore from the WAL on the next startup if the write wasn't already committed to the main database file.
Database encryption is not currently available, but it's planned for a future release. This feature is coming soon.
There are no hard-coded limits, but extensive testing hasn't been completed yet. In testing, a 2GB database file with documents up to 20MB worked well. Real-world limits will depend on your system's resources and use case.
WASM support is being experimented with and is planned for future releases. Stay tuned for updates on browser compatibility.
Just update the library dependency in your project. The database format is designed to be backward compatible, so data migration shouldn't be needed in most cases. However, this guarantee may change until we reach v1.0, so always check the release notes for breaking changes.
If the database file gets corrupted, you'll need to restore from backups. jasonisnthappy has built-in backup and recovery features to help you maintain data redundancy. Always keep regular backups of important data.
Yes, you can open and manage multiple database instances within a single application.
It should work on ARM architectures including Raspberry Pi. While it hasn't been extensively tested on these platforms, there's no architectural reason it wouldn't work. If you encounter issues, please report them on GitHub.
Yes, jasonisnthappy works perfectly inside Docker containers. Just mount a volume for your database file to ensure data persistence.