-
Notifications
You must be signed in to change notification settings - Fork 6
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
Old code with language files and MySQL #6
Comments
Yes, but MySQL would allow you to run multiple talkers (perhaps on different hosts) using the same database! I know that is definitely a priority for you (wink wink). Who needs netlinks when one can just use a single shared database (with shared login sessions and credentials, etc). I think I would lean toward a non-relational semi-structured database when it comes to use in talkers (but query language choice then becomes a key issue). As far as low footprint open source SQL alternatives go, I would consider the following:
There are also a few Java ones around (e.g., H2) but I would not recommend those unless you are writing something in a language that targets the Java/JVM platform or want to run a heavier weight server (e.g., Apache Derby aka Cloudscape). |
It would be nice to have a data layer and just write drivers. MySQL/MariaDb, TiDB, Firebird, MongoDB and such would just be a choice by the person setting it up. I've been tempted to run a talker again in a container. A bunch of security holes for these days. |
I know it's been half a year (and in terms of old school talkers, that's like yesterday), but I added a bit of a container setup to Amnuts the other day. Kind of a work in progress, but if you fancy seeing if it's practical for use or needs lots more work: #12 |
I found a copy of version 2.2.2 yesterday where I had added a hash table for lookups on language files and started to integrate MySQL for storage of messages and profiles.
Putting it here as a reminder to one day resurrect that code and properly look into it.
Pretty sure I have some test code somewhere that used sqlite instead, and I'd prefer that over MySQL. So try to find it!
The text was updated successfully, but these errors were encountered: