Connection Fields by Database Type
The connection editor renders the fields that actually apply to the database you pick, with the label each engine uses. A generic "Database" box is wrong for most engines, so the form adapts: pick a type and the right fields appear.
What the "database" slot means per engine
| Engine | Field | Meaning |
|---|---|---|
| PostgreSQL, SQL Server, MySQL/MariaDB | Database | The database / catalog (for MySQL, schema and database are the same). |
| Oracle | Service Name / PDB | The Oracle service name used to connect (EZConnect host:port/service). For a pluggable database this is the PDB, e.g. FREEPDB1. It is not a schema, in Oracle a schema is a user, so it never appears in the schema list. Use an account with access to ALL_USERS to browse schemas. |
| SQLite | Database File Path | Filesystem path to the .db/.sqlite file (or :memory:). No host or credentials. |
| MongoDB | Auth Database | The database your credentials authenticate against (default admin). A full Connection String field is also offered and overrides the host/port/auth fields. |
| Redis | Database Number | The numeric DB index (0-15 by default). |
Required vs. optional
Only the fields a connection cannot be built without are required, host (for networked engines), Oracle's Service Name, and SQLite's file path. Username and password are optional, because trust / integrated / no-auth setups are valid; a bad credential surfaces the driver's real error when you Test or connect rather than being pre-guessed by the form. Advanced, driver-honored options (SSL mode, timeouts, SQL Server encryption) live under the advanced/additional-parameters area and only appear for engines that honor them.