The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#11
|
|||
|
|||
Quote:
Let us know what happens. By the way, I don't see any problem with the query you posted above but I wanted to clarify what I mentioned before - I know that when a query starts with "UPDATE bounce LEFT JOIN user..." for instance, it sounds like you're updating the bounce table. But you can think of the "bounce LEFT JOIN user USING (email)" part as a virtual table containing fields from both, and if you then SET fields from the user table you'll be updating the user table and not bounce, even though bounce was mentioned first. And as I mentioned, the difference is that in the "bounce left join user" virtual table will contain one row for each row from bounce, whereas "user left join bounce" will have one row for each row in user (with bounce.email NULL where there was no match). |
#12
|
||||
|
||||
Yes... you are correct on the query. Works the same either way.
Thanks for the lesson. Single table queries are easy for me, but the whole join thing makes it more complex, and I'm not writing queries every day. |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|