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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-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
From | Date | Subject | |
---|---|---|---|
Next Message | Roland Roberts | 2002-09-27 17:29:03 | Re: [SQL] CURRENT_TIMESTAMP |
Previous Message | Tom Lane | 2002-09-27 16:51:50 | Re: query speed depends on lifetime of frozen db? |
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2002-09-28 00:17:42 | status of ODBC driver? |
Previous Message | JPTrue | 2002-09-27 14:12:25 | Re: Text-Varchar Truncation via ODBC |