MHSanaei e8c6c30982 fix(postgres): resync id sequences so adding clients no longer collides ...

resetPostgresSequences hardcoded table names that did not match the models: it used "client_records" (real table is "clients") and "inbound_fallback_children" (real table is "inbound_fallbacks"). For both, pg_get_serial_sequence returned NULL, so the guarded setval was a silent no-op and those id sequences were never advanced past MAX(id) after a SQLite->Postgres migration. The first client added afterward reused an existing id and failed with duplicate key value violates unique constraint "clients_pkey".

Resolve table names from the models via GORM instead of hardcoding, and run the resync on every Postgres startup (initModels) so databases already broken by the previous migration repair themselves on boot.

2026-05-31 23:44:57 +02:00

..

model

feat(fallbacks): add per-rule dest override

2026-05-28 21:17:49 +02:00

db_seed_test.go

test: name temp sqlite db x-ui.db to match the real db filename

2026-05-31 15:25:05 +02:00

db.go

fix(postgres): resync id sequences so adding clients no longer collides

2026-05-31 23:44:57 +02:00

dialect.go

fix(nodes): use GREATEST for last_online merge on PostgreSQL

2026-05-29 02:04:02 +02:00

migrate_data.go

fix(postgres): resync id sequences so adding clients no longer collides

2026-05-31 23:44:57 +02:00