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

Support SQL Server binary data types #687

Merged
merged 2 commits into from
Feb 20, 2022

Conversation

MMatten
Copy link
Contributor

@MMatten MMatten commented Oct 28, 2021

Provide base class for binary data type support.

Provide support for the following SQL Server data types: -

  • BINARY
  • VARBINARY
  • TIMESTAMP
  • ROWVERSION

Resolves #386.

@MMatten
Copy link
Contributor Author

MMatten commented Oct 28, 2021

@javornikolov I can't see any Travis builds running for this branch/push or PR. Do you know what the problem might be?

@javornikolov
Copy link
Contributor

javornikolov commented Oct 29, 2021

@javornikolov I can't see any Travis builds running for this branch/push or PR. Do you know what the problem might be?

I contacted the Travis CO support. At first glimpse seems the same issue - running out of credits. I didn't expect 25k credits to finish that quickly...

@javornikolov
Copy link
Contributor

@MMatten, builds should work now. I am not sure whether it might need manual triggering for an existing pr or branch.

@MMatten
Copy link
Contributor Author

MMatten commented Oct 30, 2021

Thanks @javornikolov I've had a (brief) search around and I'm still not quite sure if manually triggering builds for existing PRs/pushes is supported. I've got some tweaks to add to this PR anyway so I'll see what happens then.

@MMatten MMatten marked this pull request as draft October 30, 2021 11:55
@MMatten
Copy link
Contributor Author

MMatten commented Oct 30, 2021

I'll ensure that we close #386 as part of this too.

@javornikolov javornikolov added this to the 4.0.0 milestone Oct 30, 2021
@javornikolov
Copy link
Contributor

Thanks @javornikolov I've had a (brief) search around and I'm still not quite sure if manually triggering builds for existing PRs/pushes is supported. I've got some tweaks to add to this PR anyway so I'll see what happens then.

Maybe pushing something to the branch or force-pusshing the same...

@MMatten MMatten force-pushed the support-sqlserver-timestamp-rowversion branch from a593d07 to 6b6504a Compare November 1, 2021 08:12
@MMatten
Copy link
Contributor Author

MMatten commented Nov 1, 2021

@javornikolov thanks. I've pushed more changes and we're building again. Will be interesting to see how fast we're going to be burning build credits. I'll check shortly.

@MMatten
Copy link
Contributor Author

MMatten commented Nov 1, 2021

@javornikolov I'm seeing some new JUnit deprecation warnings. I'll look to deal with these on a different PR (maybe bump up to JUnit 5 too on that one).

I have to at least test this change across all of the adapters as there's that change to the core before marking this as ready for a review.

@MMatten
Copy link
Contributor Author

MMatten commented Nov 3, 2021

@javornikolov I've now tested this across all of the adapters, apart from Snowflake as I have no usable environment (I have reached out to Snowflake to see if they'll offer us any long-term support though).

@MMatten MMatten marked this pull request as ready for review November 3, 2021 23:27
@MMatten
Copy link
Contributor Author

MMatten commented Nov 3, 2021

@javornikolov one observation on the Snowflake situation...it seems that we didn't inherit any tests for Snowflake anyway.

@MMatten
Copy link
Contributor Author

MMatten commented Jan 15, 2022

@javornikolov any review comments or do you think we can merge this (after any rebasing)?

@javornikolov
Copy link
Contributor

@javornikolov any review comments or do you think we can merge this (after any rebasing)?

@MMatten - looks reasonably good to me. Just see if we can reuse hex parsing, etc. from a library which we already use - as per my comment.

You can push to the PR to trigger a build (sqlserver tests are already available in our CI).

@MMatten MMatten force-pushed the support-sqlserver-timestamp-rowversion branch from 4701f6a to 9eb343f Compare February 19, 2022 00:13
@MMatten
Copy link
Contributor Author

MMatten commented Feb 19, 2022

@javornikolov so apart from squashing commits, etc, any other things you've spotted? We could always do with more unit tests of course!

@MMatten MMatten force-pushed the support-sqlserver-timestamp-rowversion branch 2 times, most recently from 8aec4d5 to 1602c1b Compare February 20, 2022 22:02
@MMatten MMatten force-pushed the support-sqlserver-timestamp-rowversion branch from 1602c1b to 6e317e9 Compare February 20, 2022 22:06
@MMatten
Copy link
Contributor Author

MMatten commented Feb 20, 2022

@javornikolov updates applied. I think we could be ready to merge following a final review (please).

@javornikolov javornikolov merged commit 2be9e38 into main Feb 20, 2022
@javornikolov
Copy link
Contributor

javornikolov commented Feb 20, 2022

@javornikolov updates applied. I think we could be ready to merge following a final review (please).

Thank you @MMatten!. Yes, it looks good to me to merge it. 👍

@javornikolov javornikolov deleted the support-sqlserver-timestamp-rowversion branch February 20, 2022 22:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add missing SQL Server data types
2 participants