Re: psqlODBC-Driver Test / text fields

From: Johann Zuschlag <zuschlag2(at)online(dot)de>
To: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: psqlODBC-Driver Test / text fields
Date: 2006-03-27 15:50:45
Message-ID: 442809D5.2030805@online.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Dave Page schrieb:

>OK, that sounds like the old bug we were seeing. What is the difference
>between those and the previous results you reported a few minutes ago?
>Is it just the text/varchar difference?
>
>Regards, Dave.
>
>
>

Hi Dave,

the problem doesn't seem to be related to the text field. Please note
the examples below:

1. Searching for a string starting with a 't' seems to work fine:

2006-03-27 16:49:48 [2931] LOG: statement: declare "SQL_CUR0210FD50"
cursor with hold for SELECT t6.* FROM KUNDE t6 WHERE t6.name >= 't' AND
t6.name <= 'tz' ORDER BY t6.name ASC, t6.kundenid ASC

2. Searching for a string starting with o-Umlaut (german character)
doesn't return any results (in my app.).

2006-03-27 16:50:37 [2931] LOG: statement: declare "SQL_CUR0210FD50"
cursor with hold for SELECT t6.* FROM KUNDE t6 WHERE t6.name >= 'ö'
AND t6.name <= 'öz' ORDER BY t6.name ASC, t6.kundenid ASC

Maybe the WHERE-statement is not parsed by the driver. But the hex
representation of 'ö' is 'C3B6', that is the correct UTF8 code (not
unicode) of o-Umlaut.

3. Furthermore I noticed that I wouldn't get anything back if the
searched string contains any "Umlauts". So I guess there could be a
problem with the result set too.

SELECT without a WHERE-statement works.

Any ideas?

A mylog ist available, as well as the tiny data set (6 lines)..

Hope that helps.

Regards,
Johann

In response to

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Hiroshi Inoue 2006-03-27 18:44:09 Re: psqlODBC-Driver Test / text fields
Previous Message Johann Zuschlag 2006-03-27 13:00:32 Re: psqlODBC-Driver Test / text fields