diff options
| author | drh <> | 2023-08-11 11:12:46 +0000 |
|---|---|---|
| committer | drh <> | 2023-08-11 11:12:46 +0000 |
| commit | 91c009291756e7e7fa338f8f28335a3d2f3bc3ea (patch) | |
| tree | 62a948a5e113d473922ca7e2a7dca872cd7753a0 /src/ctime.c | |
| parent | 89e1caf294e50ccbbc94cb75ba8a21c41aeb160c (diff) | |
| download | sqlite-91c009291756e7e7fa338f8f28335a3d2f3bc3ea.tar.gz sqlite-91c009291756e7e7fa338f8f28335a3d2f3bc3ea.zip | |
Up until version 3.42.0, there was a bug in json_valid() such that it would
return False (0) for a NULL input. That bug is fixed in 3.42.0. This
check-in adds a compile-time option -DSQLITE_LEGACY_JSON_VALID that restores
the old buggy behavior for applications that depend on it.
FossilOrigin-Name: 15c2eadbff8e732cca45d6c3771d1fcea5aab2127e87f2a611b41ccfef4d1a0d
Diffstat (limited to 'src/ctime.c')
| -rw-r--r-- | src/ctime.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/ctime.c b/src/ctime.c index c853e5ba4..368724168 100644 --- a/src/ctime.c +++ b/src/ctime.c @@ -60,9 +60,6 @@ static const char * const sqlite3azCompileOpt[] = { #ifdef SQLITE_4_BYTE_ALIGNED_MALLOC "4_BYTE_ALIGNED_MALLOC", #endif -#ifdef SQLITE_64BIT_STATS - "64BIT_STATS", -#endif #ifdef SQLITE_ALLOW_COVERING_INDEX_SCAN # if SQLITE_ALLOW_COVERING_INDEX_SCAN != 1 "ALLOW_COVERING_INDEX_SCAN=" CTIMEOPT_VAL(SQLITE_ALLOW_COVERING_INDEX_SCAN), @@ -399,6 +396,9 @@ static const char * const sqlite3azCompileOpt[] = { #ifdef SQLITE_INTEGRITY_CHECK_ERROR_MAX "INTEGRITY_CHECK_ERROR_MAX=" CTIMEOPT_VAL(SQLITE_INTEGRITY_CHECK_ERROR_MAX), #endif +#ifdef SQLITE_LEGACY_JSON_VALID + "LEGACY_JSON_VALID", +#endif #ifdef SQLITE_LIKE_DOESNT_MATCH_BLOBS "LIKE_DOESNT_MATCH_BLOBS", #endif |