Re: Data loss when '"json_populate_recorset" with long column name

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: Data loss when '"json_populate_recorset" with long column name
Дата
Msg-id YTb5F5/jwZNOwf37@paquier.xyz
обсуждение исходный текст
Ответ на Re: Data loss when '"json_populate_recorset" with long column name  (Julien Rouhaud <rjuju123@gmail.com>)
Ответы Re: Data loss when '"json_populate_recorset" with long column name  (Julien Rouhaud <rjuju123@gmail.com>)
Список pgsql-hackers
On Tue, Sep 07, 2021 at 01:11:49PM +0800, Julien Rouhaud wrote:
> Yes, that's because json identifiers have different rules from
> relation identifiers.  Your only option here is to use the real /
> truncated identifier.  Also I don't think it would be a good thing to
> add a way to truncate identifiers in json objects using the
> NAMEDATALEN limit, as this could easily lead to invalid json object
> that should be valid.

Yeah.  We should try to work toward removing the limits on NAMEDATALEN
for the attribute names.  Easier said than done :)
--
Michael

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: when the startup process doesn't (logging startup delays)
Следующее
От: Amit Kapila
Дата:
Сообщение: Re: Column Filtering in Logical Replication