Home/ Questions/Q 723763
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T06:08:43+00:00

CREATE TABLE Phone ( phoneID – PK . . . ); CREATE TABLE PhoneDetail

  • 0
CREATE TABLE Phone
(
phoneID - PK
.
.
.
);

CREATE TABLE PhoneDetail
(
phoneDetailID - PK
phoneID - FK points to Phone
phoneTypeID ...
phoneNumber ...
.
.
.
);

CREATE TABLE Customer
(
customerID - PK
firstName
phoneID - Unique FK points to Phone
.
.
.
);

A customer can have multiple phone numbers e.g. Cell, Work, etc.
phoneID in Customer table is unique and points to PhoneID in Phone table.
If customer record is deleted, phoneID in Phone table should also be deleted.

Do you have any concerns on my design? Is this designed properly? My problem is
phoneID in Customer table is a child and if child record is deleted then i
can not delete the parent (Phone) record automatically.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    As mrjoltcola already addressed the normalization, I’ll tackle the problem of having a record in phone and no record in phone detail.

    If that is your only problem there are three approaches:

    1) do not delete from detail table but from phone with CASCADE DELETE – gives a delete from two tables with single SQL statement and keeps data consistent

    2) have triggers on the detail table that will delete the parent automatically when last record for a parent is deleted from the child (this will not perform well and will slow down all deletes on the table. and it is ugly. still it is possible to do it)

    3) do it in the business logic layer of the application – if this layer is properly separated and if users(applications) will be modifying data only through this layer you might reach desired level of consistency guarantee

    • 0