On 2022-05-19 Th 08:19, Justin Pryzby wrote:
>> + same level are considerd to be siblings,
> considered
>
>> +PostgreSQL specific functions detailed in
> postgresql hyphen specific (as in the original)
>
> These would all be easier to read with commas:
>
> +expression is NULL an
> +
> + same level are considerd to be siblings,
considered
> +PostgreSQL specific functions detailed in
postgresql hyphen specific (as in the original)
These would all be easier to read with commas:
+expression is NULL an
+If WITH UNIQUE is specified the
+If the inpu
On 2022-May-16, Andrew Dunstan wrote:
> Thanks. I have incorporated all of these, added a result for the last
> json_table example, and done some more wordsmithing around PLAN DEFAULT.
For sure this is a big improvement, thanks. No longer do we have to
refer to section 9.16.3.2.2.3 -- that's in
Op 16-05-2022 om 20:53 schreef Andrew Dunstan:
On 2022-05-16 Mo 13:52, Erik Rijkers wrote:
-
2.
This example in func.sgml says it gives 't' but on my instance it
returns 'f'. Is the example correct?
jsonb_path_exists_tz('["2015-08-01 12:00:00 -05"]', '$[*] ?
(@.datetime() < "2015-08-02".
On 2022-05-16 Mo 14:53, Andrew Dunstan wrote:
> On 2022-05-16 Mo 13:52, Erik Rijkers wrote:
>> Op 16-05-2022 om 16:49 schreef Andrew Dunstan:
>>
>>> [sqljson-dox-rework-2.patch]
>> Two issues, derived from func.sgml:
>>
>> -
>> 1.
>>
>> I noticed that some json functions, for instance json_ob
On 2022-05-16 Mo 13:52, Erik Rijkers wrote:
> Op 16-05-2022 om 16:49 schreef Andrew Dunstan:
>
>> [sqljson-dox-rework-2.patch]
>
> Two issues, derived from func.sgml:
>
> -
> 1.
>
> I noticed that some json functions, for instance json_object(), in
> their output insert unexpected spaces befo
Op 16-05-2022 om 16:49 schreef Andrew Dunstan:
[sqljson-dox-rework-2.patch]
Two issues, derived from func.sgml:
-
1.
I noticed that some json functions, for instance json_object(), in their
output insert unexpected spaces before the separator-colon:
testdb=# select json_object('{a, 1,
Not done yet but here's where I'm at. If I'm on the wrong track or
missing things that should be done please let me know.
[sqljson-dox-rework.patch]
Here are a few errors/typos/improvements.
I've added (=copied from the old docs) the CREATE TABLE for the my_films
table so that the more co
On 2022-05-04 We 15:14, Andrew Dunstan wrote:
> On 2022-05-04 We 11:39, Tom Lane wrote:
>> "David G. Johnston" writes:
>>> Is there a thread I'm not finding where the upcoming JSON function
>>> documentation is being made reasonably usable after doubling its size with
>>> all the new JSON Table
On 2022-05-04 We 11:39, Tom Lane wrote:
> "David G. Johnston" writes:
>> Is there a thread I'm not finding where the upcoming JSON function
>> documentation is being made reasonably usable after doubling its size with
>> all the new JSON Table features that we've added? If nothing else, the
>>
On Wed, May 4, 2022 at 8:39 AM Tom Lane wrote:
> "David G. Johnston" writes:
> > Is there a thread I'm not finding where the upcoming JSON function
> > documentation is being made reasonably usable after doubling its size
> with
> > all the new JSON Table features that we've added? If nothing e
On Wed, May 04, 2022 at 08:32:51AM -0700, David G. Johnston wrote:
> Hey,
>
> Is there a thread I'm not finding where the upcoming JSON function
> documentation is being made reasonably usable after doubling its size with
> all the new JSON Table features that we've added? If nothing else, the
>
"David G. Johnston" writes:
> Is there a thread I'm not finding where the upcoming JSON function
> documentation is being made reasonably usable after doubling its size with
> all the new JSON Table features that we've added? If nothing else, the
> table of contents at the top of the page needs t
13 matches
Mail list logo
