Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Making FK Constraint to ignore empty records
Message
 
 
À
Tous
Information générale
Forum:
Microsoft SQL Server
Catégorie:
Autre
Titre:
Making FK Constraint to ignore empty records
Divers
Thread ID:
01639981
Message ID:
01639981
Vues:
69
Hi,

How common is it to change the FK constraint that would ignore empty records. Here is an example of FK:
ALTER TABLE [dbo].[eq_file]  WITH CHECK ADD CONSTRAINT [FK_eq_file_site_category] FOREIGN KEY([SITE_NO],[category])
	REFERENCES [dbo].[calpmcat] ([SITE_NO],[CATEGORY])
	ON UPDATE CASCADE
	ON DELETE SET DEFAULT
The problem with the above is that table EQ_FILE could have any number of records where the field CATEGORY is empty string. Which means that the CALPMCAT has to have a record with empty CATEGORY for every SITE_NO that exists. Which does not make sense to me.
And the only way I see to get around it is to change the above expression to ignore records with empty CATEGORY.
My questions:
1. How do you modify the expression to ignore empty field?
2. Is this a good/common practice?

TIA
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform