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
Query count verification used to have a threshold check in various cases. It was complicated and seemed unnecessary. However, it used to be that if you performed 98.5% of select statements on any db query test, it would warn on verification. This is now an error.
Fortune always had the requirement that the list be dynamically sized, but it was never enforced. The verification process now brute-forcefully adds ~10,000 fortunes to the table, then makes a request to the fortune end-point again and checks that all of the old and new fortunes are present (read: if a statically sized array/vector/list were used, this would fail).
Give a 1.5% margin of error acceptance to the MySQL implementation of get_count_of_all_queries_for_table.
The text was updated successfully, but these errors were encountered:
select
statements on any db query test, it would warn on verification. This is now an error.Fortune
always had the requirement that the list be dynamically sized, but it was never enforced. The verification process now brute-forcefully adds ~10,000 fortunes to the table, then makes a request to thefortune
end-point again and checks that all of the old and new fortunes are present (read: if a statically sized array/vector/list were used, this would fail).MySQL
implementation ofget_count_of_all_queries_for_table
.The text was updated successfully, but these errors were encountered: