Skip to content

dialect: a DATE and a TIMESTAMP column are read with their own getters - #74

Merged
stbischof merged 1 commit into
mainfrom
pr/date-timestamp-type-map
Oct 31, 2026
Merged

stbischof merged 1 commit into
mainfrom
pr/date-timestamp-type-map

Conversation

@stbischof

@stbischof stbischof commented Oct 31, 2026 •

Copy link
Copy Markdown
Contributor
  • The default type map gives Types.DATE the column type DATE and Types.TIMESTAMP the column type TIMESTAMP, so such a column is read with getDate / getTimestamp instead of getObject.
  • Oracle reports its DATE as TIMESTAMP, since it carries a time of day, and keeps it so: read as a date it would lose the time, and its members and segment predicates would miss the rows.

@stbischof
stbischof force-pushed the pr/date-timestamp-type-map branch from 0d1abbf to b9899d2 Compare October 31, 2026 14:57
The default type map gives Types.DATE the column type DATE and
Types.TIMESTAMP the column type TIMESTAMP. Oracle reports its DATE as
TIMESTAMP, since it carries a time of day, and keeps it so: read as a
date it would lose the time, and its members and segment predicates
would miss the rows.

Signed-off-by: Stefan Bischof <stbischof@bipolis.org>
@stbischof
stbischof force-pushed the pr/date-timestamp-type-map branch from b9899d2 to ec1ac66 Compare October 31, 2026 15:04
@stbischof
stbischof merged commit b4a452f into main Oct 31, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant