| Simon Riggs 2006-03-29, 3:30 am |
| On Wed, 2006-03-29 at 11:02 +0530, vidisha.shah@tcs.com wrote:
> CAUSE DETERMINATION
> ====================
> VARCHAR datatype from PostgreSQL is translated by your ODBC driver in
> an unsupported datatype for HSODBC.
>
>
> CAUSE JUSTIFICATION
> ====================
> In the trace file, you get the datatype from postgreSQL
> ====>1043 VARCHAR(50)
>
> then you get the datatype that ODBC driver is mapping to get back to
> Oracle
> ====>& #91;4464]describeCol
: col 2 *pfSqlType = -9
>
> If you look at in the Note 252548.1,
> -9 is SQL_WVARCHAR
>
> and unfortunately this ODBC datatype is not supported by the Generic
> Connectivity agent (HSODBC).
>
This is not a PostgreSQL problem, it is an Oracle problem and it is
clearly stated as such by them in the report you've posted.
VARCHAR is a standard SQL:2003 datatype, and SQL_WVARCHAR is the
standard ODBC value for that datatype. So this missing functionality
means that the Oracle Generic Connectivity agent has some very basic
features missing. If it were me and I'd paid for it, I'd ask for my
money back.
You'll need to find out what datatypes they do support so you can
spoonfeed something easier to them, possibly using a PostgreSQL view.
Best Regards, Simon Riggs
---------------------------(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
|