Problem/Motivation

PostgreSQL does not like it when a database query fails, because the table in the query does not exist. We are now making it work adding a database save point around every database query. We are removing those save points in #3615690: Removal of unnecessary savepoints from PostgreSQL.

Proposed resolution

Make sure that the table has been created before running a database query on the table.

Remaining tasks

TBD

User interface changes

TBD

Introduced terminology

TBD

API changes

TBD

Data model changes

None

Release notes snippet

TBD

Issue fork drupal-3626977

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

daffie created an issue. See original summary.

daffie’s picture

daffie commented
Assigned: Unassigned » daffie

daffie opened merge request !17298

daffie’s picture

daffie commented
Status: Active » Needs review
Parent issue: » #3615690: Removal of unnecessary savepoints from PostgreSQL
daffie’s picture

daffie commented
Assigned: daffie » Unassigned
daffie’s picture

daffie commented
Priority: Major » Critical

This issue is blocking #3615690: Removal of unnecessary savepoints from PostgreSQL and that issue is critical, therefore this issue is also critical.

longwave’s picture

longwave
he/him
Primary language English
Location UK
commented

Posted an alternative approach over in #2371709-187: Move the on-demand-table creation into the database API which adds new API for lazy table creation across all database drivers.