What's the recommended way to get around caches (both browser + nginx) when the server does schema changes?

[mwildehahn]

During development I've been adjusting the schema for models in the db but the client is getting cached results from the browser when making requests. I can set the cursor value to get around this but I'm curious if there is some best practice here. For example, does it make sense to treat cursor as a "version" string, so when the schema changes, we can change the cursor and ensure we get through the cache?

[KyleAMathews]

Are you using a custom client? Adjusting to schema changes is handled automatically normally. E.g. cursor shouldn't be manually set.

[mwildehahn]

Yea, I'm using it in an ios app so I have a swift client that hits my API which then hits electric via an nginx proxy. I return the headers from electric to the client so I think what's happening is ios has some network cache that is caching the response.

if i do:

• /v1/shape?table=activity&offset=-1
• schema change on the backend
• /v1/shape?table=activity&offset=-1

i believe that last request isn't making it to the server since it's just getting cached on the client?

[KyleAMathews]

Ah ok, so a custom client. We need to write a "write your own client guide" sooner than later as there's some nuance here.

You're right about the cursor being important — it's our cache buster to ensure that requests that need to get to the server do. See the PR that added it #1826

[KyleAMathews]

You might want to have a strong AI model e.g. gpt5 or Claude Opus compare the typescript client & your swift client to see if there's anything else that might need added.

[mwildehahn]

Got it, will do! Yea, that guide would be awesome!

…

On Sun, Aug 31, 2025 at 1:21 PM Kyle Mathews ***@***.***> wrote: You might want to have a strong AI model e.g. gpt5 or Claude Opus compare the typescript client & your swift client to see if there's anything else that might need added. — Reply to this email directly, view it on GitHub <#3077 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFMAULVWKK4TWMXJZFUJPL3QNKLZAVCNFSM6AAAAACFIK2FFSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMRWHE4DKMQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>