* fix: backpatch PR#2217 to fix issue #2215. OIDs are unsigned integers and were not being handled correctly when they exceeded the size of signed integers

* Underscores are not allowed in java 6

* fix: NPE calling getTypeInfo when alias is null

…#2228)

* fix: change to updatable result set to use correctly primary or unique keys

Fix issues introduced in PR# 2199 causing problems when updating tables with PK and UK.
Originally updatable result sets support only primary keys, with the aforementioned change
and this fix unique keys are also eligible to enable updatable result set. This change will
find the better suited primary or unique key that has all the available columns in the query, but
if no match is found it will continue to fail as it used to.

Closes issue 2196

* fix: changes to updatable result set to disable use of unique keys with nullable columns

Adding logic to ensure all columns in the constraint (primary/unique) are non-nullable (always true for PKs) to guarantee 1-1 updates

* fix: removal of added code after nullable unique keys are excluded

No need to have IS NULL when nullable keys are not allowed to guarantee 1-1 updates

* fix: exclude indices with expressions for updatable result sets

Indices with expressions cannot be used (unless expression parsing / resolution
is implemented properly - currently don't see a way to get individual list elements
from pg_index.indexprs to enable proper expression filtering (pg_get_expr gives the
expression, but unable to map this to a specific attribute in the index)

Co-authored-by: Marquez Grabia, Christian <[email protected]>

…lopment script that is clearly still in development (#2240)

…here are duplicate descriptions oids are not guaranteed to be unique in the catalog (#2248)

…ment

Fixes DatabaseMetaDataTest to use older syntax for COMMENT ON FUNCTION with
explicit no-arg parameter parentheses as it is required on server versions
before v10.

…2253)

It is possible to break method PgDatabaseMetaData.getIndexInfo() by adding certain custom operators.
This PR casts operands in a query so that PgDatabaseMetaData.getIndexInfo() works in presence
of such operator config.

Creating this operator triggers this issue:

CREATE OR REPLACE FUNCTION f6(numeric, integer) returns integer as 'BEGIN return $1::integer & $2;END;' language plpgsql immutable;
CREATE OPERATOR & (LEFTARG = numeric, RIGHTARG = integer, PROCEDURE = f6);

Fixes #2241

* backpatch PR#2247
QueryExecutorImpl.receiveFastpathResult did not properly handle ParameterStatus messages.
This in turn caused failures for some LargeObjectManager operations.
Fixed by adding the missing code path, based on the existing handling in processResults.

Closes #2237
Original by Simon Strassl https://github.com/strassl

* Fix test

* docs: Add description of connection property logServerErrorDetail

* fix: Avoid leaking error message details in JDBC batches when logServerErrorDetail is disabled

* test: Add a test case for logServerErrorDetail with JDBC batches

Co-authored-by: Frode Carlsen <[email protected]>
Co-authored-by: Sehrope Sarkuni <[email protected]>

…ypes by OID, we can return types for well known types (#2257)

* fix startup regressions caused by PR #1949. Instead of checking all types by OID, we can return types for well known types

* clarifiy code, add any new types to the pgNameToSQLType cache

* Bump version to 42.2.24 and update changelog

* update contributors, and release post

Co-authored-by: Jorge Solórzano <[email protected]>