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.

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

Strange behavior with limit and join #239

Open
kaoecoito opened this issue Dec 12, 2019 · 0 comments
Open

Strange behavior with limit and join #239

kaoecoito opened this issue Dec 12, 2019 · 0 comments

Comments

@kaoecoito
Copy link

I made a wrapper implementation to integrate with the MUMPS database known as GTM.
I am still in the testing stage but the implementation is working as expected for most cases.

However I noticed a strange effect with LIMIT when used in conjunction with JOIN. Not sure if the problem is multicorn or postgresql (10.6) itself.

This query executes as expected and returns only 1 record:

select * from receipt_payment r join company e on e.id = r.company where r.receipt = 100;

But this query returns zero records. In my wrapper debug shows that the line was passed to multicorn.

select * from receipt_payment r join company e on e.id = r.company where r.receipt = 100 limit 100;

This same query without using join returns 1 record as expected:

select * from receipt_payment r where r.receipt = 100 limit 100;

Does anyone have any ideas where this problem may be occurring?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant