-
Notifications
You must be signed in to change notification settings - Fork 11.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[10.x] Fixes whereDate
, whereDay
, whereMonth
, whereTime
, whereYear
and whereJsonLength
to ignore invalid $operator
#52704
Conversation
5a92005
to
f303beb
Compare
… and `whereJsonLength` to ignore invalid `$operator` Signed-off-by: Mior Muhammad Zaki <crynobone@gmail.com>
ea2559e
to
4ff4011
Compare
whereDate
, whereDay
, whereMonth
, whereTime
, whereYear
and whereJsonLength
to ignore invalid $operator
whereDate
, whereDay
, whereMonth
, whereTime
, whereYear
and whereJsonLength
to ignore invalid $operator
@@ -33,13 +36,16 @@ public function getSQLDeclaration(array $column, AbstractPlatform $platform): st | |||
MySQLPlatform::class, | |||
MySQL57Platform::class, | |||
MySQL80Platform::class, | |||
MySQL84Platform::class, |
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.
Shouldn't we move these changes to a separate PR?
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.
10.x is currently on security only updates.
Mind if I ask why? Or what is this trying to solve? Isn't it better to throw an I mean, if a particular DBMS supports an operator not listed as valid within the class, I guess the developer would be surprised by this behavior. |
I assume the issue is SQL injection, where the operator comes from user input? We have a similar fallback system for when an invalid sort direction is passed to order by, for example. |
No description provided.