Document JDBC connection properties

[jonathanpeppers]

Sources

• https://developer.android.com/reference/java/sql/Connection#getAutoCommit()
• https://developer.android.com/reference/java/sql/Connection#getCatalog()
• https://developer.android.com/reference/java/sql/Connection#getClientInfo()
• https://developer.android.com/reference/java/sql/Connection#getHoldability()
• https://developer.android.com/reference/java/sql/Connection#isClosed()
• https://developer.android.com/reference/java/sql/Connection#getMetaData()
• https://developer.android.com/reference/java/sql/Connection#isReadOnly()
• https://developer.android.com/reference/java/sql/Connection#getTransactionIsolation()
• https://developer.android.com/reference/java/sql/Connection#getTypeMap()
• https://developer.android.com/reference/java/sql/Connection#getWarnings()

Validation

• XML parse validation for docs/xml/Java.Sql/IConnection.xml
• CRLF line-ending validation
• Scoped To be added. placeholder validation for IConnection
• Android reference-anchor coverage validation
• git diff --check

@dalexsoto please review this focused JDBC connection property documentation update.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[jonathanpeppers]

@dalexsoto review

[dalexsoto]

Two property contracts need correction:

• TransactionIsolation conflates getter and setter domains. The getter may return TransactionNone, but assigning TRANSACTION_NONE is invalid and must throw SQLException; distinguish readable results from setter-valid values.
• Holdability and TransactionIsolation use Java identifiers such as ResultSet.HOLD_CURSORS_OVER_COMMIT and Connection.TRANSACTION_READ_COMMITTED, which do not exist in the managed API. Replace them with managed references such as IResultSet.HoldCursorsOverCommit and IConnection.TransactionReadCommitted.

[jonathanpeppers]

Addressed the review in 910fc74: Holdability and TransactionIsolation now link to the managed IResultSet/IConnection constants, and the transaction isolation docs distinguish getter results from setter-valid values (TransactionNone is getter-only and rejected by the setter).

[dalexsoto]

The previously reported constant and setter-domain issues are fixed, but two managed-contract problems remain:

• TypeMap still names Java's java.util.Map instead of the exposed managed IDictionary<string, Java.Lang.Class> type.
• The five transaction-isolation altmember links near TransactionIsolation target obsolete Java.Sql.Connection constants that direct users to IConnection.

Please use the managed type/cref and point all related constants to Java.Sql.IConnection.

[jonathanpeppers]

Addressed the remaining managed-contract feedback in dabfc95: TypeMap now links to and displays IDictionary<string, Java.Lang.Class>, and all five transaction-isolation altmember links now target Java.Sql.IConnection constants.

[dalexsoto]

The managed TypeMap type and transaction constant links are fixed, but the TypeMap contract still implies the returned dictionary is directly associated with the connection. JDBC requires callers to assign the map back after modification because drivers may retain an internal copy. Please document that reassignment/setter requirement and link the setter source alongside the getter.

[jonathanpeppers]

Addressed the latest TypeMap contract feedback in ba1565d: the docs now require assigning a modified dictionary back to the property because drivers may retain an internal copy, and they link both the JDBC getter and setter sources.

[dalexsoto]

The TypeMap reassignment contract is fixed, but the metadata property now names Java's DatabaseMetaData, which does not exist in the managed API. The generated signature returns Java.Sql.IDatabaseMetaData?; please reference the managed interface, preferably with <see cref="T:Java.Sql.IDatabaseMetaData" />.

[jonathanpeppers]

Addressed the metadata feedback in f7e5efd: the MetaData value documentation now references the managed Java.Sql.IDatabaseMetaData interface via a resolvable cref.

[dalexsoto]

All JDBC property contracts now use valid managed types and constants, including TypeMap reassignment and IDatabaseMetaData.