Hi to all, > All those years of writing EJB apps, and it never even occurred to me that that was possible. I always just called the right thing based on the column type of the query :-) me too :-)
> In my experience that depends on the underlying driver. I think Christopher is right, all depends on the driver ... so a safer approach could be like in Spring that the developer read column data as he knows (using the right data type), and then transform the value (during reading of values) as needed by the serializer ... Or do you remember my proposal (one of many :-) ) of last week to set in serializers an optional Map for translating some non compatible Class after serialization not done of a single value ? In this way these problems could be handled in a transparent way, when required and activated by the developer (and using code written by the developer), sounds a little complicated but maybe i coudl try to write a sample implementation... but if this is not wanted, please skip. Anyway, no problem, there is a skeleton to try write something, and then see what to do ? Thanks to all, Sandro
