From: | Jim Nasby <jnasby(at)pervasive(dot)com> |
---|---|
To: | Jon Watte <pgfoundry(dot)org(at)mindcontrol(dot)org> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #2556: ODBC driver version 2.00 doesn't publish functions correctly |
Date: | 2006-08-08 17:24:24 |
Message-ID: | 627FD333-C2D3-4FE7-957C-B8EF42D20012@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(dot)org(at)mindcontrol(dot)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(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2006-08-08 17:26:33 | Re: BUG #2555: runtime error 80040e21 |
Previous Message | Jim Nasby | 2006-08-08 17:22:55 | Re: BUG #2552: wrong sql dump? |