TRY should handle invalid value error in cast VACHAR as TIMESTAMP

[takezoe]

Description

Previously (at least in 317), TRY(CAST(xxxx AS TIMESTAMP) returned NULL for a timestamp that contains an invalid value like 0000-00-00 but in the latest Trino, it fails with the following error:

Invalid value for MonthOfYear (valid values 1 - 12): 0

Trino's document says:

The following errors are handled by TRY:

• Division by zero
• Invalid cast or function argument
• Numeric value out of range

Therefore, I think TRY should cover this case. This pull request will resurrect the previous behavior which returns NULL for invalid values in timestamp.

Related issues, pull requests, and links

Documentation

(x) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.

Release notes

( ) No release notes entries required.
(x) Release notes entries required with the following suggested text:

# General
* Handle `varchar` to `timestamp` conversion errors in {func}`try`. ({issue}`11259`)

[findepi]

TrinoException

[takezoe]

Fixed. Is it better to replace another IllegalArgumentException in this method too?

trino/core/trino-main/src/main/java/io/trino/operator/scalar/timestamp/VarcharToTimestampCast.java

Lines 120 to 122 in 102ab2a

	if (!matcher.matches()) {
	throw new IllegalArgumentException("Invalid timestamp: " + value);
	}

[findepi]

Yes, please

[findepi]

merge try blocks together

[takezoe]

Merged into a single try block.

[findepi]

add test with timestamp with time zone

• zero day of month
• invalid tz specifier

[takezoe]

Added cases.