From: Dave Francis [mailto:[EMAIL PROTECTED]
SELECT r.eventID, d.title
FROM Events r,
EventDescription d
WHERE d.eventID = r.eventID
SELECT
r.eventID,
d.title
FROM
Events r
LEFT JOIN EventDescription d ON (r.eventID = d.eventID)
HTH,
Mike
You are using an INNER JOIN - you need to use a LEFT JOIN I believe.
SELECT r.eventID, d.title
FROM Events r
LEFT JOIN EventDescription d
ON WHERE d.eventID = r.eventID
-Original Message-
From: Dave Francis [mailto:[EMAIL PROTECTED]
Sent: 05 April 2005 15:18
To: CF-Talk
Subject:
]
Enviado el: Martes, 05 de Abril de 2005 10:17
Para: CF-Talk
Asunto: RE: SQL prob
You are using an INNER JOIN - you need to use a LEFT JOIN I believe.
SELECT r.eventID, d.title
FROM Events r
LEFT JOIN EventDescription d
ON WHERE d.eventID = r.eventID
-Original Message-
From: Dave Francis
This is the OLD way to perform a join - it should be avoided.
-Original Message-
From: David Manriquez [mailto:[EMAIL PROTECTED]
Sent: 05 April 2005 15:48
To: CF-Talk
Subject: RE: SQL prob
Another way
SELECT r.eventID, d.title
FROM Events r,EventDescription d
WHERE d.eventID
, but how much does it really matter?
Matt Osbun
Web Developer
Health Systems, International
-Original Message-
From: Robertson-Ravo, Neil (RX)
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 05, 2005 9:42 AM
To: CF-Talk
Subject: RE: SQL prob
This is the OLD way to perform a join - it should
Why - because it is deprecated.
-Original Message-
From: Matt Osbun [mailto:[EMAIL PROTECTED]
Sent: 05 April 2005 16:18
To: CF-Talk
Subject: RE: SQL prob
Why? Not a challenge, but a question. Using *= or (+) always seemed,
at least to me, quicker, easier, and easier to read
I should add - deprecated in SQL Server...
-Original Message-
From: Robertson-Ravo, Neil (RX)
[mailto:[EMAIL PROTECTED]
Sent: 05 April 2005 16:17
To: CF-Talk
Subject: RE: SQL prob
Why - because it is deprecated.
-Original Message-
From: Matt Osbun [mailto:[EMAIL PROTECTED
I should add - deprecated in SQL Server.
-Original Message-
From: Robertson-Ravo, Neil (RX)
[mailto:[EMAIL PROTECTED]
Sent: 05 April 2005 16:17
To: CF-Talk
Subject: RE: SQL prob
Why - because it is deprecated.
-Original Message-
From: Matt Osbun [mailto:[EMAIL PROTECTED
To: CF-Talk
Subject: RE: SQL prob
This is the OLD way to perform a join - it should be avoided.
-Original Message-
From: David Manriquez [mailto:[EMAIL PROTECTED]
Sent: 05 April 2005 15:48
To: CF-Talk
Subject: RE: SQL prob
Another way
SELECT r.eventID, d.title
FROM Events r
-Mensaje original-
De: Matt Osbun [mailto:[EMAIL PROTECTED]
Enviado el: Martes, 05 de Abril de 2005 11:18
Para: CF-Talk
Asunto: RE: SQL prob
Why? Not a challenge, but a question. Using *= or (+) always seemed,
at least to me, quicker, easier, and easier to read afterward.
Now, I admit
From: David Manriquez [mailto:[EMAIL PROTECTED]
I'm still using it cause a Microsoft Certified SQL
professional show me the tracing and performance of
LEFT/RIGHT/OUTHER/INNER JOIN and *=/=/=*/*=* and the last
one is better and faster.
A lot more goes into it than that... Indexes, keys,
Indeed.
Plus I was always under the impression that all other things being equal,
explicity stating your joins would be faster. Seems to make sense logically
too.
From: David Manriquez [mailto:[EMAIL PROTECTED]
I'm still using it cause a Microsoft Certified SQL
professional show me the
Why? Not a challenge, but a question. Using *= or (+)
always seemed, at least to me, quicker, easier, and easier to
read afterward.
Now, I admit that I mostly got into the habit because, until
fairly recently, I was stuck on an Oracle platform that was
too old to use INNER JOIN/LEFT
I don't think one test can be seen as proof of either way being better
or faster - there's a lot more that goes into DB performance than JOIN
vs. =. Indexes, constraints, what mood your OS is in, etc.
True story: a company I worked for had to fire a Microsoft Certified
Professional (actually, an
PROTECTED]
Enviado el: Martes, 05 de Abril de 2005 11:18
Para: CF-Talk
Asunto: RE: SQL prob
Why? Not a challenge, but a question. Using *= or (+) always seemed,
at least to me, quicker, easier, and easier to read afterward.
Now, I admit that I mostly got into the habit because, until
Also, instead of running the queries (not a very valid test unless you
do each way many times under similar conditions), try looking at
estimated execution plans, etc. You'll probably notice that in a lot
of cases the optimizer (in SQL server, at least) will create the same
execution plan for
had it up to here with people in general this morning. If it
is, maybe I should just hit the power button and take the rest of the
day.
--Ferg
-Original Message-
From: Dave Watts [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 05, 2005 11:18 AM
To: CF-Talk
Subject: RE: SQL prob
One
From: Ken Ferguson [mailto:[EMAIL PROTECTED]
Does this bother anyone else, or is it just me? It could
easily be just me; I've had it up to here with people in
general this morning. If it is, maybe I should just hit the
power button and take the rest of the day.
Click that button...
Once again, someone pops in with this reason for doing
something. It troubles me that this manner of thinking is so
prevalent, as it most certainly means it's come about from
actual experiences dealing with people.
I don't feel that this sort of because-you-might-not-be-smart-enough
all for
something that will keep a minor mistake into becoming a larger problem.
Anyway, thanks for the responses, all.
Matt
-Original Message-
From: Ken Ferguson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 05, 2005 11:33 AM
To: CF-Talk
Subject: RE: SQL prob
Once again, someone
For two, specifically speaking, I can point to a couple
instances where I've annoyed the heck out of a DBA by
forgetting to join a couple of million+ record tables before
running the query.
I can think of a million ways a dba's annoyed me :) sorry, I'll get
back to work
--
dc
I don't feel that this sort of because-you-might-not-be-smart-enough
type of argument is a good reason to do anything one way or another.
I don't think that Dave was saying people shouldn't use *= because
they might not be smart enough. I think that good developers like
Dave recognize
Matt Osbun wrote:
Why? Not a challenge, but a question. Using *= or (+) always seemed,
at least to me, quicker, easier, and easier to read afterward.
Now, I admit that I mostly got into the habit because, until fairly
recently, I was stuck on an Oracle platform that was too old to use
since. (And they read better too.)
-Original Message-
From: Matt Osbun [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 05, 2005 11:18 AM
To: CF-Talk
Subject: RE: SQL prob
Why? Not a challenge, but a question. Using *= or (+) always seemed,
at least to me, quicker, easier, and easier
I would ask him to give it back - this syntax is deprecated and could well
be removed at any stage from SQL Server .
David Manriquez [SMTP:[EMAIL PROTECTED]
-Original Message-
From: David Manriquez
To: CF-Talk
Sent: 05/04/2005 16:28
Subject: RE: SQL prob
I'm still using it cause
There's a good reason to use the new style of joins: because they are more
powerful.
Here is an example of a query that, to my knowledge, can't be done with *=
syntax:
select *
from t1 left outer join t2
on (t1.id = t2.id and t1.rating t2.max_rating)
This is
26 matches
Mail list logo
