Re: Unicode support

Hello Dave,

I'm just trying the last fix (for BDE) and I can see some odd behavior.

- It shows the TEXT fields as MEMO. But you can see the data if you make a
double click on it. It looks like it doesn't use the "text as LongVarchar"
option (this works in version 7.x).

- After a "SELECT * FROM table" The Borland SQL Explorer shows an error
('Invalid Blob Handle') for empty TEXT fields (NULL) when you try to view
them. This works fine for table view.

- After an error inserting a row ('not null' constraint) it closes the
connection (dead connection error)


Regards,

Miguel Juan




----- Original Message -----
From: "Dave Page" <dpage@vale-housing.co.uk>
To: "Miguel Juan" <mjuan@cibal.es>
Cc: <pgsql-odbc@postgresql.org>
Sent: Thursday, September 01, 2005 10:32 AM
Subject: RE: [ODBC] Unicode support


Yes please - attached.

> -----Original Message-----
> From: Miguel Juan [mailto:mjuan@cibal.es]
> Sent: 01 September 2005 09:25
> To: Dave Page
> Cc: pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] Unicode support
>
> hello,
>
> I will try it with BDE environment if you want.
>
> Regards,
>
> Miguel Juan
>
>
> ----- Original Message -----
> From: "Dave Page" <dpage@vale-housing.co.uk>
> To: "Anoop Kumar" <anoopk@pervasive-postgres.com>
> Cc: <pgsql-odbc@postgresql.org>
> Sent: Tuesday, August 30, 2005 11:36 PM
> Subject: [ODBC] Unicode support
>
>
> Hi Anoop and anyone else who might be interested,
>
> I've been thinking about how the Unicode support might be improved to
> allow the old 07.xx non-unicode style behaviour to work for those that
> need it. At them moment, when we connect using on of the wide connect
> functions, the CC->unicode flag is set to true. This only
> affects a few
> options, such as pgtype_to_concise_type()'s mapping of PG types to SQL
> types.
>
> It seems to me that perhaps we should set CC->unicode = 1, only upon
> connection to a Unicode database. Anything else, we leave it
> set to 0 so
> that it always maps varchars etc to ANSI types, and handles other
> encodings in single byte or non-unicode multibyte mode (which worked
> fine in 07.xx where those encodings where appropriate, such as SJIS in
> Japan). This should also help BDE based apps, which further
> research has
> shown me are broken with Unicode columns in SQL Server and Oracle as
> well as PostgreSQL (search unicode + BDE on Google Groups for more).
>
> Am I seeing a possible improvement where in fact there isn't one, or
> missing some obvious downside?
>
> Regards, Dave.
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
>
>