<@!336983535074279444> thx, got a "Success. No ro...
# off-topic
c
@User thx, got a "Success. No rows returned". but DELETEs still not firing. It there another step?
g
You likely don't want replica identity full, that just returns all of the data for the deleted record. Realtime deletes get sent to everyone (no RLS applied) so normally you just want the primary key which is returned.
Your problem likely lies elsewhere.
Do updates/inserts work? Do you have replication turned on for deletes and the table you are using selected?
c
YES Both insert and update do work
g
Without replica identity you just don't get all the row returned which is normally what you want as RLS will not apply to delete
c
Ok, so I understand I don't need replica identity, but any idea why my DELETEs do fire the console.log? Adds and udpates through sb website trigger, but deletes do not?
g
You have delete toggled on in the replication UI?
c
yes
g
RLS should not matter for deletes... hmmm
c
BTW, what is the reset for 'alter table "your_table" replica identity full;' ?
g
I think identity DEFAULT
c
that was correct.
g
Your js looks ok. You could check the websocket on the network tab I guess to see if you get a delete back and something on the client is going wrong.
c
thanks for the help. I didn't find answer yet, but seemingly without code change none are firing now. nice.
g
are you saying no events are coming back now?
c
correct
g
maybe default was not correct change it back to full and see if they start working again.
c
default is correct (shows in a dropdown on typing). Changed it back to full, restarted dev server, still nothing. It doesn't make sense. I will leave it for now and come back later. Thanks.