You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Electric recently merged electric-sql/electric#2044 to consistent sort query params to maximise cache hits. I have an example app with pure Electric and PGlite components in the same page. I noticed that the PGlite sync requests have params in a different order to the pure Electric requests:
I'm aware that I'm using electric from the ppm workspace and PGlite as a versioned deployment:
It does use the code Electric client internally, so I suspect this is version thing... we'll double check. It's probably bringing in the published version with then runs in parallel along side the workspace one.
Electric recently merged electric-sql/electric#2044 to consistent sort query params to maximise cache hits. I have an example app with pure Electric and PGlite components in the same page. I noticed that the PGlite sync requests have params in a different order to the pure Electric requests:
I'm aware that I'm using electric from the ppm workspace and PGlite as a versioned deployment:
So this may just be a versioning thing but I'm guessing the PGlite sync doesn't use the Typescript client under the hood (or does it)?
The text was updated successfully, but these errors were encountered: