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

Date(time) fields converted to Nullable, even when they're part of the primary key #225

Open
dlouseiro opened this issue Nov 23, 2024 · 1 comment

Comments

@dlouseiro
Copy link

WIth the current implementation of the target, all date and datetime fields received from a tap are converted to Nullable, even when they're part of the table's primary key/order by, which causes the synchronisation to fail.

My proposal would be for the Date(time) field to only be converted to Nullable when they're not part of the table's primary key.

@dlouseiro
Copy link
Author

Created a proposal of implementation here

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

No branches or pull requests

1 participant