You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error: translate: Error with parser 'SQL::Translator::Parser::DBI': JDBC not supported
at /usr/share/perl5/SQL/Translator/Parser/DBI.pm line 154.
If you're not familiar with DBD::JDBC, here is my synopsis: the thing has at least two components: a standalone java application which speaks JDBC on one side and listens for incoming connections on the other. It acts as a proxy... The perl part of DBD::JDBC talks to the little server. So, a variety of RBDMS are made available to perl's DBI via this bridge. (I guess DBI is to perl as JDBC is to Java?)
So I looked around a little and determined that I should implement SQL::Translator::Parser::DBI::JDBC. I inspected SQL::Translator::Parser::DBI::SQLServer for guidance. I quit when I saw the following in the DBD::JDBCREADME file.
NOT YET IMPLEMENTED
DBI-defined methods, including
@daveloyall Short answer: no idea ;) Generally talking to MSSQL via unixODBC is the best way to do it currently (especially if you can get your hands on the Microsoft linux driver).
Nevertheless I would appreciate pointers to how to properly setup a JDBC connection on linux however, so maybe this can be tried in the future.
This command line:
returns:
If you're not familiar with
DBD::JDBC, here is my synopsis: the thing has at least two components: a standalone java application which speaks JDBC on one side and listens for incoming connections on the other. It acts as a proxy... The perl part ofDBD::JDBCtalks to the little server. So, a variety of RBDMS are made available to perl'sDBIvia this bridge. (I guess DBI is to perl as JDBC is to Java?)So I looked around a little and determined that I should implement
SQL::Translator::Parser::DBI::JDBC. I inspectedSQL::Translator::Parser::DBI::SQLServerfor guidance. I quit when I saw the following in theDBD::JDBCREADMEfile.Meanwhile, I'll return to trying to use
unixODBCto talk to MS SQL Server.The text was updated successfully, but these errors were encountered: