fix(postgres): honour a URL's options, and each server's own sslmode - #258

URL options were dropped. ?options=-c default_transaction_read_only=on -c statement_timeout=… is how a connection string asks for session settings. psql, pg_dump and libpq clients honour it, but Laravel's connector builds its own DSN with no place for it, so DBDiff dropped it. A source made read-only through its URL, the usual guard on a production connection, was an ordinary session for DBDiff.

Now each -c name=value (or --name=value) is applied with set_config() as soon as the connection is made, with the values bound, and again when a connection is rebuilt for another schema. PostgresSessionOptions::parse follows libpq's quoting rules (backslash escapes, dashes for underscores). When DBDiff runs pg_dump, it passes the same settings through PGOPTIONS.

sslmode applied to both servers. The source URL's sslmode was applied to both connections, and the target URL's own was ignored. Each server now keeps its own. --supabase and --sslmode only fill in where a URL doesn't name one.

Tests

• tests/Unit/PostgresSessionOptionsTest: parsing, and per-server sslmode/options from toServerAndDb.
• UrlSessionOptionsPostgresTest: on a live server, the source session reports the URL's default_transaction_read_only=on and statement_timeout, the target keeps its own, and the settings survive useSchema().
• Both fail on master. Related suites (DsnParser, connection config, CLI getter, diff command) pass: 83 tests.

🤖 Generated with Claude Code