Brett Wooldridge, explicitly specifying the SQLSeverDialect rather than using the dialect resolver strategy does indeed throw the exception. I've tracked it down to a code change in TopLimitHandler that I'll address now.