-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
00378ef
commit 1fe6089
Showing
2 changed files
with
39 additions
and
27 deletions.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1fe6089
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
1fe6089
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure what this commit was intended to resolve but it breaks the oracle db support for me. When I do findFirst, the constructed query does not contain any limits (which is weird), and the result correctly contains the first record. However, when I do find(array('limit' => 1)) the query again contains no limits but the result contains no records, which is a bummer. The limit method needs to account for the possibility when the limit is passed as a "APL0" bound parameter as mentioned in #11217
1fe6089
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@andresgutierrez I fixed the Oracle dialect in my private branch at rlaffers@91985cf
This fixes #11033 (comment) and #11217
Unfortunately I had to branch off from the last known working commit from just before your commit #1fe6089a2773fe0926af34c6202470ee32c199be . After that, it seems Phalcon does not step into the limit method in the Oracle dialect when using findFirst() or find with limit specified. Can you confirm this behavior? I would like to bring my fix into the 2.0.x branch but first we have to figure out what went wrong later on.
1fe6089
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rlaffers Hello. Create please an issue for this discussion