I am getting the following error in the Statistics panel, but the rest of the site is OK (full directory path masked for security).
Fatal error: Uncaught exception 'PDOException' with message 'SQLSTATE: Syntax error or access violation: 1104 The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET MAX_JOIN_SIZE=# if the SELECT is okay' in /XXXXX/XXXXX/phpgedview/includes/classes/class_pgv_db.php:835 Stack trace: #0 /XXXXX/XXXXX/phpgedview/includes/classes/class_pgv_db.php(835): PDOStatement->execute() #1 /XXXXX/XXXXX/phpgedview/includes/classes/class_pgv_db.php(850): PGV_DBStatement->__call(Array, Array) #2 /XXXXX/XXXXX/phpgedview/includes/classes/class_pgv_db.php(850): PGV_DBStatement->execute('execute', Array) #3/XXXXX/XXXXX/phpgedview/includes/classes/class_stats.php(3910): PGV_DBStatement->__call() #4/XXXXX/XXXXX/phpgedview/includes/classes/class_stats.php(3910): PGV_DBStatement->fetchAl in/XXXXX/XXXXX/phpgedview/includes/classes/class_pgv_db.php on line 835
This has only happened since my hosting provider moved my site to a new server. There is another thread on the forum with this same error, but none of the solutions apply here. I guess I need to enable something in my hosting cPanel, but what?
Pete
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You might take this opportunity to upgrade to the latest 4.3 svn release, if you hadn't already.
Unless your site is very large this is more likely some kind of twist-up in your data. Your best bet is to review recent changes, esp. changes just before you had trouble, in the changelog files.
It could be a corrupted db, maybe your host messed up moving the db. You could sub in a backup db from before the move. If you don't have many changes to re-enter this might be the easiest thing.
Let us know how you manage.
George
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am getting the following error in the Statistics panel, but the rest of the site is OK (full directory path masked for security).
Fatal error: Uncaught exception 'PDOException' with message 'SQLSTATE: Syntax error or access violation: 1104 The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET MAX_JOIN_SIZE=# if the SELECT is okay' in /XXXXX/XXXXX/phpgedview/includes/classes/class_pgv_db.php:835 Stack trace: #0 /XXXXX/XXXXX/phpgedview/includes/classes/class_pgv_db.php(835): PDOStatement->execute() #1 /XXXXX/XXXXX/phpgedview/includes/classes/class_pgv_db.php(850): PGV_DBStatement->__call(Array, Array) #2 /XXXXX/XXXXX/phpgedview/includes/classes/class_pgv_db.php(850): PGV_DBStatement->execute('execute', Array) #3/XXXXX/XXXXX/phpgedview/includes/classes/class_stats.php(3910): PGV_DBStatement->__call() #4/XXXXX/XXXXX/phpgedview/includes/classes/class_stats.php(3910): PGV_DBStatement->fetchAl in/XXXXX/XXXXX/phpgedview/includes/classes/class_pgv_db.php on line 835
This has only happened since my hosting provider moved my site to a new server. There is another thread on the forum with this same error, but none of the solutions apply here. I guess I need to enable something in my hosting cPanel, but what?
Pete
Hi Pete,
You might take this opportunity to upgrade to the latest 4.3 svn release, if you hadn't already.
Unless your site is very large this is more likely some kind of twist-up in your data. Your best bet is to review recent changes, esp. changes just before you had trouble, in the changelog files.
It could be a corrupted db, maybe your host messed up moving the db. You could sub in a backup db from before the move. If you don't have many changes to re-enter this might be the easiest thing.
Let us know how you manage.
George
Hi George,
Thanks for the reply.
I don't actually use the program to make changes online, I do all my editing in Family Historian and just upload the gedcom every so often.
I will try upgrading to 4.3 (I'm on 4.2.4), but if that doesn't work I'll just re-install clean and re-upload.
I was just making sure it wasn't just a case of enabling something to make it work to save me the hassle of re-installing.
Regards
Pete