Re: Nested table or independent table

Prasath wrote:
> I want to implement a simple employee, department relationship.
> Only condition is that an employee can belong to multiple departments.
>
> Do I go for
>
> 1. a three table implementation ( employee, department and
> employee_department ) or
> 2. two table implementation( department and employee ) with employee
> table
> having a column which is a nested table of department ids ?
>
> Also please let us know the advantages/disadvantages of each
> implementation?
>
> Thanks,
> Prasath.

Sybrand is correct. 3 tables the intersecting entity most likely benefiting from being an IOT.

-- 
Daniel A. Morgan
http://www.psoug.org
damorgan_at_x.washington.edu
(replace x with u to respond)