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

Re: [ODBC] [s.hetze@linux-ag.de: PostgreSQL integration Visual Basic,

From: Joe Conway <mail(at)joeconway(dot)com>
To: Michael Meskes <meskes(at)postgresql(dot)org>
Cc: PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org>,pgsql-odbc(at)postgresql(dot)org
Subject: Re: [ODBC] [s.hetze@linux-ag.de: PostgreSQL integration Visual Basic,
Date: 2002-09-27 16:53:02
Message-ID: 3D948CEE.3040105@joeconway.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-odbc
Michael Meskes wrote:
> into. As far as I understand the problem, the application uses stored
> procedures for each and every select statement. Thus he needs his
> procedures to return the whole query result, which is not doable with
> our functions.

It is in 7.3.

If the return tuple definition is fixed:
instead of:
     exec sp_myproc()
     go
do
     select * from sp_myproc();

If the return tuple definition is *not* fixed:
do
     select * from sp_myproc() as table_alias([col definition list]);

Does this help any? Can he try the 7.3 beta?

Joe





In response to

Responses

pgsql-hackers by date

Next:From: Roland RobertsDate: 2002-09-27 17:29:03
Subject: Re: [SQL] CURRENT_TIMESTAMP
Previous:From: Tom LaneDate: 2002-09-27 16:51:50
Subject: Re: query speed depends on lifetime of frozen db?

pgsql-odbc by date

Next:From: Neil ConwayDate: 2002-09-28 00:17:42
Subject: status of ODBC driver?
Previous:From: JPTrueDate: 2002-09-27 14:12:25
Subject: Re: Text-Varchar Truncation via ODBC

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