Re: json(b)_to_tsvector with numeric values
От | Dmitry Dolgov |
---|---|
Тема | Re: json(b)_to_tsvector with numeric values |
Дата | |
Msg-id | CA+q6zcVr6oseeKpCvyGwWFYetgdshOZkKenuqAaVz=fqLk7_wQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: json(b)_to_tsvector with numeric values (Teodor Sigaev <teodor@sigaev.ru>) |
Ответы |
Re: json(b)_to_tsvector with numeric values
|
Список | 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
Вложения
В списке pgsql-hackers по дате отправления: