Not-Null constrains in Mapping file generated by Middlegen
posted 10 years ago
I currently encounter a problem I dont know if anybody else here having same experience with me or not. I dont know if it is Middlegen's problem or problem from somewhere else
I have a table BILL_TYPE_GROUP_MEMBERS which reference to BILL_TYPE_GROUPS_TLI's Uniqe colum BILL_TYPE_GROUPS_TLI_ID
and BILL_TYPE_GROUPS_TLI_ID is defined as foregin key and not-null for BILL_TYPE_GROUP_MEMBERS Table
But when Middlengen generate mapping files this BILL_TYPE_GROUPS_TLI_ID is not declared as not-null=true.
see below mapping files,
And more wild thing is BILL_TYPE_GROUP_MEMBERS also reference to some other Tables primary's key . those primary keys are not defined as not null foreign keys for BILL_TYPE_GROUP_MEMBERS , but in mapping files generated by middlegen, those foreign keys are defined as not-null="true". So it is totally another way around which what I expected or what Table 's constrains defined.
Do you have any idea about this problem? It is problem from Middlegen or problem from somewhere else?I used sqldeveloper to check my table's constrains, they all look correct.