Home -> Usenet -> comp.databases.theory -> does a table always need a PK?

does a table always need a PK?

From: etp <etp_at_spamoutgun.com>
Date: Fri, 22 Aug 2003 14:08:28 -0600
Message-ID: <dqtckv44op5bo3j0q9unnb7ar98fa03ngo_at_4ax.com> 





If I want to model say a book where I have a root element of book represented as
n pages, can I do something like this:



table BOOK




pageid FK



and



table PAGES




pageid PK


content text



i.e do I need to have a (f.e.) primary key in the BOOK table? The only reason I
can see that I would want to is if I want to have many different books but then
I would have to have BOOK, and then a BOOK_PAGES joining table no? 



Danke!



-Tomas


                   ,%%%,
                 ,%%%` %==--
                ,%%`( '|
               ,%%_at_ /\_/
     ,%.-"""--%%% "_at_@__  
    %%/             |__`\       
   .%'\     |   \   /  //
   ,%' >   .'----\ |  [/
      < <<`       ||      
       `\\\       ||        
         )\\      )\
 ^^^^^^^^"""^^^^^^""^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^


THE DUKE 

Received on Fri Aug 22 2003 - 22:08:28 CEST












Original text of this message