Fix creation of the database enum when using a non-default space #17
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, if a non-
nil
jobsTableSpace
was provided to theJobModelMigration
when using PostgreSQL, the job state enum type was incorrectly created in the default schema instead of alongside the jobs table. This is now fixed, and the name of the space is no longer used to prefix the names of the enumeration or the index on the table. The migration'srevert(_:)
method will attempt to drop the old name from the default space (usingIF EXISTS
) in order to maintain compatibility.Additional changes:
Package.swift
no longer importsFoundation
to get at the current environment (I learned thatContext.environment
exists).