Re: SQL/JSON revisited
От | Alexander Lakhin |
---|---|
Тема | Re: SQL/JSON revisited |
Дата | |
Msg-id | 60483139-5c34-851d-baee-6c0d014e1710@gmail.com обсуждение исходный текст |
Ответ на | Re: SQL/JSON revisited (Alvaro Herrera <alvherre@alvh.no-ip.org>) |
Ответы |
Re: SQL/JSON revisited
|
Список | pgsql-hackers |
Hi, 29.03.2023 13:27, Alvaro Herrera wrote: > ... and pushed it now, after some more meddling. > > I'll rebase the rest of the series now. Please look at the several minor issues/inconsistencies, I've spotted in the commit: 1) s/JSON_ARRRAYAGG/JSON_ARRAYAGG/ 2) check_key_uniqueness vs check_unique IIUC, these are different names of the same entity. 3) elog(ERROR, "invalid JsonConstructorExprType %d", ctor->type); vs elog(ERROR, "invalid JsonConstructorExpr type %d", ctor->type); I'd choose the latter spelling as the JsonConstructorExprType entity does not exist. 4) In the block: else { res = (Datum) 0; elog(ERROR, "invalid JsonConstructorExpr type %d", ctor->type); } res is assigned but never used. 5) (expr [FORMAT json_format]) ->? (expr [FORMAT JsonFormat]) (json_format not found anywhere else) Best regards, Alexander
В списке pgsql-hackers по дате отправления: