Icon View Incident Report

Minor Minor
Reported By: Rolf Frei
Reported On: 3/24/2016
For: Version 2.22 Build 2
# 4370 IMPORT TABLE/EXPORT TABLE Statements Not Setting Encoding Correctly for ENCODING AUTO

For some unknown reason, I'm not able to export a table with the EBD Manager build in export function and its encoding setting of Auto. The description states, that it will use the encoding of the DB if it is set to Auto, but this seems not to be true. My Database/Session is setup as ANSI, but an export does still genarate a unicode file. So I'm forced to set the encoding manually to ANSI, which will work fine.

Comments Comments
The manual states that it will use the encoding of the *engine*, but now that there's the Unicode/ANSI character set selection per session (as of 2.15), this is a little less clear.

In general, how it worked is that ElevateDB would use Unicode if the compiler was Unicode, and Ansi if the compiler was Ansi. The EDB Manager is/was compiled with a Unicode compiler, so the EDB Manager defaulted to using Unicode when ENCODING AUTO was used.

Now, ElevateDB always uses the character set setting of the session (for local sessions) and the EDB Server (for remote sessions) when ENCODING AUTO is used for the IMPORT/EXPORT TABLE statements.

Resolution Resolution
Fixed Problem on 3/26/2016 in version 2.23 build 1

Products Affected Products Affected
ElevateDB Additional Software and Utilities
ElevateDB DAC Client-Server
ElevateDB DAC Client-Server with Source
ElevateDB DAC Standard
ElevateDB DAC Standard with Source
ElevateDB DAC Trial
ElevateDB LCL Standard with Source
ElevateDB PHP Standard
ElevateDB PHP Standard with Source
ElevateDB PHP Trial
ElevateDB VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial