Results 1 to 8 of 8
  1. #1
    Join Date
    Nov 2008
    Posts
    4

    ERD registration system

    Im designing a simple registration system for a website, that lets users register only if they are accepted by certain criteria (radio buttons selected) . My entities are:

    Potential customers, Po_cus PK
    ----------------------------------------
    User name, User_id PK
    ---------------------------------------
    Password, Pass_id PK
    ----------------------------------------
    User name, password (Composite table)
    User_Id FK
    Pass_Id FK
    ------------------------------------------------
    Eligible, Pass_Id

    I have created an erd however I seem to have created a loop between password, username and potential customer. Oh btw ive separated username and password for security reasons. Any ideas on how to break the loop would be handy thanks.

  2. #2
    Join Date
    Apr 2002
    Location
    Toronto, Canada
    Posts
    20,002
    i don't see any connection from potential customer to any other entity at all
    rudy.ca | @rudydotca
    Buy my SitePoint book: Simply SQL

  3. #3
    Join Date
    Nov 2008
    Posts
    4
    Sorry forgot to add,

    Potential customers, Po_cus PK
    ----------------------------------------
    User name, User_id PK
    Po_cus FK
    ---------------------------------------
    Password, Pass_id PK
    ----------------------------------------
    User name, password (Composite table)
    User_Id FK
    Pass_Id FK
    ------------------------------------------------
    Eligible, Passed_Id PK
    Po_cus FK

    I tend to focus more on the html side, bit new at the DB bit.
    Last edited by Jetblack2; 11-04-08 at 09:29.

  4. #4
    Join Date
    Apr 2002
    Location
    Toronto, Canada
    Posts
    20,002
    just curious, why did you decide to build an ERD?

    and what's the logical difference between your Eligible entity and your Composite entity? they have exactly the same columns
    rudy.ca | @rudydotca
    Buy my SitePoint book: Simply SQL

  5. #5
    Join Date
    Nov 2008
    Posts
    4
    Altered, your right made no sense. As for the reasons i thought it might make things clearer in my head , when it came to coding the application and to make the sql quires alittle easier, i hope.

    Hi Just to let you know ive sorted the loop problem, if there is anything any of you would like to add or comment on feel free.
    Last edited by Jetblack2; 11-04-08 at 09:56.

  6. #6
    Join Date
    Apr 2002
    Location
    Toronto, Canada
    Posts
    20,002
    Quote Originally Posted by Jetblack2
    ... if there is anything any of you would like to add or comment on feel free.
    separating the username and password, and then tying them together again in a relationship table... seems like a lot of extra effort for no benefit whatsoever
    rudy.ca | @rudydotca
    Buy my SitePoint book: Simply SQL

  7. #7
    Join Date
    Nov 2008
    Posts
    4
    How about then just using a foreign key to connect them? i was doing it for security but what would you suggest. ?

  8. #8
    Join Date
    Apr 2002
    Location
    Toronto, Canada
    Posts
    20,002
    how about putting the password right in the user table
    rudy.ca | @rudydotca
    Buy my SitePoint book: Simply SQL

Posting Permissions

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