I must say, I'm really appreciative with the responses from this list.
Thanks to all!
-Original Message-
From: elein [mailto:[EMAIL PROTECTED]
Sent: January 31, 2004 12:10 PM
To: Anony Mous
Cc: [EMAIL PROTECTED]
Subject: Re: [GENERAL] Two joins on same foreign key
PostgreSQL Ge
PostgreSQL General Bits Issue #56 has an article on Join Basics
which also has an example of multiple table joins.
http://cookie.varlena.com/varlena/GeneralBits/56.php
--elein
[EMAIL PROTECTED]
On Fri, Jan 30, 2004 at 03:03:35PM -0700, Anony Mous wrote:
> Hi,
>
>
>
> I??m fairly new to this
On Jan 31, 2004, at 3:35 PM, Anony Mous wrote:
Actually, given that there may not always be a backup_employee field
(can be
null) I think I'm forced to use an outer join to return all team leader
records regardless if a matching backup_employee record exists.
yup. Actually, I hadn't seen the othe
m: Michael Glaesemann [mailto:[EMAIL PROTECTED]
Sent: January 30, 2004 11:21 PM
To: Anony Mous
Cc: [EMAIL PROTECTED]
Subject: Re: [GENERAL] Two joins on same foreign key
On Jan 31, 2004, at 7:03 AM, Anony Mous wrote:
> Table #1
> employee_id (pk)
> employee_name
>
> Table #2
On Jan 31, 2004, at 7:03 AM, Anony Mous wrote:
Table #1
employee_id (pk)
employee_name
Table #2
teamleader_employee_id
backup_employee_id
both fields in table 2 need to do a lookup in table 1 to get the name
of the actual employee. Do I need to use nested queries to accomplish
this? Any help
