in reply to Re: Avoiding SQL double jeopardy
in thread Avoiding SQL double jeopardy

PersonId INTEGER,
PersonRole TEXT,

The problem with that is PersonRole defines what PersonId is. Meaning, PersonId is two different data entities in one column. This breaks normalization.

Well, unless the entity is who the person is, and what role they play is merely an attribute for this table. If that is not the case, it should be two separate columns.