fix: strip spurious LIMIT when query already has TOP clause in MSSQL adapter

[tqrcisio]

Problem

When a user writes a T-SQL query using SELECT TOP N ..., the QueryModifier (which uses a MySQL-dialect sqlparser) would append LIMIT 1000 to the query. The existing convertLimitToTop function was supposed to handle this, but it had an early return when TOP was detected — leaving the trailing LIMIT intact.

The result was an invalid query like:

SELECT TOP 10 Code, Name FROM Product LIMIT 1000

Which caused SQL Server to return: Incorrect syntax near 'LIMIT'.

Root Cause

In convertLimitToTop, when hasTopRe matched, the function returned the query unchanged — even if a spurious LIMIT N had already been appended by QueryModifier.

Fix

When TOP is detected and a trailing LIMIT clause is also present, strip the LIMIT clause instead of returning the query untouched.

Test

Verified with a SQL Server query using SELECT TOP 10:

• Before: mssql: Sintaxe incorreta próxima a 'LIMIT'
• After: Query executes successfully returning 10 rows