anchor.diff:  The lack of JMX support is a natural consequence of running in native and is unlikely to be resolved.
   The integration with OCI could be resolved, if you need it we suggest opening a support request with the MySQL Connector/J maintainers.
   
  -=== Microsoft SQL Server
  -
  -Microsoft SQL Server takes a connection URL in the following form:
  -
  -`jdbc:sqlserver://[serverName[\instanceName][:portNumber]][;property=value[;property=value]]`
  -
  -Example:: `jdbc:sqlserver://localhost:1433;databaseName=AdventureWorks`
  -
  -The Microsoft SQL Server JDBC driver works essentially the same as the others.
  -More details can be found in the https://docs.microsoft.com/en-us/sql/connect/jdbc/connecting-to-sql-server-with-the-jdbc-driver?view=sql-server-2017[official documentation].
  -
  -=== Derby
  -
  -`jdbc:derby:[//serverName[:portNumber]/][memory:]databaseName[;property=value[;property=value]]`
  -
  -Example:: `jdbc:derby://localhost:1527/myDB`, `jdbc:derby:memory:myDB;create=true`
  -
  -Derby is an embedded database.
  -It can run as a server, based on a file, or live completely in memory.
  -All of these options are available as listed above.
  -You can find more information at the https://db.apache.org/derby/docs/10.8/devguide/cdevdvlp17453.html#cdevdvlp17453[official documentation].
  +=== PostgreSQL
  +
  +PostgreSQL only runs as a server, as do the rest of the databases below.
  +As such, you must specify connection details, or use the defaults.
  +
  +`jdbc:postgresql:[//][host][:port][/database][?key=value...]`
  +
  +Example:: `jdbc:postgresql://localhost/test`
  +
  +Defaults for the different parts are as follows:
  +
  +`host`:: localhost
  +`port`:: 5432
  +`database`:: same name as the username
  +
  +The https://jdbc.postgresql.org/documentation/head/connect.html[official documentation] go into more detail and list optional parameters as well.
   
   :no-duration-note: true
   
  
positive.code: we refer to as Dev Services. Depending on your database type you may need docker installed in order to use this feature. Dev Services
  is supported for the following open source databases:
  
  * Postgresql (container)
  * MySQL (container)
  * MariaDB (container)
  * H2 (in-process)
  * Apache Derby (in-process)
  * DB2 (container) (requires license acceptance)
  * MSSQL (container) (requires license acceptance)
  
  
  If you want to use Dev Services then all you need to do is include the relevant extension for the type of database you want (either reactive or
  JDBC, or both), and don't configure a database URL, username and password, Quarkus will provide the database and you can just start
  
negative.code: Going into each of those options is beyond the scope of this document,
  but the following section gives an overview of each database URL and a link to the official documentation.
  
  === DB2
  
  `jdbc:db2://<serverName>[:<portNumber>]/<databaseName>[:<key1>=<value>;[<key2>=<value2>;]]`
  
  Example:: `jdbc:db2://localhost:50000/MYDB:user=dbadm;password=dbadm;`
  
  See the https://www.ibm.com/support/knowledgecenter/SSEPGG_11.5.0/com.ibm.db2.luw.apdv.java.doc/src/tpc/imjcc_r0052342.html[official documentation] for more detail on URL syntax and additional supported options.
  
  === Derby
  
  `jdbc:derby:[//serverName[:portNumber]/][memory:]databaseName[;property=value[;property=value]]`
  
  Example:: `jdbc:derby://localhost:1527/myDB`, `jdbc:derby:memory:myDB;create=true`
  
  Derby is an embedded database.
  It can run as a server, based on a file, or live completely in memory.
  All of these options are available as listed above.
  You can find more information at the https://db.apache.org/derby/docs/10.8/devguide/cdevdvlp17453.html#cdevdvlp17453[official documentation].
  
  === H2
  
  `jdbc:h2:{ {.|mem:}[name] | [file:]fileName | {tcp|ssl}:[//]server[:port][,server2[:port]]/name }[;key=value...]`
  