CHAR_TO_UUID and UUID_TO_CHAR works different in big endian architectures - similar to CORE-2898 [CORE3887]

[firebird-automations]

Submitted by: @asfernandes

Value converted by UUID_TO_CHAR in little endian produce different result if used with CHAR_TO_UUID in big endian, and vice-versa.

Commits: b31f4d9 87d19fb e616957

[firebird-automations]

Commented by: @asfernandes

Important (for big-endian servers):
It has been discovered that before Firebird 2.5.2, CHAR_TO_UUID and UUID_TO_CHAR works
incorrectly in big-endian servers. In these machines, bytes/characters are swapped and goes in
wrong positions when converting. This bug was fixed in 2.5.2 and 3.0, but that means these
functions now returns different values (for the same input parameter) than before.

[firebird-automations]

Modified by: @asfernandes

Version: 2.5.1 [ 10333 ]

Version: 2.5.0 [ 10221 ]

Fix Version: 2.5.2 [ 10450 ]

summary: CHAR_TO_UUID and UUID_TO_CHAR works different in big/little endian architectures - inverted of CORE2898 => CHAR_TO_UUID and UUID_TO_CHAR works different in big/little endian architectures - similar to CORE2898

[firebird-automations]

Modified by: @asfernandes

summary: CHAR_TO_UUID and UUID_TO_CHAR works different in big/little endian architectures - similar to CORE2898 => CHAR_TO_UUID and UUID_TO_CHAR works different in big endian architectures - similar to CORE2898

[firebird-automations]

Modified by: @asfernandes

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

[firebird-automations]

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

[firebird-automations]

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: No test