-
Notifications
You must be signed in to change notification settings - Fork 87
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
Common InsertTest class tests undocumented use case #139
Comments
Judging by #134, it looks like non-named placeholders aren't even supported now, so perhaps this test should just be refactored to use an associative array? |
@djmattyg007 I am confused. Are you looking at Aura.SqlQuery/tests/Common/InsertTest.php Line 71 in b1bcd35
Thank you. |
Yes, that is what I'm looking at. |
@djmattyg007 looking into that test case, it is only a test for the The interface doesn't even care to send an exception if they are wrong. Aura.SqlQuery/src/QueryInterface.php Line 65 in b1bcd35
So there is nothing wrong. If you want to correct to make it associative it is not a problem also. Send a PR. Thank you. |
I think that test case and the one below it should be moved to a different class altogether. They're testing methods on the abstract query class. |
It's probably best to wait for #142 to be resolved before trying to make changes to this. |
I didn't noticed it earlier. Thank you for the mention. |
The common
InsertTest
class tests an undocumented way of binding values to a query object. ThetestBindValues()
method callsAbstractQuery::bindValues()
with a non-associative array. This use case doesn't appear to be documented, and isn't used by any other code. Is this intentional? Does this test even belong in theInsertTest
class?The text was updated successfully, but these errors were encountered: