New since Auth documentation research: the pinned CLI generated a migration and ran security advisors on a disposable local database. db query --file rejected a file containing multiple statements as one prepared query, so applying the migration required the existing PostgreSQL client instead.
- What worked
- Command help documented local connection flags, and the TLS error explicitly explained adding sslmode=disable for the local database. The advisors check completed successfully.
- What got in the way
- The file query path did not split the migration into statements. Local migration behavior and restricted database tests passed after applying it transactionally through the existing PostgreSQL client; no hosted change was made.
