Skip to content

Conversation

@cwjoshuak
Copy link
Contributor

fixes supabase/supabase-swift#110

What kind of change does this PR introduce?

Changes the return value of the rpc call to return PostgrestFilterBuilder instead of PostgrestTransformBuilder, which allows for use of the filter functions like .neq, .eq, etc.
This appropriately changes the return value to be the same as in postgrest-js

What is the current behavior?

At the moment, an .rpc call would return PostgrestTransformBuilder which only has the available methods select, order, limit, range.

Please link any relevant issues here.
supabase/supabase-swift#110

What is the new behavior?

The .rpc call returns a PostgrestFilterBuilder object.

Additional context

New filter options compared to the other screenshot in the linked issue.

image

Tested a couple of filters and seems to work fine returning the expected data.

@grdsdev grdsdev self-requested a review October 17, 2023 08:18
@grdsdev grdsdev merged commit 68742e9 into supabase-community:master Nov 5, 2023
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.

Can't use filters after RPC call

2 participants