In the short term (for master), I'll add new DB2 dialect.
Thanks,
Gail
On Thu, Feb 16, 2017 at 7:45 AM, Steve Ebersole wrote:
> To Gail's specific question... As Sanne stated, a new Dialect is the only
> option IMO for the moment.
>
> But what Chris brings up is important, and something we real
To Gail's specific question... As Sanne stated, a new Dialect is the only
option IMO for the moment.
But what Chris brings up is important, and something we really should start
deciding. We have been discussing it off and on for 4-5 years.
Dialects were originally designed to be inflexible. We
On 16 February 2017 at 14:23, Chris Cranford wrote:
> We have actually discussed doing something where Dialect's auto-configure
> themselves, but such a change would likely be appropriate for a major
> release only.
>
> On 02/16/2017 04:57 AM, Christian Beikov wrote:
>> How about a different appro
We have actually discussed doing something where Dialect's auto-configure
themselves, but such a change would likely be appropriate for a major
release only.
On 02/16/2017 04:57 AM, Christian Beikov wrote:
> How about a different approach? Like passing the DB version somehow to
> the dialect so t
How about a different approach? Like passing the DB version somehow to
the dialect so that it can decide for itself instead of having different
subclasses.
Am 16.02.2017 um 08:16 schrieb Gail Badner:
> HHH-11487 can be fixed by using changing DB2Dialect#getCrossJoinSeparator
> to return " cross
HHH-11487 can be fixed by using changing DB2Dialect#getCrossJoinSeparator
to return " cross join ".
DB2 9.1 did not support CROSS JOIN, but DB2 9.5 and later do support CROSS
JOIN. I see that DB2 9.1 is no longer supported as of April 30, 2015.
It's tempting to just update DB2Dialect, but I suspe
