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

DB2Database has incorrect fractional precision for TimestampType #2880

Closed
ctgnz opened this issue May 26, 2022 · 1 comment · Fixed by #2892
Closed

DB2Database has incorrect fractional precision for TimestampType #2880

ctgnz opened this issue May 26, 2022 · 1 comment · Fixed by #2892

Comments

@ctgnz
Copy link
Contributor

ctgnz commented May 26, 2022

The DB2 for z/OS definition (Db2zDatabase) correctly sets the maximum fractional digits for TimestampType to 12.

private static final int MAX_DB2Z_TIMESTAMP_FRACTIONAL_DIGITS = 12;

However, this applies to DB2 LUW as well, at least from version 9.7 onwards.

The override of getMaxFractionalDigitsForTimestamp() should be moved up from Db2zDatabase to AbstractDb2Database - possibly guarded with a check on major database version >= 9.

@ctgnz
Copy link
Contributor Author

ctgnz commented May 26, 2022

This problem means that you can't generate a changelog from an existing DB2 LUW database that uses columns with precision 12.

@kataggart kataggart added this to To Do in Conditioning++ via automation May 30, 2022
Conditioning++ automation moved this from To Do to Done Jul 28, 2022
nvoxland pushed a commit that referenced this issue Jul 28, 2022
…2880) (#2892)

Set max fractional timestamp digits to 12 for all DB2 editions (#2880)

Co-authored-by: ctg <ctg@LAPTOP-50VTJSGN>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants