/ View Ticket
Login
2020-03-11
19:56 Fixed ticket [3c9eadd2]: PRAGMA integrity_check fails due to CHECK constraint even without records plus 4 other changes (artifact: 55c5b324 user: drh)
19:56
Do not factor out constant functions into the initialization section of a prepared statement, because even though they are constant, they can still throw exceptions. Instead, put such functions in an OP_Once block. This fixes ticket [3c9eadd2a6ba0aa5] and causes COALESCE() and CASE...END to be short-circuit. (check-in: c5f96a08 user: drh tags: trunk)
2019-12-02
11:15 Ticket [3c9eadd2] PRAGMA integrity_check fails due to CHECK constraint even without records status still Open with 3 other changes (artifact: 3fcef5ea user: drh)
11:15 Ticket [3c9eadd2]: 6 changes (artifact: dd60bfe9 user: drh)
2019-11-03
10:06 New ticket [3c9eadd2]. (artifact: d58c01a9 user: mrigger)

Ticket Hash: 3c9eadd2a6ba0aa575c6ba6cbaac2e4799031175
Title: PRAGMA integrity_check fails due to CHECK constraint even without records
Status: Fixed Type: Code_Defect
Severity: Minor Priority: Low
Subsystem: Unknown Resolution: Fixed
Last Modified: 2020-03-11 19:56:35
Version Found In: 3.30.0
User Comments:
mrigger added on 2019-11-03 10:06:22:

Unexpectedly, the integrity_check fails in the following case:

CREATE TABLE t0(c0 CHECK(ABS(-9223372036854775808)));
PRAGMA integrity_check; -- unexpected: integer overflow

This is probably a minor issue that might not be worth fixing.


drh added on 2019-12-02 11:15:03:

This is difficult to fix and perhaps not worth fixing.

We will leave the ticket open for the time being as a record of the problem, but we do not anticipate fixing it right away.