Re: BUG #2556: ODBC driver version 2.00 doesn't publish functions correctly - Mailing list pgsql-bugs

From Jim Nasby
Subject Re: BUG #2556: ODBC driver version 2.00 doesn't publish functions correctly
Date
Msg-id 627FD333-C2D3-4FE7-957C-B8EF42D20012@pervasive.com
Whole thread Raw
In response to BUG #2556: ODBC driver version 2.00 doesn't publish functions correctly  ("Jon Watte" <pgfoundry.org@mindcontrol.org>)
List pgsql-bugs
Have you tried with a different client? In any case, you'll probably
get more help on pgsql-odbc.

On Jul 29, 2006, at 3:44 PM, Jon Watte wrote:
> The following bug has been logged online:
>
> Bug reference:      2556
> Logged by:          Jon Watte
> Email address:      pgfoundry.org@mindcontrol.org
> PostgreSQL version: 7.3
> Operating system:   Linux 2.4
> Description:        ODBC driver version 2.00 doesn't publish functions
> correctly
> Details:
>
> Define a function using pgAdmin III. Let's say we call it "next_id
> ()" and
> it's defined as "select max(id)+1 as next from sometable;".
>
> In Data Sources view in Visual Studio 2005, "configure dataset" on
> a dataset
> that connects to this database.
>
> Notice that the function doesn't show up under "functions" but it
> does show
> up under "stored procedures".
>
> Check the stored procedure checkbox for the "next_id" function, to
> include
> it in your data set view.
>
> You will get an error from visual studio saying that the "next_id"
> stored
> procedure wasn't actually found.
>
> It seems to me as if the ODBC driver has some confusion as to
> whether it's a
> function or a stored procedure, and this confusion means that
> Visual Studio
> can't use it.
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
>                http://archives.postgresql.org
>

--
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

pgsql-bugs by date:

Previous
From: Jim Nasby
Date:
Subject: Re: BUG #2558: initDB failed to run
Next
From: Jim Nasby
Date:
Subject: Re: BUG #2552: wrong sql dump?