| From: | Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Mathematical Functions and Operators |
| Date: | 2024-10-09 21:41:37 |
| Message-ID: | CAB-JLwZ1Ga7TFuZ_1RstE8Pxw8WpmVNGhK_kVj_YEuCRpt9UEw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Em qua., 9 de out. de 2024 às 18:23, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> escreveu:
>
> Replaceable means the user is expected to substitute an expression in that
> location. One cannot specify a function name using an expression.
>
Sorry, I thought function parameters but said names. So, function params
should have <replaceable> too ?
If you see JSON functions there are functions that their params have
<replaceable> tag
json_array ( [ *query_expression* ] [ RETURNING *data_type* [ FORMAT
JSON [ ENCODING
UTF8 ] ] ])
json_scalar ( *expression* )
json_serialize ( *expression* [ FORMAT JSON [ ENCODING UTF8 ] ] [ RETURNING
*data_type* [ FORMAT JSON [ ENCODING UTF8 ] ] ] )
they are fine, but a lot of others don't
to_json ( anyelement ) → json
json_object ( text[] ) → json
regars
Marcos
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2024-10-09 22:14:03 | Re: sunsetting md5 password support |
| Previous Message | David G. Johnston | 2024-10-09 21:23:54 | Re: Mathematical Functions and Operators |