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

Re: EXECUTE status (was Re: [ODBC] About server side prepare)

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>, <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: EXECUTE status (was Re: [ODBC] About server side prepare)
Date: 2002-12-23 01:35:38
Message-ID: GNELIHDDFBOCMGBFGEFOMELOCEAA.chriskl@familyhealth.com.au (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-odbc
> > Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> writes:
> > > Good catch. Hmm this may be a serious problem because
> > > there's no way to know the row count when we use EXECUTE
> > > statements.
> > 
> > I wonder if EXECUTE could/should be made to return the appropriate
> > command status string for the executed statement, instead of "EXECUTE".
> 
> Maybe it's preferable.

I agree.  Command status string is pretty essential!

Chris


In response to

pgsql-hackers by date

Next:From: Giles LeanDate: 2002-12-23 02:24:44
Subject: HP-UX shared library installation is incorrect
Previous:From: Hiroshi InoueDate: 2002-12-22 23:49:40
Subject: Re: EXECUTE status (was Re: [ODBC] About server side prepare)

pgsql-odbc by date

Next:From: HanDate: 2002-12-24 08:33:28
Subject: Multithread support for same connection?
Previous:From: Hiroshi InoueDate: 2002-12-22 23:49:40
Subject: Re: EXECUTE status (was Re: [ODBC] About server side prepare)

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