Request: MSSQL 2025 VECTOR datatype

[JanBrandenburger]

Hi @rhuijben ,

First of all, thank you very much for your voluntary work and continued dedication to developing and maintaining RepoDb. I really appreciate the time and effort you invest into the project.

I have a question regarding Microsoft SQL Server 2025: do you currently have any plans (or a roadmap item) to support the new VECTOR datatype in RepoDb (e.g., type mapping, parameter handling, and reading/writing values)?

I’m explicitly asking this as a question—totally understood if there are no plans at the moment, or if it’s outside the current scope.

Thanks again for all your work!

Best regards,
Jan

[rhuijben]

Good news: this was pretty trivial to implement with the parameter handling cleanup I'm working on. Support should be available 'soon'.

In theory you can set the values already using the just added Json support, but I wouldn't go that route... It has some rough edges that are handled much cleaner with the proper support.
(It just required a few minor patches to the SqlServer specific code.)

Test code is available in the builds of #40. And some testcode is on that branch too. (Requires SqlServer 2025 obviously. Luckily there is a test container in docker)

[rhuijben]

See https://github.com/AmpScm/RepoDb/blob/main/src/RepoDb.SqlServer.IntegrationTests/Common/VectorTests.cs
for the testcases for this feature. (More work to write some tests, than to get this working)

[JanBrandenburger]

Hi @rhuijben ,
I'm speechless. :-)
I was expecting anything from “in 6 months” to “unfortunately, I can't do that.”
But the fact that you've already built a first implementation within 12 hours... Wow. Thank you for that.
I'm currently still in the process of installing MSSQL 2025. I think I'll be done by the end of next week and could then get started on it.
I'm excited and grateful.

Best regards from the neighboring country,

Jan

[rhuijben]

Fix released. Should work a tiny bit better with Microsoft.Data.SqlClient 7.0.1+, as I found a bug in 7.0.0 and earlier writing this support. Current version has a workaround though.