>> PostgreSQL functions ignore typmod for parameters...
> ...not something that can be changed without a great
> deal of work --- and application breakage...
Thanks to all for the clarifications. I can make it return what I wanted wi=
th qualified character types by returning a SETOF RECORD types, where the r=
ecord type is a table or aggregate type. The key, it seems, is to avoid usi=
ng output parameters. But if RETURN TABLE doesn't respect typemods, perhaps=
it shouldn't be legal to specify them in that clause? I don't know. It jus=
t *seems* like a bug if you don=E2=80=99t know why your carefully crafted r=
eturn type is being partially ignored. But now I do, so thanks again.
I do think Pavel G. has a real bug with the char thing, though.
--- Kevin
