On 2/23/19 2:39 PM, Mark Rotteveel wrote:
On 18-2-2019 12:59, Alex Peshkoff via Firebird-devel wrote:
On 2/18/19 2:21 PM, Adriano dos Santos Fernandes wrote:
On 16/02/2019 12:57, Mark Rotteveel wrote:
BTW: similar arguments could be made for the SET DECFLOAT options, but
I don't have a need there.
The similar SET DECFLOAT wasn't it, so TIME ZONE didn't had too.
That backward compatibility bindings were designed in order to make
new features work somehow with old, having no idea about them,
software. Such software hardly has a good way to place unknown to it
items to DPB. New one should better use default bindings cause they
provide best (from functionality POV) access to new features. So why
overcomplicate server where it's not needed ?
That ignores the reality of drivers that are aware of the existence of
a feature but haven't yet come around to implementing it (or don't
want to implement it). For example, I only want to support time zones
in Java 8 (and higher) and not in Java 7 to avoid having to implement
it twice because the Java 8 implementation will use the java.time
(JSR-310) API as required by JDBC, and this doesn't exist in Java 7.
I could also add something like that in Jaybird 3.x, etc (that could
apply for both DECFLOAT and WITH TIME ZONE types).
And as I mentioned earlier, I'm also concerned about the effects of
ALTER SESSION RESET.
To me you suggestion looks reasonable - but I'm not sure is not it too
late to add new features to FB4 after beta1.
Let's see what others think about it.
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
