I used the DB connector and installed the jaybird jdbc driver but cannot access the table schema.
From the screenshots, can anyone spot anything suspicious? I’m currently pointed towards the sql dialect, can I change that somehow in KNIME?
The props of the FDB:
To cross out these possibilities,
Table selector looks like this:
and Login and PW are correct
When the DB Connector is greenlit, does it mean that there is an actual connection to the DB or only that there are no errors in the syntax of the node?
when the DB Connector is green it was able to create a connection to the database. So this is already a good start. However it seems that KNIME can not get the meta data from the driver to list the available schemata. The driver should support JDBC version 4.1 or later which the Firebird Database driver does not seem to support.
You might still be able to work with the database. Have you tried to enter the schema and table name manually in the DB Table Selector node? If this also fails it might be that Firebird does not support sub-queries which then will limit the nodes that you can use since most of the DB nodes use sub-queries. If this is the case you can still use the DB Query Reader node to read data from the DB.
thanks for clearing up that green light.
I already used the JDBC 4.2 compliant driver and the JDBC 4.1 produces the same results
JDBC 4.3. cannot be installed and also tried the legacy 3. and 2. jaybird (also jdbc 4.1. or 4.2 compliant). Same results
Trying to access the DB via query also produces a nasty error
It reads and queries
The legacy connector did the trick:
if you do not use the Evaluate button in the DB Query Reader but simply execute the node it should work as well. The problem seems to be that Firebird does not support the LIMIT statement which is used when you press the Evaluate button. See the Parsed Statement which is send to the DB. So there shouldn’t be any need to use the legacy db nodes.
thanks for the heads up, it works indeed and produces output.
Although I think I will keep to the legacy nodes in the design phase, so that I don’t have to type the queries blindfolded
this is interesting. What version of Firebird DB are you using. I would like to try it myself to see what the problem with the metadata fetching is.
thanks for the info. I was able to reproduce the problem. It looks like that Firebird does not return any schema which the new framework expects as of now. We will be looking into it to change this and also support databases that do not support schemas when listing the metadata. If everything works out this will be fixed with the release in summer.
Thanks, alot . From my point of view I can perfectly work with the current tools, but nonetheless looking forward for the further smoothing
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
Hi @MatStich ,
we have just fixed the metadata retrieval problem. You can test it with the nightly build or wait until the official release in summer. However the limit problem will still exist but I have created a ticket to fix this as well.