aboutsummaryrefslogtreecommitdiff
path: root/ext/wasm/api/sqlite3-api-prologue.js
diff options
context:
space:
mode:
authordrh <>2023-08-11 11:12:46 +0000
committerdrh <>2023-08-11 11:12:46 +0000
commit91c009291756e7e7fa338f8f28335a3d2f3bc3ea (patch)
tree62a948a5e113d473922ca7e2a7dca872cd7753a0 /ext/wasm/api/sqlite3-api-prologue.js
parent89e1caf294e50ccbbc94cb75ba8a21c41aeb160c (diff)
downloadsqlite-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 'ext/wasm/api/sqlite3-api-prologue.js')
0 files changed, 0 insertions, 0 deletions