Skip to content

Change update case to use writeUpsert method#2

Merged
nathanstitt merged 1 commit intonathanstitt:mainfrom
ravikumarmistry:ravikumarmistry-patch1
Jan 4, 2026
Merged

Change update case to use writeUpsert method#2
nathanstitt merged 1 commit intonathanstitt:mainfrom
ravikumarmistry:ravikumarmistry-patch1

Conversation

@ravikumarmistry
Copy link
Copy Markdown
Contributor

Pocketbase can send update event but it does not mean it is a update operation for local tanstackdb, Due to Api Rules of Pocketbase there are chances where Initialload miss the data but leter Pocketbase record setisfy the Api rules and recived as update operation.

In such cases it should not throw error but digest the event as create.

Pocketbase can send update event but it does not mean it is a update operation for local tanstackdb, Due to Api Rules of Pocketbase there are chances where Initialload miss the data but leter Pocketbase record setisfy the Api rules and recived as update operation.

In such cases it should not throw error but digest the event as create.
@nathanstitt
Copy link
Copy Markdown
Owner

Thanks for the update @ravikumarmistry - just so I understand the issue, does this occur when a subscription sends a record that tanstack DB doesn't yet know about? If so, I think I've seen that in some cases as well.

@ravikumarmistry
Copy link
Copy Markdown
Contributor Author

Yes

@nathanstitt
Copy link
Copy Markdown
Owner

awesome, thank you very much!

@nathanstitt nathanstitt merged commit 4edeeb5 into nathanstitt:main Jan 4, 2026
2 checks passed
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.

2 participants