MAX_ALLOWED_PACKET and MySQL >= 5.1.31
Bug #622194 reported by
fisharebest
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
webtrees |
Fix Released
|
Medium
|
fisharebest |
Bug Description
MySQL cannot import gedcoms larger than the value specified in the system parameter max_allowed_packet.
MySQL 5.1.30 and earlier allow an application to change this parameter - webtrees does this and it works OK.
MySQL 5.1.31 and later ignore requests to change this parameter, and imports fail.
To fix this, we will need to split the gedcom file into "chunks", and store each chunk in a separate row in a new table.
This will cause various problems, incuding splitting multi-byte characters. We do not know the encoding until after the import, but we need to know it beforehand to avoid splitting characters.
Changed in webtrees: | |
status: | New → Confirmed |
To post a comment you must log in.
In the short term (thinking of before ver 1.0.0 release) is it worth adding a warning where the MySQL version is identified as >5.1.30 and file size is greater than max_allowed_packet setting, with a link to our WIKI section on changing the setting (assuming such a check can be done)?