Lyall Pearce
2015-08-19 04:05:56 UTC
SQL Server 2012 supports the following...
select *
from table
where clause
ORDER BY column
OFFSET :offset ROWS
FETCH NEXT :limit ROWS
which is ideal for use with slice() and runs in SQL Server Management
Studio 2012.
However, the documentation indicates that SQL Server does not support this
and the sqlalchemy 1.0.8 actually generates code as follows
select *
from table
where clause
ORDER BY column
LIMIT :limit
OFFSET :offset
When being used with Python 2.7 and pyodbc-3.0.10, it actually runs but the
limit is actually the limit - offset, so limit is being treated as an
absolute offset, not a row count.
Is this expected?
select *
from table
where clause
ORDER BY column
OFFSET :offset ROWS
FETCH NEXT :limit ROWS
which is ideal for use with slice() and runs in SQL Server Management
Studio 2012.
However, the documentation indicates that SQL Server does not support this
and the sqlalchemy 1.0.8 actually generates code as follows
select *
from table
where clause
ORDER BY column
LIMIT :limit
OFFSET :offset
When being used with Python 2.7 and pyodbc-3.0.10, it actually runs but the
limit is actually the limit - offset, so limit is being treated as an
absolute offset, not a row count.
Is this expected?
--
You received this message because you are subscribed to the Google Groups "sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.