-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
removing rows on backend table does not replicate to client table #2293
Comments
Hi @cakir-enes - can you provide an example of the code where you're trying to remove records, so we can help you? |
+1 for this, when I noticed it ages ago it could be repoed by creating a table in python, connect web viewer, asyncio.sleep for 30 seconds table.remove([key]) in python. Observe that they key still exists in Web viewer. I'll see if I can get something specific next week. It seemed to me that the ws protocol couldn't really deal with deletes. Fyi a workaround is to have a second ws and manually call remove in javascript on the table... |
As promised too long ago, notice that data is updated and added OK and the ws is sending something on delete. The workaround is to add a second ws and just send messages to your own js code to call delete in javascript... As a side note this might make a good example for new developers as its quite hard to get started on the whole thing otherwise...
|
Not sure if this is the expected behavior, but following this guide https://perspective.finos.org/docs/server/#clientserver-replicated the replica table on client, which is derived by a view that backed by the backend table does not propagate removes.
Is this the expected behavior?
version
2.3.1
, backend :python fastapi
The text was updated successfully, but these errors were encountered: