| Age | Commit message (Collapse) | Author |
|
json_get_type/json_type
|
|
The SearchSysCacheList1 macro was introduced in PostgreSQL 9.
Changed a couple tests to cope with formatting discrepancy
introduced by PostgreSQL 9 (namely, + characters between newlines).
|
|
"\uD840\uDC00".
|
|
|
|
* char() method added to JSONPath for extracting chars from strings.
Although index subscripts (those using an integer) extract characters from
strings in Stefan Goessner's JSONPath, and although it works that way in
JavaScript, I believe it is rather illogical and unexpected in the context
of JSONPath, and a poor use of the [] real estate.
Because extracting characters from strings can still be useful, I have added
a char() method for this. I implemented it now to prevent the supporting code
for character extraction from wasting away.
|
|
The tests no longer take up 2.4 megabytes, and they'll be easier to update
whenever semantics are changed (e.g. switching json_path '$..*' from
matching breadth-first to depth-first).
|
|
|
|
* Reworked json_node::orig so it can handle replacing the key or value
without altering surrounding formatting.
* json_encode (C function) is now recursive (its stack usage depends
on the depth of input). This was done because json_encode cannot rely
on nodes' ->parent fields being trustworthy, as json_replace_value
assigns JSON nodes by reference.
|
|
* Affirmed (with a trivial test) that json_path returns its results breadth-first
|
|
* Removed the global variable json_escape_unicode and added a parameter for it
to the json_encode and json_encode_string C functions.
|
|
* Migrated test strings from json-0.0.2
* Added struct {...} orig; field to struct json_node, but it's not used yet.
It will be used to hold pointers to original text.
|
|
|
|
Currently, it re-encodes JSON nodes rather than preserving original text.
This is subject to change.
|
|
|
|
This repository should probably be an honest-to-goodness branch of
mainline PostgreSQL. I'm looking into that :-)
|