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
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-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

Browse pgsql-hackers by date

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

Browse pgsql-odbc by date

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