asked on August 30, 2017
Hi, I'm currently testing flexmonster with the free trial version.
I'm loading data from a mySql database into my table using php and the flexmonster-compressor.
For a limited query up to 4000 rows everything is working smoothly.
However, if I try to query my whole data or even only with limit 5000 the data is not put in the table anymore. Instead the php file is listing the compressed result of the query (or a part of it) with a lot more linebreaks (one between every row) than before.
Best Jonathan
⋅ August 31, 2017
Hi Jonathan!
Thank you for reporting the problem.
I don't have a quick answer for you because we need some time to check our compressor tool.
But I can recommend filtering out part of the data set in advance. Probably it will be a workaround for you while we are investigating the issue.
I will keep you updated about the progress.
Thanks,
Roman
⋅ August 31, 2017
Hi Roman,
Thank you for the fast response. I fear filtering beforehand is not a solution in my case. Meanwhile I'm going to try using a csv file created from the database and using it without compression.
Thanks,
Jonathan
⋅ September 6, 2017
Hello Jonathan,
Thank you for waiting. We have performed the necessary tests on the latest PHP compressor with 5000 rows. Everything works correctly, the compressor successfully compresses 5K rows and the component shows all the data. Please find the latest PHP compressor here -https://s3.amazonaws.com/flexmonster/lotum/FLEXMONSTER-2017-LOTUM-SEP6.ZIP.
Let us know if it works for you.
Best regards,
Dmytro.
⋅ September 6, 2017
Hi Dmytro,
Thank you for your effort. It's still not working for me. Probably I am doing something wrong.
However, as my workaround to create my own csv file from the data is working fine, I am happy to use Flexmonster this way.
For now I have no time to search for the cause of the former's problem.
Maybe later on.
Nevertheless, thanks a lot,
Jonathan
⋅ September 6, 2017
Hello Jonathan,
Thank you for sharing your feedback with us. We are glad you have found a workaround. As for reproducing this issue on our side, if you shared your sample data, it would help us. We would be grateful for your feedback.
Regards,
Tanya
