Skip to content

Commit

Permalink
HCK-8151: use primary or unique constraint for relationship parent fi…
Browse files Browse the repository at this point in the history
…eld (#34)

<!--do not remove this marker, its needed to replace info when ticket
title is updated -->
<!--jira-description-action-hidden-marker-start-->

<table>
<td>
<a href="https://hackolade.atlassian.net/browse/HCK-8151"
title="HCK-8151" target="_blank"><img alt="Sub-task"
src="https://hackolade.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10316?size=medium"
/>HCK-8151</a> Other SQL targets: Use Unique constraint of the parent
field while creating relationship
  </td></table>
  <br />
 

<!--jira-description-action-hidden-marker-end-->
## Content

A relationship parent field should be:

a PK or
a part of composite PK or
UK or
a part of composite PK
  • Loading branch information
taras-dubyk authored Sep 25, 2024
1 parent 6e49fa6 commit 0220c4b
Showing 1 changed file with 8 additions and 1 deletion.
9 changes: 8 additions & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,14 @@
"disablePipelines": true
},
"relationships": {
"compositeRelationships": true
"compositeRelationships": {
"allowRelationshipsByProperties": [
"primaryKey",
"unique",
"compositeUniqueKey",
"compositePrimaryKey"
]
}
},
"FEScriptCommentsSupported": true,
"enableFetchSystemEntitiesCheckbox": true,
Expand Down

0 comments on commit 0220c4b

Please sign in to comment.