New String) ĪllRiskData.getRelations().add(riskDetailsRelation) ĭataRow row = riskDataTable.newRow() // At the moment it is detached and needs to be add into collection. RiskDetailsDataTable /* child table which depends on parent via 'riskIDString*/, DataRelation riskDetailsRelation = new DataRelation( See the following corrected example of fist approach. Use DataRelation(String relationName, DataColumn parentColumns, DataColumn childColumns, boolean createConstraints=false)Īs we can see you try to add child’s row before parent’s one. ![]() Use tEnforceConstraints(false) before adding a row. The FOREIGN KEY constraint also prevents invalid data from being inserted into the foreign key column, because it has to be one of the values contained in the table it points to. There are three ways to achieve the goal. ![]() The problem occurs because of incorrect usage of DataTable and DataRelations. So, we will close this issue as ‘Not a Bug’. ![]() Regarding WORDSJAVA-1250, our product team has completed the work on your issue and has come to a conclusion that this issue and the undesired new behaviour you’re observing is actually not a bug.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |