**This project will be closed in early 2023!** IMS QTI 2.1 assessment delivery engine and Java development library (JQTI+). Supports the MathAssess extensions. Replacement for QTIEngine/JQTI and MathAssessEngine/JQTI. Note that this project has now ended and no further work is currently planned.
The QTIWorks database schema does not currently bootstrap on MySQL as some of the columns used to form indexes violate the 767 byte limitation on InnoDB indexes.
I had not previously noticed this as these columns were added after I last tested running QTIWorks on MySQL while filling in LTI support. (It seems like nobody else has noticed either!?)
I propose making these columns a bit smaller so as to fit MySQL's constraints. Unfortunately these columns all store LTI / OAuth information, and the specifications don't define any limits on how big this might be, so I had had previously been very generous with their storage. Restricting them will increase the potential for constraint violations, but the data I've seen so far suggests this shouldn't be a problem.
The QTIWorks database schema does not currently bootstrap on MySQL as some of the columns used to form indexes violate the 767 byte limitation on InnoDB indexes.
I had not previously noticed this as these columns were added after I last tested running QTIWorks on MySQL while filling in LTI support. (It seems like nobody else has noticed either!?)
I propose making these columns a bit smaller so as to fit MySQL's constraints. Unfortunately these columns all store LTI / OAuth information, and the specifications don't define any limits on how big this might be, so I had had previously been very generous with their storage. Restricting them will increase the potential for constraint violations, but the data I've seen so far suggests this shouldn't be a problem.