Re: string function - "format" function proposal
От | Pavel Stehule |
---|---|
Тема | Re: string function - "format" function proposal |
Дата | |
Msg-id | AANLkTimfkWVrpNz_r2FL0aS7hhhC_hX27tEq4vuJyJh2@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: string function - "format" function proposal (Itagaki Takahiro <itagaki.takahiro@gmail.com>) |
Ответы |
Re: string function - "format" function proposal
|
Список | pgsql-hackers |
2010/8/30 Itagaki Takahiro <itagaki.takahiro@gmail.com>: > On Mon, Aug 30, 2010 at 7:58 PM, Pavel Stehule <pavel.stehule@gmail.com> wrote: >> propsals: >> * "format" function - uses same formatting as PL/pgSQL RAISE statement >> * "sprintf" function >> >> Now I propose a compromise - "format" function with only three tags: >> %s .. some string >> %i .. SQL identifier >> %l .. string literal > > These are just ideas: > > * Use $n, as like as PREPARE command. > It allows for us to swap arguments in any order. > SELECT format('$2 before $1', 'aaa', 'bbb') > what is use case for this feature? I don't see it. > * Call to_char() functions for each placeholder. > For example, > format('=={YYYY-MM-DD}==', tm::timestamp) > is equivalent to > '==' || to_char(tm, 'YYYY-MM-DD') || '==' > '{}' prints the input with the default format. > > New languages' libraries might be of some help. LLs, C#, etc. I though about integration with to_char function too. There are not technical barrier. And I can live with just {to_char_format} too. It can be or cannot be mixed with basic tags together - there is specified a NULL value behave. If we allow {format} syntax, then we have to specify a escape syntax for { and }. Do you have a some idea? Regards Pavel > > -- > Itagaki Takahiro >
В списке pgsql-hackers по дате отправления: