Using "offset + fetch next rows" to replace legacy statements in mssql and oracle query #2187

Open
opened 2022-10-19 02:19:49 +00:00 by FlyingOnion · 2 comments
Member

Both SQLServer (2012 and after) and Oracle (12c and after) support offset <count> rows fetch next <count> rows only. It's a more elegant way than using legacy subquery.

bd58520020/internal/statements/query.go (L221)

Both SQLServer (2012 and after) and Oracle (12c and after) support `offset <count> rows fetch next <count> rows only`. It's a more elegant way than using legacy subquery. https://gitea.com/xorm/xorm/src/commit/bd58520020dfb5bd6b7f5779e871d53aa9ee4c71/internal/statements/query.go#L221
Owner

Could you send a PR to fix that?

Could you send a PR to fix that?
Author
Member

Could you send a PR to fix that?

Finished in #2188

> Could you send a PR to fix that? Finished in #2188
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: xorm/xorm#2187
No description provided.