ORA-01843: not a valid month binding JSR 310 to prepared statements

[lukaseder]

Oracle's support for JSR-310 types is still incomplete. Internally, the type is bound as a string, which doesn't work for Oracle, depending on the NLS settings. The workaround is to implement a custom data type binding.

An improved solution will need to bind an oracle.sql.TIMESTAMPTZ type. Note that despite ojdbc8 having been retrofitted to accept JSR 310 types like ZoneId, some clients might still be using ojdbc7

Further tests are needed - it is likely that e.g. the following might not work perfectly yet:

• IN parameters (this issue)
• OUT parameters (currently registered as Types.VARCHAR)
• UDT attributes (see Support Oracle TIMESTAMP WITH TIME ZONE data type in UDT #6630)

See also: #5910

[lukaseder]

The fixes in this area are rather delicately linked to the #4930 DefaultBinding refactoring, and will thus not be merged to 3.10