fix(brick_supabase): Fix nullable unique fields causing Supabase .eq() type errors - #672
Open
KiddoV wants to merge 1 commit into
Open
fix(brick_supabase): Fix nullable unique fields causing Supabase .eq() type errors#672KiddoV wants to merge 1 commit into
.eq() type errors#672KiddoV wants to merge 1 commit into
Conversation
KiddoV
commented
Apr 28, 2026
KiddoV
commented
- Supabase .eq() does not accept null
- Brick currently assumes all unique fields are non-null
- Nullable unique fields are valid database design
- Null values should be skipped for filters
|
This PR has been automatically marked as stale due to inactivity. To keep this PR open, you can:
|
Author
|
Will this be merged? |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.