Created attachment 67151 [details] A query longer than 65535; this will be truncated when saved. The field saved_sql.savedsql is type 'text', which is 65535 characters long. mysql> select table_name, column_name, data_type from information_schema.columns where column_name = 'savedsql'; +------------+-------------+-----------+ | table_name | column_name | data_type | +------------+-------------+-----------+ | saved_sql | savedsql | text | +------------+-------------+-----------+ The query editor in guided_reports.pl does not check the size of the report being saved, causing the report to be truncated if its more than 65535 characters long. I would suggest changing the data type of savedsql to LONGTEXT, then limiting the query length to something fairly large, but less than 4,294,967,295 characters, with a warning (to avoid denial of service by filling the hard drive).
Set to MAJOR because of data loss.
Can you give an example of a report (that would be wise to run) that is that long? I think major is too much here, we probably have a lot of fields if not all that cut off data if too long.
(In reply to Katrin Fischer from comment #2) > Can you give an example of a report (that would be wise to run) that is that > long? I think major is too much here, we probably have a lot of fields if > not all that cut off data if too long. Cait, See the attached file. It poses no danger when run because it's syntactically incorrect when imported.
It just killed my editor... kind of makes me worry if it's wise to recommend it for use with Koha :)
Not opposed to make the field bigger, was just wondering.