Community
Participate
Working Groups
When reading VARCHAR fields from the database, MaxDB automatically trims all trailing spaces. This is a limitation of the database that can't be changed. The bug is opened for documentation purposes only.
The test org.eclipse.persistence.testing.tests.jpa.fieldaccess.relationships.ExpressionJUnitTestSuite.testRightTrimWithoutTrimChar fails due to this peculiarity.
Created attachment 180610 [details] skip check for trailling on MaxDB The test checks that if data with trailing spaces is inserted the trailing spaces can be read again from the database. On MaxDB, this is not possible, as CHAR and VARCHAR data is always implicitly trimmed to the right. The proposed patch skips the validation of the trailing spaces on MaxDB.
Reviewed by Tom. Tested on MaxDB. Checked in at #8352.
Noteworthy: VARCHAR (n) BYTE columns, whihc correpsonds to the JDBC type VARBINARY, do not preserve trailing 0x00 bytes.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink