Log in

View Full Version : What is The Problem(s)? :(


Cagonni
09-07-2006, 01:52 AM
Database error in vBulletin 3.6.0:
Invalid SQL:
SELECT post.*
FROM post AS post
LEFT JOIN deletionlog AS deletionlog ON(deletionlog.primaryid = post.postid AND type = 'post')
WHERE threadid = 8
AND dateline > 1155014895
AND visible = 1 AND deletionlog.primaryid IS NULL
AND postid <> 10
ORDER BY dateline DESC
LIMIT 1;
MySQL Error : Column: 'dateline' in where clause is ambiguous
Error Number : 1052
Date : Wednesday, August 9th 2006 @ 12:28:15 AM
Script : --
Referrer : --
IP Address : xxx.xxx.xxx.xxx
Username : name
Classname : vb_database


im boring of this db error :(
i searched the forum and all the sites about vbulletin.The problem is "Prevent Double Post" they said.I disabled the plugin but the error is continuing..I think My other plugins and products dont give that error.Do Prevent Double Post Plugins tables remained in my database?

Another Question

I cant make two post consecutively.Its not a time problem.After 2 or 3 days from my first posts if there is any post after mine i cant post any message :(

The Error above quick reply part is

The following errors occurred when this message was submitted

Okay

But there isnt any error it shows :(

when I click the "Okay" all it does is go back to the normal quick reply box.

Do You Have Any Ideas With These Problems?

Adrian Schneider
09-07-2006, 01:57 AM
The post and deletelog tables both have a 'dateline' column, so you need to specify which one. SELECT post.*
FROM post AS post
LEFT JOIN deletionlog AS deletionlog ON(deletionlog.primaryid = post.postid AND type = 'post')
WHERE threadid = 8
AND post.dateline > 1155014895
AND visible = 1 AND deletionlog.primaryid IS NULL
AND postid <> 10
ORDER BY post.dateline DESC
LIMIT 1;

I'm not sure about the other problem.

Cagonni
09-07-2006, 02:23 AM
Database error in vBulletin 3.6.0:

Invalid SQL:

SELECT post.*
FROM uzakdurpost AS post
LEFT JOIN uzakdurdeletionlog AS deletionlog ON(deletionlog.primaryid = post.postid AND type = 'post')
WHERE threadid = 5503
AND dateline > 1157509558
AND visible = 1 AND deletionlog.primaryid IS NULL
ORDER BY dateline DESC
LIMIT 1;

MySQL Error : Column 'dateline' in where clause is ambiguous
Error Number : 1052
Date : Thursday, September 7th 2006 @ 05:25:58 AM
Script : http://www.hitportal.net/newreply.php
Referrer : http://www.hitportal.net/showthread.php?t=5503
IP Address : xx.xx.xx.xxx
Username : Cagonni
Classname : vb_database


This is the mail i read.Your sql code includes

WHERE threadid = 8
AND post.dateline > 1155014895

should i do this for all threadid an post datelines?For example

WHERE threadid = 5503
AND dateline > 1157509558

because this error valid for all my forum categories.

Adrian Schneider
09-07-2006, 02:26 AM
Specifying every table for those fields isn't a bad habbit - but you only have to do the ones that are in both tables (such as dateline). I don't understand your question... I'm not sure what you are trying to do.

Cagonni
09-07-2006, 02:32 AM
i took approximately 2000 mail like this.I asked

Should i specify every table for those fields? 2000 is not a small number :confused:

default vbulletin database tables have those columns but there is no problem.I dont understand :(

Adrian Schneider
09-07-2006, 02:43 AM
vBulletin includes the table when specifying the field, which you are not.

If two tables both have the same field name, and you don't tell it which table the field belongs to, it will give you an error like the above.

You can specify the table only for problematic queries like that one. To be safe, you should do it for all of your queries using more than one table.