Hello Comunity, I have a question that is more of database modeling theory ( normalisation / data organisation ) nature. Please advise me.
For a job interview I am required among other things to create a phone book application. I am thinking about database design. Although it is a simple assigment, I would like to make good first impression and do It by the book. Show them I understand relational database concepts. The application should list phone book entries. Also it should allow insertion, deletion, and modification. Name Surname City Phonenumber1 .. PhonenumberN ================================================= Mark Knolpfer Los Angeles 0002224343 .. 4443332233 ........ .... .. Allthough a denormalised model of 1, maybe 2 tables would work fine in reality, I want to go by the book. I want your reviews and possible improvements. I was thinking of having 4 tables. PERSON, PHONE_NUMBER, PERSON_CITY , CITY. It seems somehow stupid to have a table that holds only the phone number. And relation of person and phone number is 1 .. N. Please suggest. What would be the right way considering normalisation by the book. _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
