-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CNID backend using modern database tech #1177
Comments
As a side note, I learned today that Bloomberg actively maintains a BerkeleyDB fork as the key store backend bundled with their in-house SQL database called comdb2. But it doesn't look like it can be built as a separate package without modification. |
rdmark
pushed a commit
that referenced
this issue
Nov 12, 2024
Based on the Netatalk MySQL CNID backend by Ralph Boehme. Adapted for SQLite by Christopher Kobayashi. Ported to Netatalk 3 by dgsga. Touched up for Netatalk 4 by Daniel Markstedt.
rdmark
pushed a commit
that referenced
this issue
Nov 12, 2024
Based on the Netatalk MySQL CNID backend by Ralph Boehme. Adapted for SQLite by Christopher Kobayashi. Ported to Netatalk 3 by dgsga. Touched up for Netatalk 4 by Daniel Markstedt.
rdmark
pushed a commit
that referenced
this issue
Nov 12, 2024
Based on the Netatalk MySQL CNID backend by Ralph Boehme. Adapted for SQLite by Christopher Kobayashi. Ported to Netatalk 3 by dgsga. Touched up for Netatalk 4 by Daniel Markstedt.
rdmark
pushed a commit
that referenced
this issue
Nov 14, 2024
Based on the Netatalk MySQL CNID backend by Ralph Boehme. Adapted for SQLite by Christopher Kobayashi. Ported to Netatalk 3 by dgsga. Touched up for Netatalk 4 by Daniel Markstedt.
rdmark
pushed a commit
that referenced
this issue
Nov 17, 2024
Based on the Netatalk MySQL CNID backend by Ralph Boehme. Adapted for SQLite by Christopher Kobayashi. Ported to Netatalk 3 by dgsga. Touched up for Netatalk 4 by Daniel Markstedt.
Two data points regarding obsolescence:
While it is still available in both stable releases, there's a risk of removal in any future release version. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a feature wishlist item about creating a new CNID backend that uses a modern light-weight database.
Our primary backend, dbd (database daemon), relies on BerkeleyDB which is by most measures abandoned software.
All in all, staying with BDB isn't future proof.
We have the mysql backend, but it relies on a separately managed database instance to use. What we need is something that can be spun up on demand, be fast and highly reliable.
Sqlite has been brought up in the past as a potentially strong contender.
The text was updated successfully, but these errors were encountered: