Inquiry about primary key support for Views — update operations not recognized in subscriptions

Hi SpacetimeDB team,

I'm using SpacetimeDB for real-time game state sync, and I've run into an issue with View subscriptions: because Views lack primary keys, the client SDK can't pair insert+delete operations as updates. This means onUpdate callbacks never fire—we only get separate insert and delete events.

I understand Views currently don't support primary keys by design, and I've heard there might be plans to add this in the future. Could you share:

1. Is primary key support for Views still on the roadmap? Any rough timeline or current status?
2. If it's not coming soon, do you have any recommended workarounds for subscription scenarios that need proper update detection?

My use case involves pushing aggregated multi-table data via Views to clients, where distinguishing actual updates (vs. separate insert/delete pairs) matters for smooth gameplay.

This limitation is currently blocking a clean implementation for real-time game state sync. I'd really love to see primary key support for Views land soon—it would make Views truly viable for reactive applications. Fingers crossed it's high on the priority list! 🙏

Thanks for your work on SpacetimeDB—appreciate any insight you can share! 😊

The issue discusses primary key support for Views and update detection in subscriptions, but names no files, tests, or implementation entry points. Start by confirming the current roadmap and investigating the requested workaround; done would require a decided implementation scope or documented guidance for subscription update handling.