At the moment SQL Anywhere is not supported (at least, we did not test it yet). You can try to download a JDBC driver for this database, if any, and define this custom driver in Data Sources dialog.
After reading your email I remembered that SQLAnywhere supplies JDBC drivers as part of the product. They provide both a JDBC 3 and JDBC 4 driver, and there is an article here regarding how to set them up.
I followed the instructions and was able to make a successful connection. However I did receive "driver not capable" errors from the getTables functionality. I experienced this with both of the vendor supplied drivers.
Having worked similar problems before, I am certain the problem is not in the JDBC drivers, but rather the particular sql code you are executing through them.
If you will send me the sql used for your selections in the various sections of this product I will be glad to rework it to the SQLAnywhere dialect. Since you probably don't have SQLAnywhere specific sql code, it is usually best to start with the sql for the latest version of SQL Server.
I have attached images of the setup for the driver, the datasource and the error I received when trying to sync.
Currently we do not compose the SQL statements on our own, just call JDBC metadata API, implemented by the driver. So the question is just find the driver supporting all necessary methods, like getTables().
I had SQL Anywhere 12 working perfectly fine for a while now but today i refreshed the connection to see if new tables were created and i got the same issue you described above
[HYC00] [Sybase][JDBC Driver]Driver not capable
I can still run queries against the tables if i know the names but autocompletion and the table list is broken.
I dont know how long this has been broken as it has been a while since i refreshed the tables.
I reverted DataGrip from 2020.3 to 2020.2 but that did not help, i did not change anything with my driver install.
I never resolved this problem. It was a bit of an experimental project and we decided it was not worth fighting the technology particularly since the vendor did not want to engage.
1. A driver configured to use the sajdbc4.jar that comes with sqlanywhere 12 as a class sybase.jdbc4.sqlanywhere.IDriver (i guess this probably exists for other sybase databases as well)
2. A url based connection jdbc:sqlanywhere:uid=<userid>;pwd=<password>;dsn=<odbc_dsn_name>
This works just as it worked before with the difference that you get an error message "catalogs are not supported" (or something similar, my german version shows "Kataloge werden nicht unterstützt")
Hello.
At the moment SQL Anywhere is not supported (at least, we did not test it yet). You can try to download a JDBC driver for this database, if any, and define this custom driver in Data Sources dialog.
Regards,
Alexander.
Alex -- thanks for the quick response..
After reading your email I remembered that SQLAnywhere supplies JDBC drivers as part of the product.
They provide both a JDBC 3 and JDBC 4 driver, and there is an article here regarding how to set them up.
I followed the instructions and was able to make a successful connection. However I did receive "driver not capable"
errors from the getTables functionality. I experienced this with both of the vendor supplied drivers.
Having worked similar problems before, I am certain the problem is not in the JDBC drivers, but rather the particular sql
code you are executing through them.
If you will send me the sql used for your selections in the various sections of this product I will be glad to rework it
to the SQLAnywhere dialect. Since you probably don't have SQLAnywhere specific sql code, it is usually best to start with the sql for the latest
version of SQL Server.
I have attached images of the setup for the driver, the datasource and the error I received when trying to sync.
Attachment(s):
Error.pdf
DataSource.pdf
Driver.pdf
Currently we do not compose the SQL statements on our own, just call JDBC metadata API, implemented by the driver. So the question is just find the driver supporting all necessary methods, like getTables().
Regards,
Alexander.
Hey @...
did you ever really solve this issue ?
I had SQL Anywhere 12 working perfectly fine for a while now but today i refreshed the connection to see if new tables were created and i got the same issue you described above
[HYC00] [Sybase][JDBC Driver]Driver not capable
I can still run queries against the tables if i know the names but autocompletion and the table list is broken.
I dont know how long this has been broken as it has been a while since i refreshed the tables.
I reverted DataGrip from 2020.3 to 2020.2 but that did not help, i did not change anything with my driver install.
Using the sajdbc4 driver
Thanks for any help
I never resolved this problem. It was a bit of an experimental project and we decided it was not worth fighting the technology particularly since the vendor did not want to engage.
Thank you for the fast response. The weired thing is that it worked perfectly fine for me for more than a year and then just suddenly stopped working.
Maybe someone will stumble upon this in the future and find a fix or if anyone from JetBrains will see this and can provide a fix.
Ok even though it still throws an issue i got it working thanks to this post https://sqlanywhere-forum.sap.com/questions/7786/using-with-liquibase-driver-not-capable
Basically i have
1. A driver configured to use the sajdbc4.jar that comes with sqlanywhere 12 as a class sybase.jdbc4.sqlanywhere.IDriver (i guess this probably exists for other sybase databases as well)
2. A url based connection jdbc:sqlanywhere:uid=<userid>;pwd=<password>;dsn=<odbc_dsn_name>
This works just as it worked before with the difference that you get an error message "catalogs are not supported" (or something similar, my german version shows "Kataloge werden nicht unterstützt")