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 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 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 suspect that would break >> existing applications still using DB2 9.1. >> >> I'm considering adding a new dialect DB295Dialect that extends DB2Dialect >> and overrides DB2Dialect#getCrossJoinSeparator to return "cross join". >> >> WDYT? >> >> Regards, >> Gail >> _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
