fix: handling of type identifier in column create() and update() #181
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Can you please review, @kiwicopple, @soedirgo , @w3b6x9 |
|
This is great, thanks @DukeManh! |
soedirgo
approved these changes
Feb 8, 2022
|
🎉 This PR is included in version 0.33.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What kind of change does this PR introduce?
Fix issue 5330 of Supabase Upstream.
What is the current behavior?
Updating column data type from
typetotype[]fails because of insufficient identifier escaping in columcreateandupdatefunction.Additional context
This is actually a TO-DO so it's safe to delete the Todo comment now :).