You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: