-
Type:
Suggestion
-
Resolution: Won't Fix
-
None
-
Component/s: Infrastructure & Services - Application Lifecycle
-
Environment:Oracle database
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Turning on automatic creation of foreign keys and indices while using Oracle database results in a lot of errors. This is due to the Oracle restriction that all foreign keys must be uniquely named. JIRA has multiple foreign keys with the same name. There are, for example, multiple 'ParentIssue' relations.
I was able to make a workaround extending GenericHelperDAO to uniquely name all the foreign keys. Maybe JIRA should do that way by default.
Uniquely naming all the foreign keys won't solve all the errors though. See the related issue.
- relates to
-
JRASERVER-5261 Mapping errors in entitymodel relations
-
- Closed
-
-
JRACLOUD-5260 Automatic creation of foreign keys and indices fails on Oracle database
- Closed