We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug There are missing primary keys in 3 tables. The cause seems to be due to using @jointable rather than @collectiontable
@jointable
@collectiontable
- UP_EVENT_AGGR_CONF_INTRVL_EXC - UP_EVENT_AGGR_CONF_INTRVL_INC - UP_SS_DESC_LAY_ATTR_ELMS
To Reproduce Steps to reproduce the behavior:
gradlew dataInit
Expected behavior All uPortal tables have primary keys defined
The text was updated successfully, but these errors were encountered:
https://www.logicbig.com/tutorials/java-ee-tutorial/jpa/collection-table.html
https://github.com/Jasig/uPortal/blob/271f309ed71d57396737ef0c56f2a2dff4b61a73/uPortal-layout/uPortal-layout-core/src/main/java/org/apereo/portal/layout/dao/jpa/LayoutAttributeDescriptorImpl.java
Sorry, something went wrong.
Good catch ! The thing is that the ID column exist but they aren't defined as PrimaryKeys ! The patch is easy, like the migration for existing datas.
No branches or pull requests
Describe the bug
There are missing primary keys in 3 tables. The cause seems to be due to using
@jointable
rather than@collectiontable
To Reproduce
Steps to reproduce the behavior:
gradlew dataInit
Expected behavior
All uPortal tables have primary keys defined
The text was updated successfully, but these errors were encountered: