Ticket Hash: | be31cf009c8540d0b21b237ab4b8c7e6d792ffa8 | |||
Title: | Unexpected result for % and '1E1' | |||
Status: | Closed | Type: | Code_Defect | |
Severity: | Minor | Priority: | Low | |
Subsystem: | Unknown | Resolution: | Works_As_Designed | |
Last Modified: | 2020-08-27 13:33:54 | |||
Version Found In: | ||||
User Comments: | ||||
mrigger added on 2020-08-26 14:12:56:
Consider the following statement:
Unexpectedly, the result is 0.0. This seems to be a regression bug that was introduced by [048add13fc10e69a], and was found by SQLancer's PQS implementation based on commit [6c716f4b55]. drh added on 2020-08-27 13:21:31: The intent of the "%" operator is to work on integers only. For any values $A and $B, the following should always be true:
This fact is not clearly defined in the documentation, but it has always
been so. I will use this ticket to enhance the documentation.
The behavior of
The longest possible prefix of the string " drh added on 2020-08-27 13:33:54: Documentation updated. https://www.sqlite.org/docsrc/info/153857859d220dbd |