MySQL LONGBLOB truncated?

Question

MySQL

There is a DB with a column of type LONGBLOB, but something at an insertion miracles are created.
I insert binary data of 8192 bytes - 6855 bytes are saved, where the rest have gone is not clear.
I insert 34152 bytes, purely out of interest - only 33738 bytes are saved, again a part was cut off.
What am I missing, can this situation be normal?
MariaDB 10.1.4 InnoDB.

Answer 1

Most likely this is a bug in phpMyAdmin, and I trusted him...
A ticket has been opened in their tracker: https://sourceforge.net/p/phpmyadmin/bugs/4972/
UPD: it's a bug, already fixed in the git version

Answer 2

Does SQL query use LOAD_FILE or a hex string?
If it's a string, check whether the data in the string itself is truncated first. It may also be that the string is not long enough. Maybe even something with encoding.
Still unlikely, but it could be a network issue.