I found some references to issues with unicode and HSODBC. We created a
new DSN using PostgreSQL ANSI and all works well.
----- Original Message -----
Subject: Re: [ODBC] Oracle HSODBC problems
From: "Jonah H. Harris" <jonah.harris@gmail.com>
Date: Wed, August 30, 2006 12:00
On 8/30/06, LLC <kevin@kevinkempterllc.com> wrote:
> I do have the database name in the ODBC DSN but it seems to have no
> effect. In the below samples, sample 1 works and sample 2 does not.
Hmm... I've gotten it to work before with differing database names. I
don't recall doing anything special to configure it.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation | fax: 732.331.1301
33 Wood Ave S, 2nd Floor | jharris@enterprisedb.com
Iselin, New Jersey 08830 | http://www.enterprisedb.com/
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match