aozora_d

I think each has advantages and disadvantages. Clerk is great for fast movement - because there are lots of built-in functionalities out there - organizations, permissions, and billing ones. Whereas supabase gives us more control and essentially it's cheaper at scale than Clerk. Especially if the codebase uses supabase now, I think it's good to keep use the supabase. We can do everything according the project's logic with powerful supabase functions.

I think you're trying to pass a PublicBackgroundJobInsert type to the `.insert()` method, but the method signature expects JSON type. This is a common type mismatch with Supabase's generated types.

When a user signs in with Google, their email is managed by the OAuth provider, so you cannot change it directly through Supabase. If the user lost access, need to create new account, and migrate user data from original database manually. I hope this helps you 🙂

You can do this easily - enable the moddatetime extension manually from the Supabase **Dashboard** > **Database** > **Extensions**, or run this once in the SQL editor as the admin: `CREATE EXTENSION IF NOT EXISTS moddatetime SCHEMA extensions;`