diff options
| author | Rucha Deodhar <rucha.deodhar@mariadb.com> | 2022-10-28 13:03:13 +0530 |
|---|---|---|
| committer | Rucha Deodhar <rucha.deodhar@mariadb.com> | 2023-04-26 11:00:08 +0530 |
| commit | 358b8495f5ffb19a1a89574fd897261e8ff12938 (patch) | |
| tree | 7cf421be3ec83efff6a9905c13c3c9e2687cdc1a /sql/CMakeLists.txt | |
| parent | af0e0ad18d5295d57696e3d26d5a7b13dca4e420 (diff) | |
| download | mariadb-git-358b8495f5ffb19a1a89574fd897261e8ff12938.tar.gz | |
MDEV-27128: Implement JSON Schema Validation FUNCTION
Implementation:
Implementation is made according to json schema validation draft 2020
JSON schema basically has same structure as that of json object, consisting
of key-value pairs. So it can be parsed in the same manner as
any json object.
However, none of the keywords are mandatory, so making guess about the
json value type based only on the keywords would be incorrect.
Hence we need separate objects denoting each keyword.
So during create_object_and_handle_keyword() we create appropriate objects
based on the keywords and validate each of them individually on the json
document by calling respective validate() function if the type matches.
If any of them fails, return false, else return true.
Diffstat (limited to 'sql/CMakeLists.txt')
| -rw-r--r-- | sql/CMakeLists.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/sql/CMakeLists.txt b/sql/CMakeLists.txt index 9ef1ee46d5c..0284359fbc7 100644 --- a/sql/CMakeLists.txt +++ b/sql/CMakeLists.txt @@ -161,7 +161,7 @@ SET (SQL_SOURCE opt_table_elimination.cc sql_expression_cache.cc gcalc_slicescan.cc gcalc_tools.cc my_apc.cc mf_iocache_encr.cc item_jsonfunc.cc - my_json_writer.cc + my_json_writer.cc json_schema.cc json_schema_helper.cc rpl_gtid.cc rpl_parallel.cc semisync.cc semisync_master.cc semisync_slave.cc semisync_master_ack_receiver.cc |