The cluster (3.8 & 3.9) splits large file content over several rows in the table ezdbfile_data. It's therefor important that the data is fetch in the correct order, but the select statement is missing an "ORDER BY id".

This could lead to fatal error under certant circumstances where MySQL reverses the order of the rows in some special cases. One example could be the wildcard cache where PHP code is fetched and executed.

(Only an issue with the cluster in 3.8/3.9 )