Re: Character invalid saving memo with UpdateSQL

I'll do this, thanks.

Cristian

----- Original Message -----
From: Leeuw van der, Tim
To: 'Cristian Custodio' ; pgsql-odbc(at)postgresql(dot)org
Sent: Thursday, November 27, 2003 11:17 AM
Subject: RE: [ODBC] Character invalid saving memo with UpdateSQL

Hi,

If you're converting an application from Oracle to PG, that implies that in the Oracle DB you also had such large VARCHAR fields. And since that didn't give trouble, it furthermore implies that the problem is in the PG ODBC drivers.

Perhaps you should file a bug against them?

I have a varchar(1000) field in my db but since it's not actually used I haven't ran into any trouble with my application (using C#) (it's just a comment-field and I haven't filled the comment with sensible and large things in my tests, and I'm the only one testing with PG from time to time - regular testing is with MySQL and Oracle, production on Oracle only).

About testing with MS-Access, I thought you could perhaps try to open the db tables as linked tables in Access, and execute an update-query from there just to see whether or not any garbage is entered into the database instead of the proper info.

regards,

--Tim

-----Original Message-----
From: pgsql-odbc-owner(at)postgresql(dot)org [mailto:pgsql-odbc-owner(at)postgresql(dot)org]On Behalf Of Cristian Custodio
Sent: donderdag 27 november 2003 15:06
To: pgsql-odbc(at)postgresql(dot)org
Subject: Re: [ODBC] Character invalid saving memo with UpdateSQL

Its imposible. We are converting ours application in Oracle to PG.

I will try create a trigger or a function to resolve this problem.

Thanks,

Cristian

----- Original Message -----
From: Leeuw van der, Tim
To: pgsql-odbc(at)postgresql(dot)org
Sent: Thursday, November 27, 2003 8:41 AM
Subject: Re: [ODBC] Character invalid saving memo with UpdateSQL

In quite a lot of databases, VARCHAR has an upper limit of 255 characters. I would say that most likely some of the libraries don't count of ever having a VARCHAR of greater length than that. It sounds like a buffer-overrun problem, but I couldn't say where - in the postgresql ODBC drivers, or in other parts of the odbc layers / libraries. Most like not in the postgresql drivers though.

I don't know what BDE is - some sort of library on top of ODBC? If so, what happens if you try to insert/update such long strings using direct ODBC? Or from another platform than Delphi, from MS-Access for instance?

regards,

--Tim
-----Original Message-----
From: pgsql-odbc-owner(at)postgresql(dot)org [mailto:pgsql-odbc-owner(at)postgresql(dot)org]On Behalf Of Cristian Custodio
Sent: donderdag 27 november 2003 12:59
To: pgsql-odbc(at)postgresql(dot)org
Subject: Re: [ODBC] Character invalid saving memo with UpdateSQL

I'm using LATIN1 but the problem happened with any other database.

It Occur with any varchar column greatest 255 characters.

Cristian

----- Original Message -----
From: Richard Combs
To: Cristian Custodio
Cc: pgsql-odbc(at)postgresql(dot)org
Sent: Wednesday, November 26, 2003 2:50 PM
Subject: Re: [ODBC] Character invalid saving memo with UpdateSQL

I haven't used the BDE in a while, however it looks like a problem with character sets. That is BDE is using one character set and PG is using another, hence the "invalid" characters. Check the postgreSQL documentation on localization to see how to make your server recognize other language (character) sets.

One other question, does this happen only with varchar and only with that one column, or can you duplicate the problem with character type in another column?

Cristian Custodio wrote:

I'm using delphi 5 and PG: 7.3.4 and BDE

I have 1 varchar(4000) column. When I try post any value in this column
using UpdateSQL it save very invalids caracters. Like this: ííííííííí.

Any body could help me?

Thanks,

Cristian Luciano Custodio