Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

limit(int) sets default offset incorrectly #412

Closed
lukaseder opened this issue Jul 22, 2012 · 3 comments
Closed

limit(int) sets default offset incorrectly #412

lukaseder opened this issue Jul 22, 2012 · 3 comments
Assignees
@lukaseder
Labels
C: DB: PostgreSQL P: High R: Fixed T: Defect
Milestone
Version 1.5.7

Comments

@lukaseder
Copy link
Member

When using the current snapshot of jOOQ with PostgreSQL, executing a query with "limit(1)" results in this SQL: "limit 1 offset 1".

I would expect it to result in "limit 1", or, if you want to specity the offset explicitly: "limit 1 offset 0".

"offset 1" means "start with the second record".
@ghost ghost assigned lukaseder Jul 22, 2012
@lukaseder
Copy link
Member Author

Nice catch. Is this behaviour specific to the upcoming version 1.5.7, or did you experience this before?

@lukaseder
Copy link
Member Author

Author: anonymous
I don't know - i haven't tried this on 1.5.6 because i need the Attachable API :)

@lukaseder
Copy link
Member Author

Makes sense... ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lukaseder lukaseder

Labels
C: DB: PostgreSQL P: High R: Fixed T: Defect
Projects
None yet
Milestone
Version 1.5.7
Development

No branches or pull requests
1 participant
@lukaseder