You are not logged in.
Ads (what is this?) |
Announcement
|
Ads (what is this?) |
I totally agree with you.
This is not correct to use JNI to connect to SQLLite.
I have added your remark to the feature [Bugtracker] bug 1022.
Thanks for your test on this unvalidated component.
Best Regards,
Michaël.
I downloaded the latest milestone Win 32 V2.1.0M1 in order to try out the new Java tSQLite* connectors. In the properties for the components the location of the JNI lib must be filled in. Problem is there's no indication of what SQLITEJDBC.DLL to use. I tried using the latest from http://www.zentus.com/sqlitejdbc/dist/s … n-i386.tgz as from the license associated with component it appears to be using David Crawshaw's JDBC drivers. When I just placed the DLL in the JNI folder, it failed with a "no such native driver error". I had to replace the Talend supplied sqlietjdbc.jar file with David's jar to get the component to work. So 3 questions ..
(a) What DLL (.so) are we meant to use and should it not be provided in the Talend download ?
(b) If you're using http://www.zentus.com/sqlitejdbc/ why not consider using the Pure Java version (http://www.zentus.com/sqlitejdbc/dist/s … nested.tgz). I know it's somewhat slower than the JNI version but for most cases it's fast enough (Kettle uses the Pure Java lib).
(c) You offer a genericDB based on ODBC, why not a generic JDBC option - again Kettle offers this.
Tom