Results 1 to 3 of 3
  1. #1
    Join Date
    Sep 2009
    Posts
    2

    Unanswered: 1 to many Relationship

    I am trying to create tables for two objects, "Document" and "Document Review". A Document Review can have many Documents in it.

    I am thinking of creating a table T_Doc_Rev with DOC_REV_ID as primary key. This is used as a foreign key in T_Doc table; however, the foreign DOC_REV_ID in T_Doc table is nullable because a document may not have an existing document review at one time.

    My question is, is it ok for the DOC_REV_ID foreign key to be nullable in T_Doc table? I am asking this because I heard it is a bad practice to have a nullable foreign key.

  2. #2
    Join Date
    Aug 2009
    Location
    Olympia, WA
    Posts
    337
    What is it you are trying to model with the t_doc_rev table?

  3. #3
    Join Date
    Sep 2009
    Posts
    2
    T_DOC_REV is for the Document Review. T_DOC is for the Document.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •