Pete Brown (12/13/2007)
I wonder what benefit questions like these have to the community at large.I thought the question of the day was there to inform not just to make the author feel smug!!!
The point is that you have to look at what the code does, especially if the syntax looks new to you.
All the following work, and are all equivalent, even though a few get highlighted strangely
SELECT * FROM dbo.Customers
PARTIAL JOIN dbo.Employees ON CustomerID = EmployeeID
SELECT * FROM dbo.Customers
CONNECTED JOIN dbo.Employees ON CustomerID = EmployeeID
SELECT * FROM dbo.Customers
DISCONNECTED JOIN dbo.Employees ON CustomerID = EmployeeID
SELECT * FROM dbo.Customers
UPPER JOIN dbo.Employees ON CustomerID = EmployeeID
SELECT * FROM dbo.Customers
LOWER JOIN dbo.Employees ON CustomerID = EmployeeID
SELECT * FROM dbo.Customers
INVERTED JOIN dbo.Employees ON CustomerID = EmployeeID
SELECT * FROM dbo.Customers
EQUAL JOIN dbo.Employees ON CustomerID = EmployeeID
SELECT * FROM dbo.Customers
UNEQUAL JOIN dbo.Employees ON CustomerID = EmployeeID
SELECT * FROM dbo.Customers
TRIANGULAR JOIN dbo.Employees ON CustomerID = EmployeeID
SELECT * FROM dbo.Customers
INVISIBLE JOIN dbo.Employees ON CustomerID = EmployeeID
And, of course, all these work, but one returns a different result to the others 🙂
SELECT * FROM dbo.Customers
RIHGT JOIN dbo.Employees ON CustomerID = EmployeeID
SELECT * FROM dbo.Customers
RITE JOIN dbo.Employees ON CustomerID = EmployeeID
SELECT * FROM dbo.Customers
WRITE JOIN dbo.Employees ON CustomerID = EmployeeID
SELECT * FROM dbo.Customers
RIGHT JOIN dbo.Employees ON CustomerID = EmployeeID
Derek