details
Type php
Date Friday, 30 June 2006 - 5:52pm
User MrMister
Location http://domain.com/user/stevi10623
Referrer http://domain.com/user/candela
Message 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 '0,1,2,6,9,14,15,22,23,26,32,33,36,38,49,53,57,59,60,62,64,65,66,72,74,75,80,81,8' at line 1 query: SELECT * FROM user WHERE uid IN 0,1,2,6,9,14,15,22,23,26,32,33,36,38,49,53,57,59,60,62,64,65,66,72,74,75,80,81,83,86,88,89,94,98,100,104,111,112,117,121,123,124,126,128,132,134,137,140,154,156,159,160,164,166,167,176,178,181 AND uid != 0 in /path/domain.com/httpdocs/includes/database.mysql.inc on line 120.
Severity error
Hostname ip

Comments

Fusion_Sushi’s picture

Fusion_Sushi commented

details
Type php
Date Friday, 30 June 2006 - 5:52pm
User MrMister
Location http://domain.com/user/stevi10623
Referrer http://domain.com/user/candela
Message Missing argument 2 for variable_get() in /path/domain.com/httpdocs/includes/bootstrap.inc on line 266.
Severity error
Hostname ip

Fusion_Sushi’s picture

Fusion_Sushi commented

details
Type php
Date Friday, 30 June 2006 - 5:52pm
User MrMister
Location http://domain.com/user/stevi10623
Referrer http://domain.com/user/candela
Message 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 '0,6,9,26,72,89,90,94 AND uid != 0' at line 1 query: SELECT * FROM user WHERE uid IN 0,6,9,26,72,89,90,94 AND uid != 0 in /path/domain.com/httpdocs/includes/database.mysql.inc on line 120.
Severity error
Hostname ip

heine’s picture

heine commented

I commend you for the effort, but these kind of bug reports are useless. You really need to provide more information. Can you reproduce on a core 4.7.2 install? What modules / php blocks are you using? Because you file against profile; what profile fields are defined?

Fusion_Sushi’s picture

Fusion_Sushi commented

so.. the question is... why are error reports usless?? that would be something that should be looked at... why does Drupal report and track usless information? is'nt there something that could be done to provide more useful information? or to discard this information all together and provide more "active" error reports inline?

beginner’s picture

beginner commented

reports are not useless.
For us to find a fix, we need to find out what is causing the problem.
And, in order to find out what is causing the problem, we need to be able to reproduce the problem first.
That's where you can help us a lot: tell us very precisely how we can reproduce the problem on a clean install of Drupal.

please, see:
http://drupal.org/node/317
http://drupal.org/node/19279

Fusion_Sushi’s picture

Fusion_Sushi commented

I understand and I do that if you have seen some of my reports, they are detailed and usually contain suggestions, questions and process information... as you can see ablove(maybe not) the user was "MrMister" not me... so, when you ask me, what other info I can provide.. not much really, or perhaps I don't know how to give you more... it does not seem to happen "all" the time, so I doubt that a clean install would show anything, consistantly as my install does not do this consistantly.

I don't really know what happened, I was not there but it appears that there was a bit of a "car accident" happening.

Crell’s picture

Crell commented

It looks like you're just pasting a watchdog error. That on its own is not very useful.

What exact version of Drupal are you running? (4.7.0, 4.7.1, 4.7.2?)

What modules do you have installed and enabled? Are they all the 4.7-tagged version?

Can you reliably reproduce the error? Eg, if you always go to a specific page, does an entry then show up in watchdog? Try turning on error display in admin/settings so that you can see errors right on the page. That makes it easier to see what page is causing an error.

Have you talked to MrMister to see what it is he's up to? :-) Does it only happen for that one user, for for multiple users?

It looks like at least some of them are mis-written SQL statements. But there's hundreds of thousands of lines of code in Drupal and Contribs. If you can't narrow it down to what module or modules may be causing it, there's no way that anyone can find the erring lines.

drupal777’s picture

drupal777 commented

php version?

mysql version?

It looks like you have some sort of listing that is being made. Do you have a custom profile list? Do you have a module that does a custom list? Can you see any trait that is consistent amongst the user id's mentioned in either the first or second string of uid's?

Prometheus6’s picture

Prometheus6 commented

Guys...when you get all that...

SELECT * FROM user WHERE uid IN (0,1,2,6,9,14,15,22,23,26,32,33,36,38,49,53,57,59,60,62,64,65,66,72,74,75,80,81,
83,86,88,89,94,98,100,104,111,112,117,121,123,124,126,128,132,134,137,140,154,
156,159,160,164,166,167,176,178,181) 
AND uid != 0

The problem with the SQL statement is the list of uid values needs to be enclosed in parentheses.

asimmonds’s picture

asimmonds commented

Shouldn't user be users in the SQL statement?

If so, I did a grep of all the contrib modules and came up with the profile_visit.module which has:

$result = db_query('SELECT * FROM {user} WHERE uid IN %s AND uid != 0', implode(',', array_keys($visitors)));

c4.Pilgrim: Are you using this profile_visit.module?

Fusion_Sushi’s picture

Fusion_Sushi commented

thanks for the tip, on how to possibly find the error.. yes, I'll disable it and test..

drupal777’s picture

drupal777 commented

I think a better course of action would be to add the parenthesis.

heine’s picture

heine commented
Project: Drupal core » Profile visit
Version: 4.7.2 » master
Component: profile.module » Code

Reassigned to profile visit.

From an IRC conversation:

Replace %s with sufficient %d's eg. $placeholders = implode(', ', array_fill(0, count($visitors), '%d')); then use ($placeholders)

Crell’s picture

Crell commented

Is this still an issue?

Crell’s picture

Crell commented
Status: Active » Closed (won't fix)

No response from submitter.