Yes, I mentioned the approach elsewhere. Now you have two database things (the FK and the constraint) describing a single relationship. I don't think it's very

Yes, I mentioned the approach elsewhere. Now you have two database things (the FK and the constraint) describing a single relationship. I don't think it's very elegant and people often forget the unique constraint. One table is a much better solution.