@jamoran1356@kiwicopple@tannerlinsley AFAIK it roll backs on error. Reconnect behaviors are part of a offline-first approach, which is not yet supported by the Supabase adapter (working on it). You can try using the other adapters (Electric, Powersync, RxDB), it sounds they fit your usecase better.
@jamoran1356@kiwicopple@tannerlinsley AFAIK TanstackQuery has its cache (which is GCed/refetched accordingly). The results are then copied and deduped in separate TDB cache, which is used for optimistic mutations, rollbacks and realtime updates.
@mhsnook@kiwicopple@tannerlinsley Yes, thatβs because of the βon-demandβ sync mode. AFAIK it assumes queries donβt overlap each other, so it just refetches.
For the behavior you described, weβd need βeagerβ mode. We donβt support that yet, since itβs usually paired with offline storage (which we're working on).
@jamoran1356@kiwicopple@tannerlinsley This is online-only for now, it refetches the data on each refresh. Think of it as ReactQuery with realtime updates.
we just shipped @ππππππππ-ππππ/ππππππππ-ππ
β live queries
β optimistic mutations
β automatic Realtime sync
β fully typed
shout out to @tannerlinsley - a very impressive framework. Currently in alpha:
@naelodev@dshukertjr@supabase@convex Realtime updates would be very hard to achieve with next-safe-action, but very doable with Tanstack DB, that's why we decided on supporting it.
@naelodev@dshukertjr@supabase@convex next-safe-action is a library if you're going the SSR route for your app - you POST to your server, it figures out what to render and sends it back in RSC format. Tanstack DB is a client-side pattern similar to ReactQuery, where you hold all data in memory and render from there.
Launching @supabase-labs/tanstack-db, a TanStack DB collection adapter backed by Supabase.
It supports live queries, optimistic mutations, automatic Realtime sync, and is fully typed.
Currently in alpha. Try it out, and let us know any feedback!
Official Tanstack DB collection adapter from Supabase is here!
It connects queries, mutations, and Realtime subscriptions so your UI stays in sync with Postgres!
Try it out today: npm i @supabase-labs/tanstack-db
Supabase Select is back!
October 2 in San Francisco.
Our user conference for builders, teams, and the open source community.
Registration is now open.
https://t.co/iTHLK4DIZp
@tannerlinsley why's there no queryClient.fetchMutation for imperative mutations? I'm trying to use mutationOptions with cache invalidation in onSuccess.
Supabase has raised $500M at a $10B valuation
In this round we are giving @supabase employees the opportunity to cash out 25% of their vested options. We have done this in every round since inception.
We do it as a βcashless transactionβ so that employees donβt need to front any cash to exercise their options. This is the friendliest way we could design it until we can offer RSUs.
On top of that, we give employees a 10 year exercise window: whether they stay or leave the company. The typical/default window is 3 months. IMO, equity is earned and employees shouldn't be penalized because they don't have the cash to exercise within 3 months of leaving a job (often that's the time they need the cash/certainty the most).