Address :: Foreign Key Issue

[tmsincomb]

'addresses' table can have a null value for addr_field, but the 3 children <obj_...> require a value for the addr_field.

[tgbugs]

I now remember why the address field can be null. The reason is because the field can be null if the address type is constant. This is needed to handle cases where the value inserted into the database comes from a constant (i.e. in the code) that is not present anywhere in the source data.

[tgbugs]

Ah also to clarify here, this is a matter of naming confusion. In the obj_... tables that points to a whole address NOT to the field within the address, the reason for the distinction is that addr_desc_inst (etc.) are also needed and the address of the field containing the quantitative value (etc.) needed to be differentiated, I didn't have a good way to differentiate the name so unfortunately both are addr_field even though one is a string and the others are pointers to addresses.