I enable the taxonomy_term,
and made some changes in that and i saved , Then it through the ERROR
user warning: 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 'LIMIT 0, 1' at line 1 query: SELECT count(node.nid) AS num_nodes FROM node node WHERE (node.status = '1') GROUP BY LIMIT 0, 1 in C:\wamp\www\bharani\includes\database.mysql.inc on line 172.
After i view that taxonomy related content it through the error like
* user warning: 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 ')) FROM node node WHERE (node.status = '1')' at line 1 query: SELECT count(DISTINCT()) FROM node node WHERE (node.status = '1') in C:\wamp\www\bharani\includes\database.mysql.inc on line 172.
* user warning: 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 'LIMIT 0, 10' at line 1 query: SELECT count(node.nid) AS num_nodes FROM node node WHERE (node.status = '1') GROUP BY LIMIT 0, 10 in C:\wamp\www\bharani\includes\database.mysql.inc on line 172.
* user warning: 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 'LIMIT 0, 1' at line 1 query: SELECT count(node.nid) AS num_nodes FROM node node WHERE (node.status = '1') GROUP BY LIMIT 0, 1 in C:\wamp\www\bharani\includes\database.mysql.inc on line 172.
Comments
Comment #1
thelocaltourist commentedI have the same problem and I need to go live in two days! HELP!
Comment #2
bharanikumariyerphp commentedmay i know
for what purpose u want ...texonomy_term
Comment #3
iansears commentedI am ALSO having the same error today.
Mine started when I deleted a custom content type.
Anyone know what could be throwing this error?
Thanks in advance for any comments towards solutions.
Ian
Comment #4
merlinofchaos commentedOk, this bug was originally against Views 1 for D5 and was recategorized to Views 2, with NO INFORMATION. Please don't do that.
Comment #5
thelocaltourist commentedHi Earl - Sorry about that. I didn't realize I'd changed it. BTW - thanks for all your work!
Comment #6
Rodeo.be commentedi still get the error....
Comment #7
artis commentedI'm getting this error too. I noticed that "FROM node node" is in the SQL statement. There is no table like that...it should just be "FROM node"... I'm pretty sure. Problem is I can't figure out what module is causing the problem. Views?
Comment #8
merlinofchaos commentedFYI there is not anywhere near enough information in here for me to debug this. If all you have to add is "I get this error too" then please go read up on how to actually submit issue reports. I need completeness.
Comment #9
kulfi commentedGetting the following error with Views 1, exposed filters, when a filter operator 'contains' is used:
An export of my view:
Comment #10
iansears commentedOk,
This may not be of help at all, but it corrected my problem.
In my case, I received this error immediately after deleting a Content Type that the View was supposed to be displaying. So, in my case, I simply deleted the View. Of course, all was good there. It may be that if I had told the View to work on a different Content Type rather than the CT I had deleted, that it also would have corrected my issue.
I sincerely hope this helps someone. In my case this issue is closed though.
iansears
Comment #11
sunComment #12
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.