Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 369551

Summary:	jpa platform usage prevents platforms having different defaults
Product:	z_Archived	Reporter:	James Sutherland <jamesssss>
Component:	Eclipselink	Assignee:	Nobody - feel free to take it <nobody>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	tom.ware
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description James Sutherland

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

2022-06-09 10:32:31 EDT

The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink