fix: add migration for missing ai_settings columns

Browse Source

The original migration only created the table with id/userId/apiKey.
All provider keys, models, toggles, and feature flags were in the
schema but never added to the database, causing every AI settings
save to fail with a Prisma column-not-found error.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

...

This commit is contained in:

Gitead

2026-06-09 23:46:52 -04:00

parent facf9e79e2

commit 949e64c129

10 changed files with 111 additions and 16650 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

2327

apps/Backend/backups/dental_backup_1776124800085.sql

File diff suppressed because one or more lines are too long

4152

apps/Backend/backups/dental_backup_1776211200056.sql

File diff suppressed because one or more lines are too long

2213

apps/Backend/backups/dental_backup_user1_1775952000048.sql

File diff suppressed because one or more lines are too long

2213

apps/Backend/backups/dental_backup_user2_1775952000270.sql

File diff suppressed because one or more lines are too long

2213

apps/Backend/backups/dental_backup_user3_1775952000425.sql

File diff suppressed because one or more lines are too long

2213

apps/Backend/backups/dental_backup_user4_1775952000559.sql

File diff suppressed because one or more lines are too long