Hi All,
I’m currently working on adding Teradata support to ar-jdbc and wanted
to
check a few assumptions I’ve made about the structure of the project.
(Apologies if this is the wrong mailing list, I couldn’t see an ar-jdbc
centric list on codehaus).
There’s still a bunch to fix but it connects and allows queries
(currently
only used against AR 2.3.14). The code is available here:
GitHub - C3/activerecord-jdbc-adapter at teradata if anyone
wants to take a gander.
I’ve implemented a new ArJdbc::Teradata module and it’s
connection_methods
counterpart but I wasn’t quite sure what the function of the
RubyJdbcConnection java classes were for. I added one based on the H2
one
(the simplest one I could see) and added it to the AdapterJavaService
basicLoad. Was that necessary?
Are the top level of jruby/activerecord-jdbc-adapter the individual
activerecord-jdbc-adapter thin gems only if there’s a corresponding
jdbc- gem available? i.e. if the Teradata JDBC drivers are license
compatible then I could make an activerecord-jdbcteradata-adapter that
pulled in jdbc-teradata which required the jars.
Cheers,
Lucas