Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 369551 - jpa platform usage prevents platforms having different defaults
Summary: jpa platform usage prevents platforms having different defaults
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-24 11:30 EST by James Sutherland CLA
Modified: 2022-06-09 10:32 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description James Sutherland CLA 2012-01-24 11:30:07 EST 
JPA does preDeploy with DatabasePlatform and changes this to the real platform in deploy.

usePlatform ends up getting used on login, which copies over all state from the old DatabasePlatform.

If the new platform has different defaults they will be ignored.

I found this because the defaultSequence gets copied over, preventing the platform from giving a different default than table.

I fixed this by ensure JPA does not access/set the defaultSequence so it remains null.  But other properties such as binding, trimming, etc. will not allow a platform to use different defaults.
Comment 1 Eclipse Webmaster CLA 2022-06-09 10:32:31 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink