1
Postgres Realtime Querying hydration and commonality to postgREST
Source: supabase/supabase#14031 · opened by @Towerful
Hello, I would love to see some better hydration options for Postgres Realtime. Would it be possible for a successful connection to also return an initial data set? Alternatively, is there a way to use the supabase-js query builder to return the RealtimePostgresChangesFilter object? so supabase.from('users').select('name').eq('id', 1).toRealtime('*') might return {event: '*', schema: 'public', table: 'users', filter: 'id=eq.1'} This would allow something like: or, perhaps, the result of the await-ed query would have an additional realtime property that would include the information. e.g ---------------- I realise that this breaks down when dealing with multiple relations and complex queries. Using the 2nd method above (after a successful query) might allow for auto-generation of multiple realtime filters, however the complexity would very quickly explode. It might wo…
No pledges yet. Be the first to back this.
Comments
Similar requests
Custom query parameter on postgrest-js
4 votes · 0 comments
Introducing supabase to the Haskell ecosystem
9 votes · 0 comments
Make Changes to the DB through a Realtime extension
2 votes · 0 comments
Allow configuring PostgREST pool and pooler in Supabase CLI (api.db_pool, api.use_pooler)
1 vote · 0 comments
Compression Issue with ‘application/vnd.pgrst.object+json’ Content-Type in PostgREST Responses
3 votes · 0 comments
No comments yet.