1. Alezo
  2. RO CSVI
  3. Tuesday, 07 October 2014
  4.  Subscribe via email
Hello!

We would really appreciate the help. We have a Joomla 3.3.6 install with Virtuemart 2.9.9e, CSVI Pro version 5.19. Any export/import operation ends with an error message as soon as "Process" button is pressed:
1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'OPTION SQL_BIG_SELECTS=1' at line 1 SQL=SET OPTION SQL_BIG_SELECTS=1


We also tried installing CSVI Pro 5.19 on another server running Joomla 3.3.6 (without Virtemart) on another hosting account (but SAME hosting), and the error message was exactly the same as above. So maybe the problem is with some settings that our hosting provider is using?
There's also no debug log created.
Accepted Answer Pending Moderation
Okay, thank you very much RolandD! :)
  1. more than a month ago
  2. RO CSVI
  3. # 1
Accepted Answer Pending Moderation
Hello,

Thank you for the valuable feedback, it is greatly appreciated.

Can you implement this in the future release?
Absolutely, I have already changed it for the next release of CSVI.

This is only applicable to the export as the import doesn't set the SQL_BIG_SELECTS option.
Kind regards,

RolandD

=========================
If you use our extensions, please post a rating and a review at the Joomla! Extension Directory
  1. more than a month ago
  2. RO CSVI
  3. # 2
Accepted Answer Pending Moderation
We've contacted our hosting provider and here's what we found.

They have updated MySQL server to version 5.6, where syntax of some commands has changed. So now instead of:
SET OPTION SQL_BIG_SELECTS=1


Another syntax should be used:
SET SQL_BIG_SELECTS=1


Modifications should be made to these files (for export, haven't tried import yet):

./administrator/components/com_csvi/models/exportfile.php:92:                   $db->setQuery("SET SQL_BIG_SELECTS=1");
./components/com_csvi/models/export.php:72: $db->setQuery("SET SQL_BIG_SELECTS=1");


I hope this will help people with similar problems. Can you implement this in the future release?
  1. more than a month ago
  2. RO CSVI
  3. # 3
Accepted Answer Pending Moderation
Hello,

There is indeed no debug log created because the process stops even before it starts. Check with your hosting, they probably have disabled executing this query
SET OPTION SQL_BIG_SELECTS=1
which is very rare to disable. This code has been in CSVI for many years and if I remember correctly, this is the first time it is a problem.
Kind regards,

RolandD

=========================
If you use our extensions, please post a rating and a review at the Joomla! Extension Directory
  1. more than a month ago
  2. RO CSVI
  3. # 4
  • Page :
  • 1


There are no replies made for this post yet.
Be one of the first to reply to this post!