Fix Enum Array Column Types for PostgreSQL Migrations #3759
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.
Fix an issue specific to PostgreSQL migrations, where enum array column types are generated without the schema prefix. This omission leads to invalid SQL statements that cannot be executed properly.
Current Behavior:
Generated migrations for enum array columns omit the schema prefix. For example:
Expected Behavior (Post-Fix):
Enum array columns correctly include the schema prefix, ensuring valid SQL generation:
Schema Structure:
Below is a simplified version of the schema used for generating the migrations:
Related to: #3278