Hiroshi Inoue | 2 Aug 2008 07:50
Picon

Re: compiling dlg_specific.c file on Sun Solaris 5.8

Marcin Ligorowski wrote:
> I've detected problem with compiling dlg_specific.c file on Sun Solaris 5.8 using compiler 'cc: Sun C 5.8 2005/10/13'.
> To resolve this problem I've changed line 896 to
> qlog("          conn_settings='%s',conn_encoding='%s'\n",
> ci->conn_settings, enc ? enc : (UCHAR*)"(null)");
> 
> I've added cast to (UCHAR*), because compiler can not automatically cast to correct type.

OK I would take care of it.
Thanks.

regards,
Hiroshi Inoue

--

-- 
Sent via pgsql-odbc mailing list (pgsql-odbc <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Joost Kraaijeveld | 7 Aug 2008 09:51
Picon

Should/does SQLForeignKeys work (8.03.02)?

Hi,

I am trying to retrieve the foreign keys of/to a PostgreSQL table
(PostgreSQL ODBC 8.03.02, PostgreSQL 8.3.3, unixodbc 2.2.11) using ODBC.
But whatever I try I do not get any results.

I assume that if I do 

SQLForeignKeys(hstmt,
         NULL, 0,            /* Primary catalog */
         NULL, 0,            /* Primary schema */
         szTable, SQL_NTS,   /* Primary table */
         NULL, 0,            /* Foreign catalog */
         NULL, 0,            /* Foreign schema */
         NULL, 0);           /* Foreign table */

I should get all the foreign keys TO this table FROM another table.

Otherwise, doing

SQLForeignKeys(hstmt,
         NULL, 0,             /* Primary catalog */
         NULL, 0,             /* Primary schema */
         NULL, 0,             /* Primary table */
         NULL, 0,             /* Foreign catalog */
         NULL, 0,             /* Foreign schema */
         szTable, SQL_NTS);   /* Foreign table */

should get me all the foreign keys FROM this table TO another table.

(Continue reading)

Adam M | 8 Aug 2008 23:03
Picon

Re: resolution for bug 1010313

On Tue, Jul 29, 2008 at 2:36 AM, Marcin Ligorowski <ligo <at> interia.pl> wrote:

> Below is source code that I've implemented
> (I've send all ucs2_to_utf8 function source code)
>

Is it possible to attach your changes as a patch? In-line posting of
some code changes (and in non-patch format) really is not an ideal way
to post changes.

Thanks,
Adam

--

-- 
Sent via pgsql-odbc mailing list (pgsql-odbc <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Hiroshi Inoue | 9 Aug 2008 01:24
Picon

Re: Should/does SQLForeignKeys work (8.03.02)?

Joost Kraaijeveld wrote:
> Hi,
> 
> I am trying to retrieve the foreign keys of/to a PostgreSQL table
> (PostgreSQL ODBC 8.03.02, PostgreSQL 8.3.3, unixodbc 2.2.11) using ODBC.
> But whatever I try I do not get any results.

Seems the server side implementation of foreign keys was changed in 8.3
  and 8.3.02 ODBC drivers didn't know it.
I beleive the bug was fixed in 8.3.0201.

regards,
Hiroshi Inoue

--

-- 
Sent via pgsql-odbc mailing list (pgsql-odbc <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Tom Lane | 9 Aug 2008 01:59
Picon

Re: Should/does SQLForeignKeys work (8.03.02)?

Hiroshi Inoue <inoue <at> tpf.co.jp> writes:
> Seems the server side implementation of foreign keys was changed in 8.3
>   and 8.3.02 ODBC drivers didn't know it.
> I beleive the bug was fixed in 8.3.0201.

So ... when will that be released?

			regards, tom lane

--

-- 
Sent via pgsql-odbc mailing list (pgsql-odbc <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Hiroshi Inoue | 9 Aug 2008 02:41
Picon

Re: Should/does SQLForeignKeys work (8.03.02)?

Tom Lane wrote:
> Hiroshi Inoue <inoue <at> tpf.co.jp> writes:
>> Seems the server side implementation of foreign keys was changed in 8.3
>>   and 8.3.02 ODBC drivers didn't know it.
>> I beleive the bug was fixed in 8.3.0201.
> 
> So ... when will that be released?

I would talk with Hiroshi Saito about the next release.
Anyway I have not been able to commit changes to psqlodbc
for some days because the server responds with the message
 "waiting for anonymous's lock in /cvsroot/psqlodbc/psqlodbc".

Thanks.
Hiroshi Inoue

--

-- 
Sent via pgsql-odbc mailing list (pgsql-odbc <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Joost Kraaijeveld | 10 Aug 2008 19:11
Picon

c type of int8 / serial8?

Hi,

I wonder what the C type of int8 / serial8 is.

If I use SQLGetTypeInfo() to get all the supported type is says that
int8 is of SQL type SQL_BIGINT. It does not show any values for serial8
but I suppose that that is a user defined type and the driver is not
required to show those (is that correct?). 

If I use SQLColumns() and get the data type from that function, is says
for both int8 and serial8 that the SQL type is SQL_BIGINT. There is
however not mapping for SQL_BIGINT to a C type. There is a mapping to a
signed or unsigned 8 byte integer (SQL_C_SBIGINT or SQL_C_UBIGINT).

>From the docs
(http://www.postgresql.org/docs/8.3/interactive/datatype.html , table
8.1)  I see that int8 is a "signed eight-byte integer". For serial8 it
only says "autoincrementing eight-byte integer". So I assume that int8
is actually SQL_C_SBIGINT, but I am unsure about serial8: is it signed
or unsigned?

Shouldn't both SQLGetTypeInfo and SQLColumns return SQL_C_SBIGINT for
int8, and/or return SQL_C_SBIGINT/SQL_C_UBIGINT for serial8,. depending
on the signed-ness?

TIA

--

-- 
Groeten,

(Continue reading)

Joost Kraaijeveld | 11 Aug 2008 08:18
Picon

time with time zone sql type?

Hi,

Is there a reason why the sql type of a column with "time with time
zone" as returned by SQLColumns is SQL_VARCHAR and not SQL_TYPE_TIME?

For timestamp in both cases SQL_TYPE_TIMESTAMP is returned.

-- 
Groeten,

Joost Kraaijeveld
Askesis B.V.
Molukkenstraat 14
6524NB Nijmegen
tel: 024-3888063 / 06-51855277
fax: 024-3608416
web: www.askesis.nl

--

-- 
Sent via pgsql-odbc mailing list (pgsql-odbc <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Joost Kraaijeveld | 11 Aug 2008 22:55
Picon

int2: sql type bug?

Hi,

According to SQLColumns the sql type (DATA_TYPE) for a int2 column is
SQL_INTEGER. According to SQLGetTypeInfo the sql type is SQL_SMALLINT.

Is this a bug?

BTW: I am writing an application that uses the ODBC rather heavily. Is
ODBC actually maintained and is there someone who is prepared to answer
some questions (and accept (source)solutions for problems)?

-- 
Groeten,

Joost Kraaijeveld
Askesis B.V.
Molukkenstraat 14
6524NB Nijmegen
tel: 024-3888063 / 06-51855277
fax: 024-3608416
web: www.askesis.nl

--

-- 
Sent via pgsql-odbc mailing list (pgsql-odbc <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Hiroshi Inoue | 12 Aug 2008 04:50
Picon

Re: c type of int8 / serial8?

Joost Kraaijeveld wrote:
> Hi,
> 
> I wonder what the C type of int8 / serial8 is.
> 
> If I use SQLGetTypeInfo() to get all the supported type is says that
> int8 is of SQL type SQL_BIGINT. It does not show any values for serial8
> but I suppose that that is a user defined type and the driver is not
> required to show those (is that correct?). 

No.
serial8 is bigint not a user defined type.

xxxx=> create table tab1 (id serial8);
NOTICE:  CREATE TABLE will create implicit sequence "tab1_id_seq" for 
serial column "tab1.id"
CREATE TABLE
xxxx=> insert into tab1 values ('-9223372036854775808');
INSERT 0 1
xxxx=> select * from tab1;
           id
----------------------
  -9223372036854775808
(1 row)

--

-- 
Sent via pgsql-odbc mailing list (pgsql-odbc <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

(Continue reading)


Gmane