Re: RfD: more powerful "any" types
От | Pavel Stehule |
---|---|
Тема | Re: RfD: more powerful "any" types |
Дата | |
Msg-id | 162867790909101205u7cdf763k5c4159f25bc77fce@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: RfD: more powerful "any" types (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: RfD: more powerful "any" types
|
Список | pgsql-hackers |
2009/9/10 Tom Lane <tgl@sss.pgh.pa.us>: > Pavel Stehule <pavel.stehule@gmail.com> writes: >> 2009/9/10 Tom Lane <tgl@sss.pgh.pa.us>: >>> I think the point of it is that people are used to how sprintf works. >>> So it should work as nearly like sprintf as possible. > >> How sprintf will be print bytea type, or char(n) type values? > > Well, that's why it requires some actual thought and agreement on a > specification --- sprintf just crashes on type mismatches, but perhaps > the SQL version should be smarter. You shouldn't expect that the > easiest thing to throw together is going to be considered the most > desirable solution. I don't afraid about crashing. Simply I have not idea what sql sprintf's behave in case: SELECT sprintf('some %s', 10) or SELECT sprintf('some %d', 10::mycustomtype) ??? > > regards, tom lane >
В списке pgsql-hackers по дате отправления: