There's been rather vague suggestions in this direction by JSR 308,
but I guess JDBC4 isn't directly tied to SE8, is it?
Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail
Linda DeMichiel <linda.demichiel@...> schrieb:
On 6/8/2012 11:25 AM, Steve Ebersole wrote:
> No one else is interested in unifying this? As-is this is yet another
mapping annotation that will need to be provider
> specific. Or do other providers not support nationalized datatypes?
I'd like to get more input on this from others in the group. Should we
do anything (now)
along these lines, or is the columnDefinition element of @Column
> On Tue 22 May 2012 04:07:48 PM CDT, Steve Ebersole wrote:
>> I apologize if I missed reference to this in previous 2.1 discussions.
>> Has there been discussion about support for nationalized character
>> data (nvarchar, nchar, nclob) mappings in 2.1? These are new types
>> standardized in JDBC 4. Handling them differently is important in
>> (1) read and wri!
>> (2) DDL exporting
>> I'd love to see a @Nationalized annotation that can be applied to
>> properties that correspond to character data.
[jsr338-experts] Re: Nationalized character data