Re: BUG #2917: spi_prepare doesn't accept typename
| От | Bruce Momjian |
|---|---|
| Тема | Re: BUG #2917: spi_prepare doesn't accept typename |
| Дата | |
| Msg-id | 200701270233.l0R2XcJ27247@momjian.us обсуждение исходный текст |
| Ответ на | Re: BUG #2917: spi_prepare doesn't accept typename aliases (Andrew Dunstan <andrew@dunslane.net>) |
| Ответы |
Re: BUG #2917: spi_prepare doesn't accept typename aliases
|
| Список | pgsql-hackers |
OK, what is the TODO wording? --------------------------------------------------------------------------- Andrew Dunstan wrote: > Jim Nasby wrote: > > On Jan 26, 2007, at 9:31 AM, Tom Lane wrote: > >> If you wanted to be a bit more ambitious maybe you could change the fact > >> that this code is throwing away typmod, which means that declarations > >> like "varchar(32)" would fail to work as expected. Perhaps it should be > >> fixed to save the typmods alongside the typioparams and then pass them > >> to InputFunctionCall instead of passing -1. On the other hand, we don't > >> currently enforce typmod for any function input or result arguments, so > >> maybe it's consistent that spi_prepare arguments ignore typmods too. > >> Thoughts? > > > > I'd like to see us move towards supporting that; both for function > > parameters/results as well as inside functions. It'd be nice if both > > cases got fixed at once, but IMHO fixing only one now would be better > > than fixing none. > > > > I'm not going to do either in fixing this bug - I think they should be > fixed but are a separate issue. These probably belong on the TODO list. > > cheers > > andrew > > > ---------------------------(end of broadcast)--------------------------- > TIP 3: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq -- Bruce Momjian bruce@momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
В списке pgsql-hackers по дате отправления: