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

Re: Problem with libpsqlodbc

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: gilles(at)darold(dot)net
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Problem with libpsqlodbc
Date: 2001-08-30 00:15:42
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-odbc
Gilles DAROLD wrote:
> Yes it work on other database but probably i'm missing something...

It's a limited spec of PostgreSQL that SELECT can call
function(procedure)s but SELECT returns a result set
not a parameter.

> For oracle they do
> create_proc => '{call create_person(?)}'
> add_proc      => '{call set_person_name(?,?)}'

It's an ODBC's spec to call a procedure.

> Is that the problem ? Should I use call ?

There seems to be 2 ways.

1) You could use the following.
    create_proc => '{?=call create_person(?)}'
    add_proc => '{?=call set_person_name(?, ?)}'
    (optional parameter marker ?= at the start of the syntax
     is needed if you need to accept the return value)
  But psqlodbc driver couldn't handle the syntax
  other than that of the latest snapshot.
  Could you try it ?

2) SELECT returns a result set.
  You could fetch and get the result using
  SQLFetch(), SQLGetData() etc.

Hiroshi Inoue

In response to

pgsql-odbc by date

Next:From: Marc G. FournierDate: 2001-08-30 16:25:10
Subject: Majordomo being upgraded ...
Previous:From: TerryDate: 2001-08-29 19:12:13
Subject: Re: msaccess

pgsql-general by date

Next:From: Martijn van OosterhoutDate: 2001-08-30 00:25:58
Subject: Re: RFC: PostgreSQL and MySQL comparison.
Previous:From: Russ McBrideDate: 2001-08-29 23:52:36
Subject: WebObjects (and PG vs. FrontBase)

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