Bit of dejavu here Justin?? :)

> select * from people, jobs
> where people.id = jobs.peopleid and people.id = xxxx and jobs.id = yyyy

Don't mind that at all.


> select * from people p, jobs j
> where p.id = j.peopleid and p.id = xxx and j.id = yyy

That what I really don't like. Especially when the names get
increasingly abstract (like Joe Celko's style).

> Possibly it's a personal thing.

It really is - whenever I start getting muddled in something, if its
not 100% clear when I look at it, I start by making it as verbose and
clear as possible. You've seen me frantically tabbing and spacing
everything so its super neat, this is not because I'm a neat person,
its to help me get a mental picture of what is going on.

To me SQL is one of those things that I don't find immediatly
intuitive, it often takes me a while to get my head clear on it.
Aliasing tables just makes things harder for me to understand, its one
more thing to remember.

I can see how in Barry's example it may help him.

-- 
Mark Stanton 
Gruden Pty Ltd 
http://www.gruden.com

---
You are currently subscribed to cfaussie as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/

Reply via email to