Path: dp-news.maxwell.syr.edu!spool.maxwell.syr.edu!drn.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!news.tele.dk!news.tele.dk!small.news.tele.dk!uninett.no!ntnu.no!not-for-mail From: Jon Heggland Newsgroups: comp.databases.theory Subject: Re: How can one normalize this table? Date: Thu, 15 Dec 2005 10:37:11 +0100 Organization: IDI/NTNU Lines: 11 Message-ID: References: <1134611329.358990.12250@g47g2000cwa.googlegroups.com> <1134619558.077407.164330@f14g2000cwb.googlegroups.com> NNTP-Posting-Host: coleburn.idi.ntnu.no Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit X-Trace: orkan.itea.ntnu.no 1134639426 14474 129.241.111.99 (15 Dec 2005 09:37:06 GMT) X-Complaints-To: usenet@itea.ntnu.no NNTP-Posting-Date: Thu, 15 Dec 2005 09:37:06 +0000 (UTC) User-Agent: MicroPlanet-Gravity/2.60.2060 Xref: dp-news.maxwell.syr.edu comp.databases.theory:35160 In article <1134619558.077407.164330@f14g2000cwb.googlegroups.com>, dawnwolthuis@gmail.com says... > > If I understand the requirements correctly, there is no need for an > e-o-p base table. Position can be an attribute in the employee table. > Then you need only an employee-office relationship table. If you do it this way, you'll need a multi-table constraint to implement the FD { p, o } -> { e }. -- Jon