Add dynamic schemas on a per-query basis

[sjones6]

Resolves supabase/postgrest-js#280

What kind of change does this PR introduce?

Feature

What is the current behavior?

Currently, the supabase client is created and defaults to the public schema when no option is supplied:

createClient(supabaseUrl, supabaseKey)

Or, you can supply an alternative schema:

createClient(supabaseUrl, supabaseKey, {
  db: {
    schema: 'alternative'
  }
})

However, this means that all methods/queries for the client are associated to the single schema. Using multiple schemas requires multiple clients, which presents a challenge for auth where all clients need to be authenticated.

See pre-existing issue:

supabase/postgrest-js#280

What is the new behavior?

Extends on behavior added to underlying PostgrestClient: supabase/postgrest-js#455

The method added to the supabase client allows for dynamic schema selection on a per-query basis.

const supabase = createClient(supabaseUrl, supabaseKey);

supabase.from('some_table_in_public').select();

supabase.schema('alt').from('table_in_alt').select()

If a Database generic type is supplied, type inference works as expected without additional generics:

Additional context

Add any other context or screenshots.

[dshukertjr]

Thanks for the feedback! We do have an issue discussing a solution for this here supabase/postgrest-js#280 . We will pick this one post launch week. Thanks for your patience!

[soedirgo]

Thanks @sjones6! We'll need the change both here and in postgrest-js, so keeping this open.

[sjones6]

@soedirgo , updated this PR now that supabase/postgrest-js#455 is published.

[sjones6]

Copied from postgrest-js. Didn't bring over the the whole database setup that postgrest-js has, since that seems like a lot for this change.