Re: Regression test failures on big endian

Re: Inoue, Hiroshi 2016-04-05 <5702F6C6.6010707@dream.email.ne.jp>
> Hi Christoph,
>
> Sorry for the late reply.

Thanks for the reply :)

> >>! '1234567' (int4) as SQL_C_BINARY: hex: 87D61200
> >>! '1234567' (int4) as SQL_C_BINARY: hex: 0012D687
>
> The difference above is a natural outcome from the difference of endianness.

Ah, on a second look that's indeed the case. I'll blame myself for
still not being comfortable with reading "context" diffs where
original and changed version are way apart.

Thanks for confirming this is an expected change. I'll proceed to
submit some _1.out files.

> >>! '' (text) as SQL_C_WCHAR:
\FF00\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF
(truncated)
> >>! '' (text) as SQL_C_WCHAR: \
FF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF
(truncated)
>
> The difference above means that encoding of Unicode is UTF-16LE whichever
> the endianness is.

Ew. There should be a law forbidding everything except UTF-8 :)

> Is it as you expected?

Thanks for the confirmation!

Christoph