Skip site navigation (1) Skip section navigation (2)

Re: Issues when using schema names with odbc

From: <michael(dot)28(dot)smith(at)bt(dot)com>
To: <michael(dot)28(dot)smith(at)bt(dot)com>, <inoue(at)tpf(dot)co(dot)jp>
Cc: <pgsql-odbc(at)postgresql(dot)org>, <stephen(dot)hindmarch(at)bt(dot)com>
Subject: Re: Issues when using schema names with odbc
Date: 2010-11-29 15:03:19
Message-ID: 806CB309AA19EE4F8F30EB5DF3E372B33B5E635C4D@EMV61-UKRD.domain1.systemhost.net (view raw or flat)
Thread:
Lists: pgsql-odbc
Attaching test app source for reference.



Mike Smith
Voice & Multimedia Platform | BT Innovate & Design
Tel: +44 (0) 20 7876 8005
ClickDial Me


-----Original Message-----
From: Smith,M,Michael,DLW C 
Sent: 29 November 2010 14:51
To: 'Hiroshi Inoue'
Cc: pgsql-odbc(at)postgresql(dot)org; Hindmarch,SJ,Stephen,DLW R
Subject: RE: [ODBC] Issues when using schema names with odbc

Used a little test app to verify this and I get different results,

Assuming create schema test_schema;

create table public.test(
	row1 int,
	row2 text);

create table test_schema.test(
	row_t_1 int,
	row_t_2 text);

grant usage on schema test_schema to public;
grant select on public.test to public;
grant select on test_schema.test to public;

insert into public.test values (1,'public schema');
insert into test_schema.test values (2,'test schema');



The test app shows the following results....:


[root(at)winston scripts]# ./sqltest
SQLColumns Connection Test
Handles Allocated

Getting columns from test_schema.test
No data!

Getting all rows from test_schema.test
Row 0:1=2;2=test schema;

Getting columns from public.test
No data!

Getting all rows from public.test
Row 0:1=1;2=public schema;

Getting columns from (null).test
Column 0: row
Column 1: row
Column 2: row
Column 3: row

Getting all rows from (null).test
Row 0:1=1;2=public schema;


It shows that when using schema.table_name no column data is returned, but returns when not using a schema name.

Any other ideas?

Cheers


Mike Smith
Voice & Multimedia Platform | BT Innovate & Design
Tel: +44 (0) 20 7876 8005
ClickDial Me


-----Original Message-----
From: Hiroshi Inoue [mailto:inoue(at)tpf(dot)co(dot)jp] 
Sent: 20 November 2010 02:33
To: Smith,M,Michael,DLW C
Cc: pgsql-odbc(at)postgresql(dot)org; Hindmarch,SJ,Stephen,DLW R
Subject: Re: [ODBC] Issues when using schema names with odbc

(2010/11/19 1:22), michael(dot)28(dot)smith(at)bt(dot)com wrote:
> I think there is an issue with the following version of postgresql-odbc
> where I am unable to use schema names.
>
> Using "isql " "help table_name" returns information about the column
> names but "help schema.table_name returns nothing.

ODBC doesn't handle schema_name.table_name type format.
For example the syntax of SQLColumns() is as follows.

	SQLRETURN SQLColumns(
		SQLHSTMT       StatementHandle,
		SQLCHAR *      CatalogName,
		SQLSMALLINT    NameLength1,
		SQLCHAR *      SchemaName,
		SQLSMALLINT    NameLength2,
		SQLCHAR *      TableName,
		SQLSMALLINT    NameLength3,
		SQLCHAR *      ColumnName,
		SQLSMALLINT    NameLength4);

regards,
Hiroshi Inoue

> This assumes the identical tables are in public.table_name and
> schema.table_name
>
> I actually come across this when using asterisk realtime - I was about
> to raise this as an asterisk issue and came across this - which suggests
> it is actually an underlying odbc issue.
>
> https://issues.asterisk.org/view.php?id=15963
>
> Has this been seen before..?
>
> Many Thanks
>
> Mike
>
> rpm -qa |grep odbc
>
> postgresql-odbc-08.01.0200-3.1
>
> rpm -qa |grep postgres
>
> postgresql-server-8.1.11-1.el5_1.1
>
> postgresql-libs-8.1.11-1.el5_1.1
>
> postgresql-8.1.11-1.el5_1.1
>
> postgresql-libs-8.1.11-1.el5_1.1
>
> postgresql-odbc-08.01.0200-3.1
>
> Asterisk 1.6.2.12

Attachment: sqltest.c
Description: text/plain (5.5 KB)

In response to

pgsql-odbc by date

Next:From: Hiroshi InoueDate: 2010-11-30 14:17:30
Subject: Re: Issues when using schema names with odbc
Previous:From: michael.28.smithDate: 2010-11-29 14:51:00
Subject: Re: Issues when using schema names with odbc

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group