I just stumbled across the default SQLServer2005LimitHandler which is the default limit handler for SQL server. We have queries with a subquery in the column list like this one:
When the limit handler trys to get the position of the FROM-clause (in method fillAliasInSelectClause) it uses a regular expression:
to determine the actual column aliases in the select. This will match the first FROM-clause in the subquery thus yielding to a wrong select list of the limit clause like this for the example above:
Am I right that there will be no fix for the 5.1.x branch?
Just curious because I will have to adopt the fix manually then.
Fixed in 5.1 branch as well.
, this will be fixed in 5.1.6 to be released later this week.