OJS OCS OMP OHS

You are viewing the PKP Support Forum | PKP Home Wiki


DB Error: The SELECT would examine (...)

Are you responsible for making OJS work -- installing, upgrading, migrating or troubleshooting? Do you think you've found a bug? Post in this forum.

Moderators: jmacgreg, michael, jheckman, barbarah, btbell, bdgregg, asmecher

Forum rules
What to do if you have a technical problem with OJS:

1. Search the forum. You can do this from the Advanced Search Page or from our Google Custom Search, which will search the entire PKP site. If you are encountering an error, we especially recommend searching the forum for said error.

2. Check the FAQ to see if your question or error has already been resolved.

3. Post a question, but please, only after trying the above two solutions. If it's a workflow or usability question you should probably post to the OJS Editorial Support and Discussion subforum; if you have a development question, try the OJS Development subforum.

Re: DB Error: The SELECT would examine (...)

Postby CarlaTC » Sun Mar 14, 2010 4:29 pm

Hello

I'm reading all the solutions written here, but I'm using the OJS 2.3.1.2 version and, although I have tried the solutions mentioned in this topic, I still can display the list of currently submissions from the "editor" section.

The error message is the same:

DB Error: The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET SQL_MAX_JOIN_SIZE=# if the SELECT is okay

The strange thing is that this occurred after uploaded and published over 100 paper, because of a platform migration.

Is there a way to fix this error in this version of OJS?

Thanks

Carla Tossi
Layour Editor
Economic Analysis Review (RAE-EAR)
CarlaTC
 
Posts: 1
Joined: Sun Mar 14, 2010 4:10 pm

Re: DB Error: The SELECT would examine (...)

Postby erreal » Mon Nov 05, 2012 2:51 am

Hello everyone,

I have the same problem: "DB Error: 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".

I put de debug ON and this is what I gett:

(mysql): SELECT * FROM sessions WHERE session_id = '18b39ff35d9f2a2214719f62ad209a27'
(mysql): SELECT * FROM users WHERE user_id = 1
(mysql): SELECT * FROM user_settings WHERE user_id = '1'
(mysql): select version()
(mysql): SELECT * FROM journals WHERE path = 'ENE'
(mysql): SELECT * FROM site
(mysql): SELECT v.* FROM versions v LEFT JOIN plugin_settings ps ON lower(v.product_class_name) = ps.plugin_name AND ps.setting_name = 'enabled' AND ((journal_id = '2') OR v.sitewide = 1) WHERE v.current = 1 AND (ps.setting_value = '1' OR v.lazy_load <> 1)
(mysql): SELECT setting_name, setting_value, setting_type FROM plugin_settings WHERE plugin_name = 'timedviewplugin' AND journal_id = '2'
(mysql): SELECT * FROM roles WHERE user_id = 1 ORDER BY journal_id
(mysql): SELECT * FROM notifications WHERE user_id = 1 AND level = 1 ORDER BY date_created DESC
(mysql): SELECT i.* FROM issues i WHERE journal_id = '2' AND current = 1
(mysql): SELECT * FROM issue_settings WHERE issue_id = '2'
(mysql): SELECT * FROM roles WHERE user_id = 1 AND journal_id = 2 ORDER BY journal_id
(mysql): SELECT iss.subscription_id FROM institutional_subscriptions iss, subscriptions s, subscription_types st WHERE POSITION(UPPER(LPAD(iss.domain, LENGTH(iss.domain)+1, '.')) IN UPPER(LPAD('84.79.229.209', LENGTH('84.79.229.209')+1, '.'))) != 0 AND iss.domain != '' AND iss.subscription_id = s.subscription_id AND s.journal_id = '2' AND s.status = 1 AND s.type_id = st.type_id AND st.institutional = 1 AND ((st.non_expiring = 1) OR (st.non_expiring = 0 AND ('2012-11-05 10:46:55' >= s.date_start AND '2012-11-05 10:46:55' <= s.date_end))) AND (st.format = 1 OR st.format = 17)
(mysql): SELECT isip.subscription_id FROM institutional_subscription_ip isip, subscriptions s, subscription_types st WHERE ((isip.ip_end IS NOT NULL AND '1414522321' >= isip.ip_start AND '1414522321' <= isip.ip_end AND isip.subscription_id = s.subscription_id AND s.journal_id = '2' AND s.status = 1 AND s.type_id = st.type_id AND st.institutional = 1 AND ((st.non_expiring = 1) OR (st.non_expiring = 0 AND ('2012-11-05 10:46:55' >= s.date_start AND '2012-11-05 10:46:55' <= s.date_end))) AND (st.format = 1 OR st.format = 17)) OR (isip.ip_end IS NULL AND '1414522321' = isip.ip_start AND isip.subscription_id = s.subscription_id AND s.journal_id = '2' AND s.status = 1 AND s.type_id = st.type_id AND st.institutional = 1 AND ((st.non_expiring = 1) OR (st.non_expiring = 0 AND ('2012-11-05 10:46:55' >= s.date_start AND '2012-11-05 10:46:55' <= s.date_end))) AND (st.format = 1 OR st.format = 17)))
(mysql): SELECT i.* FROM issues i WHERE journal_id = '2' AND current = 1
(mysql): SELECT * FROM issue_settings WHERE issue_id = '2'
(mysql): SELECT count(*) FROM notifications WHERE user_id = 1 AND date_read IS NULL AND level = 2 AND context_id = 2


I tried to follow the instructions here, but i can't find the DBConnection.inc.php, there is no db folder in classes. I tried with the search but I can't find anything. Would you help me?


Thanks (and sorry for my english).
erreal
 
Posts: 3
Joined: Wed Oct 31, 2012 4:00 am

Re: DB Error: The SELECT would examine (...)

Postby springday » Mon Nov 05, 2012 9:24 am

Hi erreal,

the "db" folder is not in /classes, but in /lib/pkp/classes. You'll find the DBConnection.inc.php there.

(I've been confused a lot by this and wondered why there are two separate /classes folders. It makes finding source code files more difficult. However, I believe the PKP team can manage the code base more easily this way: /classes is the individual source code of OJS, /lib/pkp/classes is the source code that all PKP applications - OJS, OCS, OMP - share with eath other)

Best regards,
Kai Weber
springday
 
Posts: 98
Joined: Wed Jul 25, 2012 2:56 pm
Location: Munich, Germany

Previous

Return to OJS Technical Support

Who is online

Users browsing this forum: No registered users and 3 guests