Bruce Momjian wrote:
> >
> > In the latter case, I would suggest an additional SQL command for open
> > cursors,
> > or a pseudo table for open cursor where you could do a simple select
> > statement:
> >
> > DECLARE CURSOR FOO_CURSOR FOR SELECT * FROM MYTABLE;
> >
> > SELECT _FIELD_NAME,_FIELD_TYPE,_FIELD_SIZE FROM
> > FOO_CURSOR_INFO_PSEUTOTABLE;
>
> The information you want is in pg_attribute.atttypmod. It is normally
> -1, but is set for char() and varchar() fields, and includes the 4-byte
> length. See bin/psql/psql.c for a sample of its use.
I see everyone writing in terms of length. You do mean precision, don't
you? For our purposes, this precision should arrive in the result
header. (redundancy in each tuple could be over looked) The goal is to be
able to put realistic bounds on memory allocation before the entire result is
read in. For this to work, functions must also be able to propagate the
their precision.
Did I spell doom to this idea?