Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add minimal support for EXTENDED TIME(STAMP) WITH TIME ZONE types [JDBC611] #642

Closed
firebird-automations opened this issue Mar 7, 2020 · 3 comments

Comments

@firebird-automations
Copy link

Submitted by: @mrotteveel

Two special 'bind-only' datatypes were added, EXTENDED TIMESTAMP WITH TIME ZONE and EXTENDED TIME WITH TIME ZONE. These types are the same as their 'normal' WITH TIME ZONE counterpart, with the difference that they have an extra signed short (serialized as 4 bytes in the wire protocol) with the offset in minutes, which is populated for both offset and named zone values.

The support in Jaybird will be minimal: we will parse the value exactly the same as the 'normal' WITH TIME ZONE types, basically ignoring the extra bytes. On sending the values, these bytes will always be zeroed. This support is intended to address situations where users manually set the bind to an extended type.

Commits: 6aa26af

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Fix Version: Jaybird 4 [ 10441 ]

Fix Version: Jaybird 4.0.0 [ 10903 ]

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

status: Resolved [ 5 ] => Closed [ 6 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants