[MDEV-6404] max_allowed_packet Created: 2014-06-28 Updated: 2023-06-09 Resolved: 2014-07-19 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | 10.0.7 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Trivial |
| Reporter: | Miroslav Tzonkov | Assignee: | Unassigned |
| Resolution: | Not a Bug | Votes: | 1 |
| Labels: | max_allowed_packet | ||
| Environment: |
debian testing amd64, AMDFX8320, SSD, HDD, 16GRAM |
||
| Issue Links: |
|
||||||||
| Description |
|
max_allowed_packet maximum size is 1GB, however I want to insert LARGEBLOBS - 4GB. |
| Comments |
| Comment by Miroslav Tzonkov [ 2014-06-30 ] |
|
workaround by temp table and max_allowed_packet / 2 sized packets |
| Comment by Axel Schwenke [ 2014-06-30 ] |
|
If you use the C API to access MySQL and if you use the prepared statement protocol, then you can send a BLOB in multiple pieces. The packet size limit applies to each piece you send, but the BLOB as a whole can be larger. This is done with the API function mysql_stmt_send_long_data() which is documented in the MySQL manual here. There is even an example how to use that function. You didn't say which connector you use to connect to MySQL. But if your connector is based on libmysqlclient (aka the C connector) then there is a certain chance that it exports this function as well. |
| Comment by Elena Stepanova [ 2014-07-19 ] |
|
I'm closing this for now as not a bug. If you disagree or/and want to convert it to a feature request, please feel free to comment to-reopen. |