Support multiple sql dialects #104
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request migrates the authentication and directory backend from MySQL-specific implementations to a unified, database-agnostic SQL backend. It introduces new configuration options for SQL backends, updates documentation and example configs to reflect these changes, and removes the old MySQL backend code in favor of new SQL backend providers. The changes make it easier to support multiple SQL databases (MySQL, MariaDB, SQLite3, PostgreSQL) and simplify configuration via connection URLs and custom SQL queries.
Backend migration and code removal:
server/backends/mysql.auth.jsandserver/backends/mysql.directory.js). [1] [2]server/backends/sql.auth.js) that uses Sequelize and supports custom queries via environment variables.Configuration and environment variable changes:
sqlinstead ofmysql, and replaced individual MySQL variables with a singleSQL_URLand query variables (SQL_QUERY_ONE_USER, etc.). Updated example configs inREADME.md,.env.example, and other docs. [1] [2] [3] [4]Documentation updates:
Feature and compatibility improvements:
Migration instructions: