• Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

Urgent Oracle SQL Question (INNER JOIN)

that would work fine too, technically no reason not to
Personally I'd say that good practice dictates otherwise though

Every person I have met who has used inner join has been a complete numpty. Those who use "=" are far better.

Maybe it is just me?
 
Every person I have met who has used inner join has been a complete numpty. Those who use "=" are far better.

Maybe it is just me?

No, it's not just you.

I've never written an inner join using the ANSI syntax.

Some clients will demand that you use it, but I would still only use the ANSI syntax for outer joins rather than an inner join.
 
Every person I have met who has used inner join has been a complete numpty. Those who use "=" are far better.

Maybe it is just me?

I used to use "=" then switched

Once you start writing more complex queries you'll understand the benefits
 
I used to use "=" then switched

Once you start writing more complex queries you'll understand the benefits

The only benefit I can see is that it helps separate the join condition from the data selection conditions.

I have enough trouble with

SELECT *
FROM emp
WHERE ename = 'KING'

to be honest - I'll leave such complex queries to others :)
 
I used to use "=" then switched

Once you start writing more complex queries you'll understand the benefits

What he said.

And if you're using a inner join and then want to switch to an outer join, you only have to change a couple of words.
 
Yeah in Oracle you can use this, but if you get into this habbit and then have to start using other databases, this syntax doesn't work.

I'll bear that in mind for when Oracle migrate the eBusiness Suite away from the Oracle database :)

After all, there is no other database but Oracle.
 

Advertisers

Back
Top