-
Notifications
You must be signed in to change notification settings - Fork 388
Add the SQLQueryError class for DQE and its test #1257
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
Add the SQLQueryError class for DQE and its test #1257
Conversation
The core idea of DQE is that the SELECT, UPDATE and DELETE queries with the same predicate φ should access the same rows. If these queries access different rows, DQE reveals a potential logic bug in the target DBMS. SQLQueryError class is used to compare the errors
|
Looks good to me. |
mrigger
left a comment
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.
Sorry for the delay - I have been traveling. This almost looks good to me. Could you please check whether any of my suggestions make sense before merging this?
mrigger
left a comment
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.
LGTM, thanks!
|
It seems the formatter check currently fails. After executing |
I'm sorry for that mistakes, I've solved that. Thanks a lot. @mrigger |
|
It seems some code style checks fail. You can execute |
I hava get the |
This PR is used to split #1251 into small pieces.
The core idea of DQE is that the SELECT, UPDATE and DELETE queries with the same predicate φ should access the same rows. If these queries access different rows, DQE reveals a potential logic bug in the target DBMS. SQLQueryError class is used to compare the errors @mrigger @JensonSung