Thanks for the feedback.
I added some comments in-line.
On Tue, Jan 7, 2020 at 1:59 AM Yoann Rodiere wrote:
> Hi,
>
> The syntax looks nice.
> I suppose it's future-proof enough, though I can imagine us getting in
> trouble if JDBC starts allowing parameterized or custom formats, which may
> st
On Tue, 7 Jan 2020 at 14:45, Steve Ebersole wrote:
> Sorry, I should have been more clear. The literals are not "passed
> through"; it's just a mechanism to be able to recognize the literal
> syntactically while parsing. All of those forms I showed actually are
> handled in the code and interpr
On Tue, Jan 7, 2020 at 10:05 AM Yoann Rodiere wrote:
> On Tue, 7 Jan 2020 at 14:45, Steve Ebersole wrote:
>
>> Sorry, I should have been more clear. The literals are not "passed
>> through"; it's just a mechanism to be able to recognize the literal
>> syntactically while parsing. All of those
>
> As far as I know, even Java does not support that. A true zone-id would
> be something like (for me) "America/Chicago". If I ask Java to parse
> "2020-01-01 10:10:10 America/Chicago +02:00" it just says no. For me, CST
> (standard) and CDT (daylight savings) are really synonyms for offset -
