- This topic has 25 replies, 6 voices, and was last updated 20 years, 1 month ago by
.
-
Posts
-
That’s great, I’m glad its working better for you now. MySQL is supported very well by many tools, if you don’t need SQL Server either MySQL or PostgreSQL are good choices.
Hmmm. Weird behavior for the driver stuff. I will download a MSSQL Server driver and try it in debug.
Ok, I think I know what is wrong. Because the class hierarchy is split between jar files, the classloader being used to sequentially open each jar file and examine contents for CLass.isAssignableFrom(Class) is to seeing that the subclass of BaseDriver is also a Driver. I will add a bug report on this.
In the meantime, there is a work around for the problem. Unjar all three jar files and then create a single jar file with the content of all three. When you open it in the Driver editor you will now see the SQLServerDriver in the list of available drivers. I have verified that this works.
I was having the _exact_ same problem, the driver was not being displayed. I solved the problem by literally typing in “com.microsoft.jdbc.sqlserver.SQLServerDriver” in the drop-down menu that displays drivers. Things went fine after that; I was able to connect to the database.
This should be automated in the next release, the problem was that the wizard was only searching 1 JAR at a time for the proper class, so in the case of the MS driver (split across 3 JARs) it wasn’t finding a valid driver. Jeff fixed this in what will be the 3.8.3 release.
I just wanted to let you know 3.8.2 still has a malfunctioning Microsoft SQL driver. I could not connect to my MS SQL server with the provided driver. I created a new one (based on the post above from Sep. 21) and I could connect.
