Re: json(b)_to_tsvector with numeric values - Mailing list pgsql-hackers

From Dmitry Dolgov
Subject Re: json(b)_to_tsvector with numeric values
Date
Msg-id CA+q6zcVr6oseeKpCvyGwWFYetgdshOZkKenuqAaVz=fqLk7_wQ@mail.gmail.com
Whole thread Raw
In response to Re: json(b)_to_tsvector with numeric values  (Teodor Sigaev <teodor@sigaev.ru>)
Responses Re: json(b)_to_tsvector with numeric values
List pgsql-hackers
> On 4 April 2018 at 16:09, Teodor Sigaev <teodor@sigaev.ru> wrote:
>
>>> Hm, seems, it's useful feature, but I suggest to make separate function
>>> jsonb_any_to_tsvector and add support for boolean too (if you know better
>>> name for function, do not hide it). Changing behavior of existing
>>> function
>>> is not obvious for users and, seems, should not backpatched.
>>
>>
>> What do you think about having not a separate function, but a flag
>> argument to
>> the existing one (like `create` in `jsonb_set`), that will have false as
>> default value? The result would be the same, but without an extra function
>> with
>> almost the same implementation.
>
>
> tsvector jsonb_to_tsvector(jsonb[, bool]) ?
> Agreed. Second arg should be optional.

Unfortunately, this idea with a flag argument can't be implemented easily
(related discussion is here [1]). So I've modified the patch accordingly to
your original suggestion about having separate functions
`json(b)_all_to_tsvector`.

1:
https://www.postgresql.org/message-id/flat/CA%2Bq6zcVJ%2BWx%2B-%3DkkN5UC0T-LtsJWnx0g9S0xSnn3jUWkriufDA%40mail.gmail.com

Attachment

pgsql-hackers by date:

Previous
From: Melanie Plageman
Date:
Subject: Re: Removing useless DISTINCT clauses
Next
From: Peter Eisentraut
Date:
Subject: Re: [PATCH] Logical decoding of TRUNCATE