Skip to content

Remove explicit schema in postgreschema - #19606

Merged
LordSimal merged 1 commit into
5.xfrom
fix-19604-gis
Aug 28, 2026
Merged

LordSimal merged 1 commit into
5.xfrom
fix-19604-gis

Conversation

@markstory

Copy link
Copy Markdown
Member

Remove the hardcoded public schema from postgis column reflection. Adding a test seemed more complex than it would provide value.

Fixes #19604

Remove the hardcoded `public` schema from postgis column reflection.
Adding a test seemed more complex than it would provide value.

Fixes #19604
@markstory markstory added this to the 5.4.2 milestone Aug 28, 2026
@LordSimal
LordSimal merged commit 39a15f5 into 5.x Aug 28, 2026
15 checks passed
@LordSimal
LordSimal deleted the fix-19604-gis branch August 28, 2026 06:30
type,
srid
FROM public.{$postgisType}_columns
FROM {$postgisType}_columns

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of dropping the hard-coded public shouldn't the $schema argument be used here?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a fair point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

PostGIS schema forced to "public" since v5.4 → custom schema breaks entity creation

3 participants