Re: Foreign key constraint with literal?

Just my suggestions so everything is just my opinion.

First if you are building new tables I would not use candidate fields as
join fields. I would be using identity keys as my primary keys.

My unique PART_NUMBER would be my Candidate key. The Obsolete flag would
just be a in a where clause in a view.

Just access the data through the view if you do not want obsolete parts.
Big subject.


On Tue, Apr 27, 2021 at 7:01 AM Justin Taylor <jtaylor.0ab@xxxxxxxxx> wrote:

Here's the situation. I have a parent table, PART_MASTER, with several
child tables (e.g. PROMOTIONS). The tables have a foreign key relationship
(PART_MASTER.PART_NO = PROMOTIONS.PART_NO). PART_MASTER also has a column
to indicate obsolete parts. I need the relationships to be
(PART_MASTER.PART_NO = PROMOTIONS.PART_NO and PART_MASTER.OBSOLETE = '0').

I've tried everything I can think of, but I can't get this to work. Am I
going to have to create triggers over every table involved?

TIA
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com