Ok, you may have a totally different problem. You have
posted about storing audio recordings before and seemed to indicate that you use the
LONGTEXT column type which can store up to 4GB of text. So my above answer my be mute. What you are most likely running into is that your SQL statement becomes too long since you are embedding the value of your music file into the SQL statement. The maximum length that an SQL statement can be can be found in the MariaDB documentation and has something to do with the "
max_allowed_packet" size. Depending on which version of MariaDB is running on the server, this size ranges from 1MB to 16MB. If it is the lower limit, a 800K audio file can easily blow this limit (due to base64 overhead). The answer to this then would be to
1) Use parameterized SQL queries. Since you must be using a 3rd part SQL library (Android does not support MySQL/MariaDB out of the box) you have to look at it and see if it provides methods for handling parameterized SQL queries.
2) Modify the configuration of your database server to accept larger SQL queries.
Please note this is just another (un)educated guess, since I have no means to reproduce your application/server setup and I'm only going off of the symptoms that you are experiencing.