firebird-automations
commented
11 years ago Commented by: @mrotteveel
I don't see the advantage of this over the normal hexadecimal notation (if anything it makes it harder to read and adds additional overhead because now you need to include a slash and an x for every byte).
Also what are '3-digit bytes'? Bytes are 8 bits and are represented by 0x00 to 0xFF.
Submitted by: Andrea Spanu (jurhas)
Votes: 1
With the new "Hexadecimal notation for "binary" strings" should be interessant to have the possibility to separate the bytes with a back slash or a space or something other.
For example the string :
E'\x20\xD\xA\x20\x20\x31\x20' it means :" \015\012 1 " (postgres notation) x'20DA20203120' it means: " \332 1 "
I know, you can say to put 0´s in advance so to have ever 2n digits, but the same can not understand the 3-digit bytes100 to 1FF). I think can be easely to implement and is also usefull. Or also a Decoder from Base64 function. It give the possibility to insert each kind of blob via string.