Re: segfault in SQLSpecialColumns when table name is null string

On Mon, Jul 16, 2012 at 12:50:40AM +0900, Hiroshi Inoue wrote:
> (2012/07/15 14:02), Lionel Elie Mamane wrote:
>> On Sun, Jul 15, 2012 at 06:50:27AM +0900, Hiroshi Inoue wrote:
>>> (2012/07/10 23:27), Lionel Elie Mamane wrote:

>>>> Also, the ultimate reason for this "strange thing" is that

>>>> SQLColAttribute( (SQLHANDLE) 0x1ec7850,
>>>> (SQLUSMALLINT) 1,
>>>> (SQLUSMALLINT) 15,
>>>> (SQLPOINTER) 0x1eb2640,
>>>> 128,
>>>> (SQLSMALLINT *) 0x7fffffff97de,
>>>> NULL);

>>>> where 15 == SQL_DESC_TABLE_NAME == SQL_COLUMN_TABLE_NAME
>>>> returns (writes at 0x1eb2640) an empty string for this query:

>>>> SELECT "Num" "Numero", "data" FROM "foo"."Table1"

>>> What is your environment e.g. the version of your PG server
>>> or the version of your psqlodbc?

>> On Debian GNU/Linux amd64, Debian packages.

>> Client:
>> unixodbc 2.2.14p2-5
>> psqlodbc 09.01.0100
>> libpq5 9.1.3
>> Server:
>> postgresql 9.0.6

> SQLColattribute returns non null string here under Windows environment.
> Well how are you setting odbc.ini?

[PgSQL tst]
Description = PostgreSQL test
Driver = PostgreSQL Unicode
Trace = No
TraceFile =
Database = lobugs
Servername = pgsql.localdomain
Username =
Password =
Port = 5432
Protocol = 6.4
ReadOnly = No
RowVersioning = No
ShowSystemTables = No
ShowOidColumn = No
FakeOidIndex = No
ConnSettings =

odbcinst.ini:

[PostgreSQL Unicode]
Description = PostgreSQL ODBC driver (Unicode version)
Driver = psqlodbcw.so
Setup = libodbcpsqlS.so
Debug = 0
CommLog = 1
UsageCount = 1

--
Lionel