Navigation Menu

Skip to content

Instantly share code, notes, and snippets.

@andrewnicols
Created February 26, 2020 02:55
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save andrewnicols/d3532a73531297e81fea473402b50f19 to your computer and use it in GitHub Desktop.
Save andrewnicols/d3532a73531297e81fea473402b50f19 to your computer and use it in GitHub Desktop.
Hi all,
After discussion with others in the Integration team, and careful consideration, the decision has been made to close this issue as "Will not fix".
Adding additional database engines to the list of supported engines is an extremely large undertaking. Even if the initial support level appears trivial, it is highly that this will introduce severe limitations to the product, and potential new features.
Whilst SQLite has many benefits, we do not feel that it has the featureset required to support the entire of Moodle LMS product in either its current form, nor potential future features that we introduce int he future. Therefore we cannot entertain adding full SQLite support in this, or any future version of Moodle.
That said, we will of course continue to support SQLite in locations where it is already supported. Notably areas such as the database enrolment, and database authentication plugins.
I will also note that there are already thoughts to remove the ADOdb integration that we currently use and replace it with our own {{moodle_database}} API, and I should imagine that some of the work in this issue will be translated into that project.
Thank you all for your understanding and hard work on this issue.
I will now be closing this issue, as well as all of it sub tasks.
Best wishes,
Andrew Nicols
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment