-
-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question]: Does this work with a self hosted postgrest server (no supabase account)? #503
Comments
hey! Sure, self hosted should work as long as you have the rest api enabled. cache helpers is really just a wrapper around the supabase client. if the cache updates are not working, could you provide a more focussed report? |
Hi @psteinroe thanks so much for the repsonse! I ended up switching it over to react query as the debugging tools were more robust - below is as far as I have gotten. Please let me know what specifics I can provide you in addition to the below. What seems to be happening is that the mutation methods are not correctly receiving a cache key. In this simple example you can see react query is properly receiving and caching the GET of my tasks. Now once I trigger the insert logic the mutation is registered by react query but without a cache mutationKey. The mutation is set up as the following
Obviosuly this is not going to merge to the original query data without the proper mutationKey but I am at a loss for why the Thanks for you help in advance! Below are my dependency versions
|
What I did notice is that cache helpers requires |
Apologies if this is the incorrect place to ask.
I have a simple example component and DB spun up using a self hosted postgrest server where I am trying to test out the auto cache update functionality for an insert and update mutation however I cannot seem to get it working.
Would it be expected the following example works? Or is it required I have a supabase project and connect to that?
Postgest Client
Simple component (clicking the button does not update the table or the rendered list of titles)
The text was updated successfully, but these errors were encountered: