hi,
why bother with this stuff in the first place? you'll get an exception by
the jdbc driver anyway. what else could you do but throw an exception if
you realize that the value exceeds some limit. would you always truncate?
would you like to configure if it truncates or throws an exception?
hi,
why bother with this stuff in the first place? you'll get an exception by
the jdbc driver anyway. what else could you do but throw an exception if
you realize that the value exceeds some limit. would you always truncate?
would you like to configure if it truncates or throws an exception?
man, would I love to have an application that uses entity beans where the
exception handling is the bottleneck ;-). just kidding, no offense. I would
also be interested in numbers but I would suspect that there are many other
issues with entity beans (or EJB in general) that affect the
man, would I love to have an application that uses entity beans where the
exception handling is the bottleneck ;-). just kidding, no offense. I would
also be interested in numbers but I would suspect that there are many other
issues with entity beans (or EJB in general) that affect the
