personal-user-foundation

Database migration for account discrimination initializes schema and triggers in PostgreSQL and Supabase to distinguish between personal and company users. This foundation supports user profile management hooks and authentication wiring.

Account type discrimination is the process of differentiating personal users from company users at the database level. You need it during Phase 1 or Phase 2 of personal user plan implementation when your application requires separate profile management and authentication logic for each user type.

You wire personal user authentication by defining TypeScript data types for user information and implementing dedicated hooks and services. This authentication wiring integrates directly with your Supabase database setup to manage personal user profiles securely.

Yes, you need both PostgreSQL and Supabase for database operations to implement the personal user foundation. Supabase handles the backend infrastructure, while PostgreSQL executes the database migration and triggers necessary for account type discrimination.

The best way to bootstrap personal user account infrastructure is running the development server via npm run dev. This initializes the TypeScript environment to define data types, implement hooks, and set up database migration for personal user profiles.

Database triggers are required for account discrimination because they automatically enforce the distinction between personal and company users at the database level. This ensures data integrity when managing user profiles and routing authentication logic during Phase 1 or Phase 2 implementation.