On 20/02/2020 08:54, Mark Rotteveel wrote:
> So, I assume that ISQL will use that character set information of a
> column - if present - and otherwise use the default encoding.
ISQL just output data received by client (which may be converted to the
client charset if specified), and that data, if s
On 2020-02-20 12:38, Jiří Činčura wrote:
Hi *,
do I remember correctly that when NONE is used i.e. in isql (simply on
client side) the "current" OS's charset is used?
When NONE is used, Firebird sends the stored bytes as-is, however
columns with an explicit character set will have that charac
20.02.2020 12:45, Jiří Činčura wrote:
The bytes will end up on screen as characters eventually (i.e. as isql's
output). Thus the bytes will be, sooner or later, converted to characters.
It is the Windows' part of work. Firebird accept raw bytes and return them as
is.
--
WBR, SD.
Fireb
>Nope. NONE means exactly that, no bytes interpretation at all.
Nope. The bytes will end up on screen as characters eventually (i.e. as isql's
output). Thus the bytes will be, sooner or later, converted to characters.
--
Mgr. Jiří Činčura
https://www.tabsoverspaces.com/
Firebird-Devel mai
20.02.2020 12:38, Jiří Činčura wrote:
do I remember correctly
Nope. NONE means exactly that, no bytes interpretation at all.
--
WBR, SD.
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
