maria-developers team mailing list archive

[Sergei Golubchik <serg@xxxxxxxxxxxx>]

Hi, Alexander!

Could you report this bug and fix it, please?

On Apr 30, Alexander Barkov wrote:
> Hello,
> 
> This is definitely a bug.
> 
> 0xHHHH is a MySQL extension, and it's a hybrid thing.
> It can behave as a number and a string depending on context.
> 
> Binary log could use the X'HHHH' notation instead:
> 
> INSERT INTO t1 VALUES (a) VALUES (X'31');
> 
> which is an SQL standard, and which must always be a string.
> 
> However, it seems the behaviour of X'HHHH' and of 0xHHHH
> is exactly the same, and X'HHHH' can also act as a number.
... 
> I'd propose the following as a quick fix:
> 1. Fix X'HHHH' to work always as string.
> 2. Fix binlog to use X'HHHH'

Regards,
Sergei