Let's say I have a business object called Child. It has no persistence logic, and is not designed around the UI. It merely represents a business entity.
Parent will have a reference to the Child objects: List Children
Since Parent has a direct object reference to Child(s), is it bad to also have Child have ParentId? Downside is that it is a duplicated data as there is already reference. Upside, is it will make it easier to populate from the data-layer.
Any opinions on this type of thing in general? If a business object has a reference to another business object is it bad form to also possess the foreign key?