BUG #3537: Postgres odbc can only access public schema and any other schema does not work - Mailing list pgsql-bugs

From maya
Subject BUG #3537: Postgres odbc can only access public schema and any other schema does not work
Date
Msg-id 200708150832.l7F8W0cq029708@wwwmaster.postgresql.org
Whole thread Raw
List pgsql-bugs
The following bug has been logged online:

Bug reference:      3537
Logged by:          maya
Email address:      maya.govender@ebucks.com
PostgreSQL version: 08.02.0400
Operating system:   solaris 9 64 bit
Description:        Postgres odbc can only access public schema and any
other schema does not work
Details:

Hi ,

I have a solaris 9 64 bit server with sas installed.I have unix odbc 2.2
installed and psqlodbc08.02.0400 installed.i can access only the public
schema and any other schema i cannot.I am test from the sas application ,
see comments from SAS

SAS query the odbc driver regarding Schema usage and the PostgreSQL driver
comes back basically saying "no schema usage". Therefore tables are not
prefix'ed with the schema.

ODBC: ENTER SQLGetInfo
             0x000000000033e530
                             91 <SQL_SCHEMA_USAGE>
             0x0000000078024528
                              4
             0x000000007307c0fe

ODBC: EXIT SQLGetInfo with return code 0 (SQL_SUCCESS)
             0x000000000033e530
                             91 <SQL_SCHEMA_USAGE>
             0x000000007307bf4c (0) <>      <---- This is the information
returned from the PostgreSQL driver - no schema usage
                              4
             0x000000007307c0fe (4)

This is what the driver should return (exmple with oracle's odbc driver):

ODBC: EXIT SQLGetInfo with return code 0 (SQL_SUCCESS)
             0x049a1348
                     91 <SQL_SCHEMA_USAGE>
             0x0495f028 (31) <SQL_SU_DML_STATEMENTS |
SQL_SU_PROCEDURE_INVOCATION | SQL_SU_TABLE_DEFINITION |
SQL_SU_INDEX_DEFINITION
| SQL_SU_PRIVILEGE_DEFINITION>
                      4
             0x0495f2be (4)


I suggest that they contact the ODBC driver vendor with the issue. Maybe
there is an option to turn on the schema usage within the driver
configuration."


TX

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: ON DELETE SET NULL clauses do error when more than two columns are referenced to one table
Next
From: "Erik R."
Date:
Subject: BUG #3539: tsearch2 broken on Intel Macs running Leopard