What problem did you meet?

I’ve been integrating Supabase with my app by following this guide:
https://blog.logto.io/integrating-with-supabase

However, I just noticed that starting April 21, Supabase is introducing restrictions on SQL actions in the auth, storage, and realtime schemas (see announcement).

Since my current setup involves custom functions under the auth schema (e.g., auth.user_id()), I’m concerned this change will break the integration. Could you please clarify:
1. How should I migrate these custom functions (e.g., auth.user_id) to work under the new restrictions?
2. Should I move them to the public schema or a separate custom schema? Will that still work with Logto’s integration?
3. Are there any recommended practices for maintaining compatibility with both Supabase and Logto moving forward?

Describe what you'd like Logto to have

Clear guidance on how to adjust Supabase integration when custom functions can no longer reside in the auth schema — including recommended alternatives that remain compatible with Logto.