Re: Unicode support

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Miguel Juan" <mjuan(at)cibal(dot)es>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: Unicode support
Date: 2005-09-01 11:17:50
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4AC9DE0@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

> -----Original Message-----
> From: Miguel Juan [mailto:mjuan(at)cibal(dot)es]
> Sent: 01 September 2005 11:06
> To: Dave Page
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] 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).

Right, I'll look at that.

> - 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.

Strange.

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

I'll test that as well.

To be honest though, I've been researching BDE on Google Groups and
there are lots of people reporting similar problems with SQL Server and
Oracle - apparently BDE fails to work properly with any Unicode data.
I'm happy to spend a little time trying to work around that, but I can't
spend masses of time on it.

Regards, Dave.

Browse pgsql-odbc by date

  From Date Subject
Next Message Dave Page 2005-09-01 12:55:06 Re: figuring out why I am having this issue
Previous Message Miguel Juan 2005-09-01 10:05:37 Re: Unicode support