Client SDKs available on external repositories
Hi community!
I am excited to say that since the beginning of this year we have published many of the client SDKs for InterSystems IRIS, InterSystems IRIS for Health and Health Connect to the corresponding external repositories (Maven, NuGet, npm and PyPI). This provides many benefits to you such as:
- You can access the latest releases for a client SDK as soon as they get published, independent of the InterSystems IRIS release cadence
- You can integrate the SDKs as a dependency with the native package manager tool within your ecosystem and manage dependencies in an industry-standard way
- End users can access the SDKs directly e.g., when they are looking for direct access to the database layer through a SQL tool such as DBeaver
- You can publish projects with dependencies on InterSystems client SDKs without including them directly in your project
Here is a list of client SDKs we have published so far, as well as the corresponding version number of the latest release and where to find them:
Java
| JDBC | 3.10.5 | https://mvnrepository.com/artifact/com.intersystems/intersystems-jdbc |
| Document API | 1.0.3 | https://mvnrepository.com/artifact/com.intersystems/intersystems-document |
.NET
| ADO | 2.6.0 | https://www.nuget.org/packages/InterSystems.Data.IRISClient/ |
| Bindings | 2.5.2 | https://www.nuget.org/packages/InterSystems.Data.Bindings/ |
| XEP | 2.4.0 | https://www.nuget.org/packages/InterSystems.Data.XEP/ |
| Entity Framework Core | 1.0.0 | https://www.nuget.org/packages/InterSystems.EntityFrameworkCore.Iris/ |
| Document API | 1.1.0 |
Node.js
Python
| Python SDK | 5.3.0 | https://pypi.org/project/intersystems-irispython/ |
Going forward client SDKs will be published to external repositories as soon as a new version is available. The external repositories will also become the major distribution channel for client SDKs.
Usage of the client SDKs is subject of the Terms of Use as outlined here: https://www.intersystems.com/IERTU/
If you haven't used the external repositories yet, I encourage you to give them a try. As always, we are looking forward to your feedback!
Comments
Thanks, I've asked for this for the last 10 years at least.
I thought there was supposed to be a very different driver for NodeJS, with SQL support, driver published I don't know what for, and who will use it without access to SQL.
Python driver, I would not say the best implementation, I tried to report about issues there, and were told that's not going to be fixed.
@Stefan Wittmann - Please expedite publication of version 2.0.3 of the Node.js package, which WRC tells me will fix the problem that's been causing my gj :: configExplorer extension to crash VS Code.
Hi @John Murray the 2.0.3 release of the node.js native artifact is on the way and should show up on npm during the day.
Many thanks for this. I have now published a new release of the gj :: configExplorer extension that works in VS Code on Windows.
It's fantastic that developers can finally access the drivers without having to jump through hoops! It's hard to understand why this had to be such a difficult process all these years. But anyway, the drivers are finally easy to obtain... directly from InterSystems. Great! 😀
... the icing on the cake would be a simple way to see what has changed between the JDBC driver versions, such as which features have been added or which bugs have been fixed.
If you'd like to know how this can be done in a charming way, here's a link to an informative page about the MS SQL JDBC driver: Releases · microsoft/mssql-jdbc
Andreas
Microsoft is not even against publishing drivers in open source
We are working on incorporating the changelog information directly into the official documentation, so it's not far away! In some cases you can find them in the publication already (e.g. https://pypi.org/project/intersystems-irispython/).