"Rob Richardson" <Rob.Richardson@rad-con.com> writes:
> I think I just came up with a thoroughly ugly idea. The database
> supports an annealing shop, in which coils are assigned to charges.
> After the check fails, I end up with coils assigned to a charge that
> does not exist. I could set up a job that runs every minute and
> checks all coils with status "Assigned" to make sure that the
> associated charges actually exist. That would fix another recurring
> problem, in which a user intentionally deletes a charge but the
> charge's coils stay assigned to that charge.
Why don't you have a foreign key constraint from coils to charges?
regards, tom lane
