- Issue created by @daffie
Supporting the PostgreSQL database by Drupal Core is delaying improvements in Core and in Starshot. Think of JSON support in Core and the Experience Builder in Starshot. Moving the database driver for PostgreSQL to contrib will solve this problem. The pgsql module in Core just gets too little love and is stagnating itself and Core.
We can just move the pgsql module to contrib and when we only do that the module wither away. The tests in the module cover just a tiny bit of the functionality of the module. To keep the module up to date and even flourish the module needs more help. The things that are needed are:
An example for PostgreSQL specific functionality in core is the helper method Drupal\Core\Entity\ContentEntityStorageBase::cleanIds()
. The problem is that something a fix in Drupal core is needed to make it work for a specific database.
I (@daffie) am willing to become the maintainer for pgsql module in core when it is set up for succes.
Active
11.0 🔥
postgresql db driver
It is used to alert the product manager core committer(s) that an issue represents a significant new feature, UI change, or change to the "user experience" of Drupal, and their signoff is needed. If an issue significantly affects the usability of Drupal, use Needs usability review instead (see the governance policy draft for more information).
It is used to alert the release manager core committer(s) that an issue significantly affects the overall technical debt or release timeline of Drupal, and their signoff is needed. See the governance policy draft for more information.