Bugs item #16240, was opened at 2007-12-11 15:16 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=7857&aid=16240&group_id=2014
Category: None Group: None >Status: Closed >Resolution: Out of Date Priority: 3 Submitted By: Nobody (None) Assigned to: Nobody (None) Summary: JNDI config requires jdbc driver? Initial Comment: irc claims that driver: must still be specified in database.yml when jni is in use. This shouldn't be required. Interestingly, you can set _any_ value in driver: when using jndi, and the application can still talk to the database for whatever reason (though it fails to function properly, it definitely has a jdbc connection), for example, setting driver: 'firetruck' results in the following jdbc error from oracle: ArgumentError: ORA-00933: SQL command not properly ended clearly the call is getting all the way to the db and back, even without a proper driver: line. ---------------------------------------------------------------------- Comment By: Ryan Bell (kofno) Date: 2007-12-12 06:57 Message: Is it still required? There was some code in the jdbc adapter that would try to find out what driver was being used by the database connection. Even if it is still required, it is required in the same way that selecting a hibernate dialect is still required when using JNDI. Sure, you can select any dialect, but the wrong ones will cause your stuff. To fail. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=7857&aid=16240&group_id=2014 _______________________________________________ Jruby-extras-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/jruby-extras-devel
