Re: Variadic polymorpic functions
От | Vincenzo Romano |
---|---|
Тема | Re: Variadic polymorpic functions |
Дата | |
Msg-id | 3eff28921001250048n3d40cdb2v4ce367eef163e5eb@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Variadic polymorpic functions (Pavel Stehule <pavel.stehule@gmail.com>) |
Ответы |
Re: Variadic polymorpic functions
Re: Variadic polymorpic functions |
Список | pgsql-general |
2010/1/25 Pavel Stehule <pavel.stehule@gmail.com>: > 2010/1/25 Vincenzo Romano <vincenzo.romano@notorand.it>: >> 2010/1/23 Pavel Stehule <pavel.stehule@gmail.com>: >>> 2010/1/22 Vincenzo Romano <vincenzo.romano@notorand.it>: >>>> 2010/1/22 Tom Lane <tgl@sss.pgh.pa.us>: >>>>> Vincenzo Romano <vincenzo.romano@notorand.it> writes: >>>>>> 2010/1/22 Tom Lane <tgl@sss.pgh.pa.us>: >>>>>>> regression=# CREATE FUNCTION q( fmt text, variadic args "any" ) >>>>> >>>>>> And this would allow for a stdarg-like argument list? >>>>> >>>>> Yeah, it should work, given suitable C code. >>>> >>>> Great! >>>> >>> >>> I wrote this function year ago. >>> >>> look on content >>> >>> http://pgfoundry.org/projects/pstcollection/ >> >> Pavel, >> that format() function should be included into official contribs. >> What about HOWTO compile? > > There are not consensus about final semantic - some people prefer > sprintf like, some others PostgreSQL RAISE NOTICE like. Whatever you prefer would be OK as far as it is documented. In my opinion, the main usage for such a function is in the dynamic SQL code generation in PL/PgSQL functions: EXECUTE pst.format( .... ); In this very case the sprintf-like syntax/semantics would be much more powerful, but the current one is OK if you think that there's nothing similar at the moment. Again, this function looks to be a badly missing one and including it at least into the default contrib collection would help a lot of users. -- Vincenzo Romano NotOrAnd Information Technologies NON QVIETIS MARIBVS NAVTA PERITVS
В списке pgsql-general по дате отправления: