Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Re: retrieving varchar size

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Hirohama <kamesan(at)ricochet(dot)net>
Cc: pgsql-hackers(at)postgreSQL(dot)org, pgsql-interfaces(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Re: retrieving varchar size
Date: 1998-04-30 20:36:05
Message-ID: 13212.893968565@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-interfaces
Michael Hirohama <kamesan(at)ricochet(dot)net> wrote:
> The historical reason why the POSTGRES backend is required to send multiple
> result sets is to support cursors on queries involving type inheritance and
> anonymous target lists.
> 	begin
> 	declare c cursor for
> 		select e.oid, e.* from EMP* e
> 	fetch 10 in c
> 	...
> To handle the command sequence above, frontend applications would need to
> be provided with a new result descriptor when the "fetch 10 in c" crosses a
> result set boundary.

I tried this and was unable to produce a failure.  It looks like the
select only returns the set of fields applicable to the base class,
regardless of what additional fields may be possessed by some
subclasses.  Which, in fact, is more or less what I'd expect.

Is Michael remembering some old behavior that is no longer implemented?
And if so, is the old or new behavior the correct one?

			regards, tom lane

Responses

pgsql-hackers by date

Next:From: Tom Ivar HelbekkmoDate: 1998-04-30 21:01:57
Subject: Re: [INTERFACES] Access'97 and ODBC
Previous:From: aldevDate: 1998-04-30 18:55:57
Subject: PostgreSQL HOWTO Version 6.0 released

pgsql-interfaces by date

Next:From: Tom Ivar HelbekkmoDate: 1998-04-30 21:01:57
Subject: Re: [INTERFACES] Access'97 and ODBC
Previous:From: Tom LaneDate: 1998-04-30 18:42:58
Subject: Re: [HACKERS] Revised proposal for libpq and FE/BE protocol changes

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group