[progress Communities] [progress Openedge Abl] Forum Post: Re: Longchar Conversion Error...

  • Thread starter Thread starter Garry Hall
  • Start date Start date
Status
Not open for further replies.
G

Garry Hall

Guest
CHARACTER field data in the database is always intended to be in the database's codepage. This allows the AVM to provide automatic codepage conversion between the database and the client session's -cpinternal. IT also ensures indexing works correctly. However, it is possible to insert data that is not in the database codepage into the database, by bypassing the automatic conversions the AVM provides, or not appreciating the encoding of the input file. For example, if you have a file encoded as 1252, and an AVM running -cpinternal UTF-8 -cpstream UTF-8, and you INPUT from the file without specifying CODEPAGE SOURCE "1252", then you are telling the AVM that the data is in UTF-8. As -cpinternal == -cpstream, there is no codepage conversion done when reading this data. The data is not validated to ensure it is correctly encoded as UTF-8, for performance reasons (I know of a customer situation where there was a request to add this validation, I can't remember the exact details or the outcome).

Continue reading...
 
Status
Not open for further replies.
Back
Top