Re: json(b)_to_tsvector with numeric values

Dmitry Dolgov <9erthalion6@gmail.com>

From: Dmitry Dolgov <9erthalion6@gmail.com>
To: Teodor Sigaev <teodor@sigaev.ru>
Cc: Arthur Zakirov <a.zakirov@postgrespro.ru>, Oleg Bartunov <obartunov@postgrespro.ru>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2018-04-04T11:27:16Z
Lists: pgsql-hackers
> On 4 April 2018 at 11:52, Teodor Sigaev <teodor@sigaev.ru> wrote:
>>>> the consistency of FTS.I think this is a bug, which needs to be fixed,
>>>> else inconsistency with existing full text search  will be gets
>>>> deeper.
>
> 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.


Commits

  1. Add json(b)_to_tsvector function