You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to do an unfortunate breaking change as used table names derived from entity classes may become too long and is causing issues with databases if there are limitations. For example oracle usually limits all objects to max 30 chars, thus making these unusable.
Essentially plan is to remove jpa_repository_ prefix which then gives more freedom for users to prefix their own tables with custom naming. Using custom jpa naming to add a prefix would then be migration path to 1.2.8 if user wants to keep old tables.
The text was updated successfully, but these errors were encountered:
- Modify existing JPA entity classes to
have a fixed names for constraints and
foreign key. Also name used tables so that
we don't get crazy long names which are
causing issues with some DB's
- Fixesspring-projects#468
- Fixesspring-projects#469
- Modify existing JPA entity classes to
have a fixed names for constraints and
foreign key. Also name used tables so that
we don't get crazy long names which are
causing issues with some DB's
- Fixesspring-projects#468
- Fixesspring-projects#469
We need to do an unfortunate breaking change as used table names derived from entity classes may become too long and is causing issues with databases if there are limitations. For example oracle usually limits all objects to max 30 chars, thus making these unusable.
Essentially plan is to remove
jpa_repository_
prefix which then gives more freedom for users to prefix their own tables with custom naming. Using custom jpa naming to add a prefix would then be migration path to1.2.8
if user wants to keep old tables.The text was updated successfully, but these errors were encountered: