.schema() causes future queries to not use public schema

[FFX3]

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

If the supabase instance uses a different schema previously, you need to specify .schema("public") to start using the public schema again

To Reproduce

create 2 schemas invoke an rpc from a non public schema and then try to query the public schema without using the schema method.

    #this works
    response = (
        supabase.schema('infra')
        .rpc('claim_pdf_job', { "worker_token": worker_token })
        .execute()
    )

    response = (
        supabase.schema('public').table("dzi_builder_logs")
        .insert({
            "message": 'test',
            "pdf_id": record['pdf_id']
        })
        .execute()
    )

    #this throws a 404 on the second query
        #this works
    response = (
        supabase.schema('infra')
        .rpc('claim_pdf_job', { "worker_token": worker_token })
        .execute()
    )

    response = (
        supabase.table("dzi_builder_logs")
        .insert({
            "message": 'test',
            "pdf_id": record['pdf_id']
        })
        .execute()
    )

Expected behavior

I'd expect the schema to default to public if no specified.

System information

• OS: NixOS
• Version of supabase-py: 2.13.0
• Version of Node.js: v22.14.0

[silentworks]

This was fixed in version 1.0.0 of postgrest-py which is only available from 2.15.0 of supabase-py #1074