WeBWorK Problems

Data too long for 'frozen_hash'

Data too long for 'frozen_hash'

by Tim Flowers -
Number of replies: 2

This error has been popping up for us lately. I am not sure if it is a server issue or an issue with the individual problems or both.  

Here are 2 library problems as examples:


Example seeds:  42 , 2681 , 


Example seeds: 3466 , 4391

Here is the error message:

DBD::MariaDB::st execute failed: Data too long for column 'frozen_hash' at row 1 at /opt/webwork/webwork2/lib/WeBWorK/DB/Schema/NewSQL/Std.pm line 881.

Any ideas? 

We are running 2.17

In reply to Tim Flowers

Re: Data too long for 'frozen_hash'

by Glenn Rice -

Disable the "still not right" achievement.  Either that or upgrade to webwork 2.18 (probably not an option for you at this point).

What is happening is that that achievement saves the last answer to the frozen hash column.  It is very easy for the last answer to contain to much data for the frozen hash column which prior to webwork 2.18 was a VARCHAR(1024) column.  Fir webwork 2.18 that is changed to a MEDIUMBLOB which can hold more than the last answer column which is of type TEXT.