Dec 23rd, 2011, 11:32 AM
Hey Teamwebb,
Yes, it's a drag, I know... I spent ages trying to figure out a more elegant solution. Unfortunately, the SQL error returned by the server doesn't specify by how much the row is too large - and the math is surprising tricky, since the table charset influences the allocated space for varchar fields. I think there's a better solution somewhere, I just haven't found an approach.
Anyway, I hope the 2.1.9 update at least provides a better error message for the scenario.
- Ben
Yes, it's a drag, I know... I spent ages trying to figure out a more elegant solution. Unfortunately, the SQL error returned by the server doesn't specify by how much the row is too large - and the math is surprising tricky, since the table charset influences the allocated space for varchar fields. I think there's a better solution somewhere, I just haven't found an approach.
Anyway, I hope the 2.1.9 update at least provides a better error message for the scenario.
- Ben