Re: pgsql: Add more SQL/JSON constructor functions
От | Tom Lane |
---|---|
Тема | Re: pgsql: Add more SQL/JSON constructor functions |
Дата | |
Msg-id | 75664.1717435222@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: pgsql: Add more SQL/JSON constructor functions (Peter Eisentraut <peter@eisentraut.org>) |
Ответы |
Re: pgsql: Add more SQL/JSON constructor functions
|
Список | pgsql-hackers |
Peter Eisentraut <peter@eisentraut.org> writes: > On 02.06.24 21:46, Tom Lane wrote: >> If you don't >> like our current behavior, then either you have to say that RETURNING >> with a length-limited target type is illegal (which is problematic >> for the spec, since they have no such type) or that the cast behaves >> like an implicit cast, with errors for overlength input (which I find >> to be an unintuitive definition for a construct that names the target >> type explicitly). > It asks for the latter behavior, essentially (but it's not defined in > terms of casts). It says: Meh. Who needs consistency? But I guess the answer is to do what was suggested earlier and change the code to use COERCE_IMPLICIT_CAST. regards, tom lane
В списке pgsql-hackers по дате отправления: