pgsql module's NonPublicSchemaTest can fail in non-CI environments

Created on 29 December 2023, 8 months ago
Updated 18 February 2024, 7 months ago

Problem/Motivation

Non-public schema testing for Postgres appears to depend on the database configuration allowing on-the-fly schema creation or... something like that? Ensure the schema exists before testing it.

Steps to reproduce

Working on an issue that makes changes to code invoked by NonPublicSchemaTest::testIndex(). Went to re-create it locally and got:

Invalid schema name: 7 ERROR: schema "testing_fake" does not exist

Seems that there's something different about the pgsql server's configuration or whatever on CI vs. locally that allows for the non-standard schema name to be used on the fly.

Proposed resolution

Ensure the testing schema is present.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

πŸ› Bug report
Status

Fixed

Version

10.2 ✨

Component
DatabaseΒ  β†’

Last updated less than a minute ago

  • Maintained by
  • πŸ‡³πŸ‡±Netherlands @daffie
Created by

πŸ‡ΊπŸ‡ΈUnited States bradjones1 Digital Nomad Life

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024