371021d3c0
Issue: Foreign key constraint violation when creating reports - reports.created_by referenced practitioners.id - Code was storing auth.uid() instead of practitioner.id - Demo practitioners have user_id: null (no auth link) Solution (prototype): - Drop FK constraints on created_by and updated_by - Store auth user ID directly without constraint - Added migration: 20251123_fix_reports_created_by_constraint.sql Note: In production, populate practitioners.user_id and restore FK constraints for proper data integrity. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.