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
I'm using LATIN1 but the problem happened with any other database.
It Occur with any varchar column greatest 255 characters.
Cristian
----- Original Message -----
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
