Why do I need to provide schema for realtime subs?

It seems supabase clients are schema-specific; why do I need to provide the schema a second time when creating a subscription, like in this example from the docs [1]

supabase
  .channel('public:countries')
  .on('postgres_changes', { event: 'DELETE', schema: 'public', table: 'countries' }, payload => {
    console.log('Change received!', payload)
  })
  .subscribe()

supabase
  .channel('public:countries')
  .on('postgres_changes', { event: 'DELETE', schema: 'public', table: 'countries' }, payload => {
    console.log('Change received!', payload)
  })
  .subscribe()

[1] https://supabase.com/docs/reference/javascript/next/subscribe

Supabase•4y ago•

1 reply

ixxie

Why do I need to provide schema for realtime subs?

It seems supabase clients are schema-specific; why do I need to provide the schema a second time when creating a subscription, like in this example from the docs [1]

supabase
  .channel('public:countries')
  .on('postgres_changes', { event: 'DELETE', schema: 'public', table: 'countries' }, payload => {
    console.log('Change received!', payload)
  })
  .subscribe()

supabase
  .channel('public:countries')
  .on('postgres_changes', { event: 'DELETE', schema: 'public', table: 'countries' }, payload => {
    console.log('Change received!', payload)
  })
  .subscribe()

[1] https://supabase.com/docs/reference/javascript/next/subscribe

Why do I need to provide schema for realtime subs?

Similar Threads

Why do I need to provide schema for realtime subs?

Similar Threads

Similar Threads

Similar Threads