Analyze the error message and the API response to diagnose the issue. The error message indicates a foreign key constraint violation when inserting or updating data in the 'employees' table, specifically referencing the 'profiles' table. The API response suggests a problem with the 'employee_id' foreign key. Investigate why the 'employee_id' from the 'employees' table does not match any primary key in the 'profiles' table. Review the database schema to confirm the relationship between the 'employees' and 'profiles' tables, ensuring the 'employee_id' in 'employees' correctly references the primary key (likely 'id') in 'profiles'. Examine the sign-up and sign-in processes to ensure user data, including the user's ID, is correctly created and linked to the 'employees' table upon successful registration. Verify that the user's ID from the 'profiles' table is being correctly used as the 'employee_id' when creating a new employee record. If the user data is not being stored in the 'profiles' table after sign-up and login, check the database triggers or functions responsible for inserting data into the 'profiles' table. Confirm that these triggers or functions are correctly configured to execute after a successful sign-up and login, and that they correctly retrieve and store the necessary user information. Ensure that the user's ID from the 'profiles' table is being correctly used as the foreign key in the 'employees' table. Review the code responsible for fetching and displaying data after authentication. Confirm that the correct user ID is being used to retrieve user-specific data from the 'profiles' table. If the user's profile data is not being displayed, check the database queries and ensure they are correctly filtering data based on the authenticated user's ID. Implement robust error handling throughout the authentication and data storage processes to catch and address potential issues. Provide detailed logging to track the flow of data and identify the source of the problem. Test the sign-up, sign-in, and data retrieval processes thoroughly to ensure data integrity and user experience.

-- Fix the database schema relationships-- The key insight: employees and system users are different entities-- First, let's clean up any existing problematic constraintsALTER TABLE employees DROP CONSTRAINT IF EXISTS employees_employee_id_fkey;ALTER TABLE employees DROP CONSTRAINT IF EXISTS employees_created_by_fkey;-- Ensure the employees table has the correct structure-- employee_id should NOT be a foreign key to profiles-- created_by should reference auth.users(id) for audit purposesALTER TABLE employees   ALTER COLUMN employee_id TYPE TEXT,  ALTER COLUMN created_by TYPE UUID;-- Add the correct foreign key constraint for created_byALTER TABLE employees   ADD CONSTRAINT employees_created_by_fkey   FOREIGN KEY (created_by) REFERENCES auth.users(id) ON DELETE SET NULL;-- Remove any incorrect foreign key on employee_id-- employee_id is just a business identifier like "EMP001", not a database foreign key-- Ensure the profiles table is correctly structuredCREATE TABLE IF NOT EXISTS profiles (  id UUID REFERENCES auth.users(id) ON DELETE CASCADE PRIMARY KEY,  email TEXT,  full_name TEXT,  avatar_url TEXT,  role TEXT DEFAULT 'user',  created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW(),  updated_at TIMESTAMP WITH TIME ZONE DEFAULT NOW());-- Ensure the employees table is correctly structuredCREATE TABLE IF NOT EXISTS employees (  id UUID DEFAULT gen_random_uuid() PRIMARY KEY,  employee_id TEXT UNIQUE NOT NULL, -- Business ID like "EMP001"  full_name TEXT NOT NULL,  email TEXT UNIQUE NOT NULL,  department TEXT NOT NULL,  position TEXT NOT NULL,  phone TEXT,  avatar_url TEXT,  status TEXT DEFAULT 'active' CHECK (status IN ('active', 'inactive')),  hire_date DATE DEFAULT CURRENT_DATE,  created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW(),  updated_at TIMESTAMP WITH TIME ZONE DEFAULT NOW(),  created_by UUID REFERENCES auth.users(id) ON DELETE SET NULL -- Who added this employee);-- Optional: Create a linking table if some employees are also system usersCREATE TABLE IF NOT EXISTS employee_user_links (  id UUID DEFAULT gen_random_uuid() PRIMARY KEY,  employee_id UUID REFERENCES employees(id) ON DELETE CASCADE,  user_id UUID REFERENCES auth.users(id) ON DELETE CASCADE,  created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW(),  UNIQUE(employee_id, user_id));-- Enable RLS on the new tableALTER TABLE employee_user_links ENABLE ROW LEVEL SECURITY;-- Create policy for the linking tableCREATE POLICY IF NOT EXISTS "Authenticated users can view employee links"   ON employee_user_links FOR SELECT TO authenticated USING (true);CREATE POLICY IF NOT EXISTS "Authenticated users can manage employee links"   ON employee_user_links FOR ALL TO authenticated USING (true);-- Clean up any bad dataDELETE FROM employees WHERE created_by IS NOT NULL AND created_by NOT IN (SELECT id FROM auth.users);-- Verify the schema is correctDO $$BEGIN  -- Check that employee_id is TEXT and not a foreign key  IF EXISTS (    SELECT 1 FROM information_schema.table_constraints tc    JOIN information_schema.key_column_usage kcu ON tc.constraint_name = kcu.constraint_name    WHERE tc.table_name = 'employees'     AND kcu.column_name = 'employee_id'     AND tc.constraint_type = 'FOREIGN KEY'  ) THEN    RAISE EXCEPTION 'employee_id should not be a foreign key!';  END IF;    RAISE NOTICE 'Schema verification passed: employee_id is correctly a TEXT field';END $$;ERROR: 42601: syntax error at or near "NOT"LINE 65: CREATE POLICY IF NOT EXISTS "Authenticated users can view employee links" these are the errors i cannot add employees in my supabase fix it