Community
Participate
Working Groups
From users mailing list: --------------------- The @BasicMap annotation with eclipselink 1.1 always generates a key column with the same type as the value column. Why? Do I need to change my annotation? For example: @BasicMap private Map<String, Integer> aMap = ... generates a key column of type int and a value column of type int. @BasicMap private Map<Integer, String> aMap = ... generates a key column of type varchar and a value column of type varchar. @BasicMap private Map<String, Number> aMap = ... generates a key column of type decimal(10,0) and a value column of type decimal(10,0). Thanks for any help, Peter ----------------------- Workaround is to specify the columnDefinition on the keyColumn from BasicMap.
This bug fix did not make the cut off for 2.0.0. We are deferring the bugs to Future where we can properly sort them all together based on community votes and severity. We will then assign them accordingly to future patch sets and releases.
Changing the priority of the bugs that have been recently triaged to future. Targetting them to P2 will differentiate them from the P3s that have been triaged into future earlier.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
