Updated: 8/30/18 The HCL Informix 4.10.JC8 Java driver is one of the largest updates to an HCL Informix client in years. The number of improvements is pretty impressive. All of them around making the Java driver better, faster, easier to use. JDBC 4.0 Standards Compliance Application programmers rejoice! The HCL Informix Java driver has been JDBC 3.0 compliant for years. With 4.10.JC8 and newer versions we are now 4.0 compliant! What does that mean? That means more API's are available, and better working API's when you program against our driver. How often would one call a method in our JDBC driver to get a runtime error that "Method not supported". You should see less of that as we have implemented over 100 new API's and fixed many others. Want to use long values when you upload a blob object? Now you can! You see that createBlob() API off of your Connection Interface and wonder if it would actually make one for you? Now it will! With so many additions, I won't list them here. At the bottom is a link to the IIUG presentation that has many more details on the actual API's we added/fixed. Packaging We decided to clean house with JDBC 4.10.JC8, combining or removing pieces that are no longer needed. Part of this is the combination of ifxjdbc.jar and ifxjdbcx.jar. We have merged the files from ifxjdbcx.jar into ifxjdbc.jar. Now you just have 1 jar file. We also pulled out the SQLJ code, SQLJ hasn't been a viable standard for a decade and the code has not been maintained or updated in that time. It's still in older builds if someone still needs it. Little Things Our focus on ease of use spans both the large (4.0 compliance) and little things. IfxDriver.connect no longer needs a properties object. It's a small change, but it annoyed me to have to provide an empty object there so it might have bothered you too. Want to know more? The IIUG presentation of the new features for 4.10.JC8 is posted on SlideShare https://www.slideshare.net/BrianHughes70/informix-java-driver-improvements-410jc8 Informix is a trademark of IBM Corporation in at least one jurisdiction and is used under license.
8 Comments
Brian,
Reply
Brian Hughes
1/3/2018 12:15:01 pm
You are correct we should never return 0 in this case. I reviewed the source and there are a couple cases where we can potentially return 0 (a zero byte array passed into the read(...) is a quick way to do it). I have fixed the code in the driver for the next release.
Reply
Brian,
Reply
Brian Hughes
1/3/2018 01:26:02 pm
I don't have anything that I've encountered that would relate to this problem. Without a solid reproduction I don't have much to go on for this unfortunately. You are welcome to contact our support team to assist in tracking down a reproduction for this issue you are seeing. Sorry I can't more with this one.
Reply
Brian,
Reply
Brian Hughes
1/3/2018 01:43:05 pm
An async driver sounds pretty neat but I'm not sure we would build one until Java has a standard API for it. We will be watching the new non-blocking API's as it matures in Java and keeping tabs on user interest in this area.
Reply
6/15/2020 01:06:02 am
You have a good point here!I totally agree with what you have said!!Thanks for sharing your views...hope more people will read this article!! Go with site to find Top 10 Mediterranean food in Bastia, Corsica, France
Reply
Leave a Reply. |