Question: Is users_sessions table created or renamed from another table?

[spiral lynx]

Can somebody help me understand this?
This log happens when I enter /admin for the first time.
I installed Payload on my existing Next.js project that uses Supabase.
The log listed 3 tables from my Supabase public schema (yokohama, profiles, and tokyo).
What am I supposed to do in this process?

 ○ Compiling /admin/[[...segments]] ...
 ✓ Compiled /admin/[[...segments]] in 5.7s (4418 modules)
[✓] Pulling schema from database...

Is users_sessions table created or renamed from another table?
❯ + users_sessions                  create table
  ~ yokohama_table › users_sessions rename table
  ~ profiles › users_sessions       rename table
  ~ tokyo_table › users_sessions    rename table

[copper peak]

New Community-Help Thread Created!

Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:

Documentation:

• Managing User Preferences
• SQLite - Drizzle schema hooks - beforeSchemaInit
• Postgres - Drizzle schema hooks - beforeSchemaInit

Community-Help:

• Payload w/ Supabase Auth
• GET accessToken with payload-plugin-oauth
• GraphQL access control check failing via local API
• [The following path cannot be queried: status","data":[{"path":"status"}]}]](https://payloadcms.com/community-help/discord/the-following-path-cannot-be-queried-status-data-path-status)

[spiral lynx]

Note that I have been through this road before and I ended up wiping all my existing tables in Supabase.

What to do so that the existing tables stay the same?

[spiral lynx]

I ended up exited out from that and went back to payload.config.tf to specify schemaName according to this docs:
https://payloadcms.com/docs/database/postgres#options

It seems to be a good choice to separate payload to a different schema. I'll go with this for now 🙂

[tough wave]

After v3.44.0 (https://github.com/payloadcms/payload/releases/tag/v3.44.0) the local auth changed to auth sessions. If you use existed db from older version, the migration is needed. Or you can opt-out new default behaviour.