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

[Michael Meskes]

On Fri, Sep 27, 2002 at 09:53:02AM -0700, Joe Conway wrote:
 It is in 7.3.
 
 If the return tuple definition is fixed:
 instead of:
 exec sp_myproc()
 go
 do
 select * from sp_myproc();

That's a great feature to have. 

 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?

Unfortunately no. They are not willing to use a beta so they are appearantly switching 
to SAP DB. Sorry.

Michael
-- 
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

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

[Joe Conway]

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





---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]