Skip to content

Use new entitySchema field for Postgres migrations#7

Merged
curranosaurus merged 1 commit intocurran/use-schema-in-postgresql-queriesfrom
curran/use-schema-in-postgres-migrations
Oct 3, 2024
Merged

Use new entitySchema field for Postgres migrations#7
curranosaurus merged 1 commit intocurran/use-schema-in-postgresql-queriesfrom
curran/use-schema-in-postgres-migrations

Conversation

@curranosaurus
Copy link
Copy Markdown
Owner

This updates the migrations code. In particular, if you manually set a table schema, we're going to prepend the CREATe TABLE statement with a CREATe SCHEMA IF NOT EXISTS statement. That's going to lead to some duplication in the migrations, but it is a lot easier than tracking the "lifetime" of the schema name inside the migration file. Persistent already uses a bit of a hack to make sure that all tables exist before fkey references are declared, so there isn't any prior art for managing this kind of thing.

I tested this by hardcoding table schemas to "foo". It didn't break any tests, so presumably the migrations & queries are working well with each other.

@curranosaurus curranosaurus merged commit b96c415 into curran/use-schema-in-postgresql-queries Oct 3, 2024
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.

2 participants