The getDate(), getTime() and getTimestamp() methods in EmbedCallableStatement ignore the Calendar argument, and therefore give the wrong results if some other calendar than the default calendar is passed in. The client driver seems to do the right thing, though.
Also note that none of these methods are ever called by any of the regression tests.
DERBY-4582 Timestamps inserted with GMT calendar are 1 hour later when subsequently read with GMT calendar (Server Mode Only).
- is required by
DERBY-4728 10.5 backport effort tracking issue