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

From Teodor Sigaev
Subject Re: json(b)_to_tsvector with numeric values
Date
Msg-id 34d4eb10-7b77-eb66-6198-89900a11fb56@sigaev.ru
Whole thread Raw
In response to Re: json(b)_to_tsvector with numeric values  (Dmitry Dolgov <9erthalion6@gmail.com>)
Responses Re: json(b)_to_tsvector with numeric values  (Dmitry Dolgov <9erthalion6@gmail.com>)
List pgsql-hackers
>> 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.


-- 
Teodor Sigaev                                   E-mail: teodor@sigaev.ru
                                                    WWW: http://www.sigaev.ru/


pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS
Next
From: Craig Ringer
Date:
Subject: Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS