Permalink
Switch branches/tags
Commits on Dec 20, 2012
  1. Merge pull request #276 from kares/jndi-driver

    guilleiguaran committed Dec 20, 2012
    JNDI updates
Commits on Dec 19, 2012
  1. move Derby specific hack out of the (generic) jdbc adapter

    kares committed Dec 19, 2012
    there's some duplication now about DS lookup but the first one is generic for all specs while the username is strictly Derby adapter specific code
    
    make sure we  always close the obtained DB connection (not just on errors) as jndi DS will be pooled most likely
  2. refactor #adapter_spec

    kares committed Dec 19, 2012
    - 2.times code seemed really hard to grasp
    - predictable order of ArJdbc (adapter) DB vendor matching
  3. no need to set the :driver for jndi config (did not work anyways)

    kares committed Dec 19, 2012
    when jdbc is being configured do not raise if there's a :driver_instance instead of the :driver
  4. do not depend on Sun's "old" FS JNDI (no where to be found)

    kares committed Dec 19, 2012
    instead use Tomcat's JNDI impl ... jars get auto-downloaded
  5. Merge pull request #258 from tinylox/oracle-in-clause-limits

    ajuckel committed Dec 19, 2012
     Oracle has a 1000 entry in clause limit.
  6. Remove duplicated primary_key method

    ajuckel committed Dec 19, 2012
    I wasn't careful enough rebasing that last change, and needlessly duplicated
    the primary_key method.
Commits on Dec 18, 2012
  1. Merge pull request #273 from kares/master

    guilleiguaran committed Dec 18, 2012
    backwards compat with current Jdbc gems (without #load_driver)
  2. allow for building + releasing of the jdbc driver gems separately

    kares committed Dec 18, 2012
    these will be tagged as "jdbc-mysql-x.x.x"
  3. update Derby to 10.8.2.2

    kares committed Dec 18, 2012
  4. update H2 to 1.3.170

    kares committed Dec 18, 2012
Commits on Dec 17, 2012
  1. Merge pull request #272 from kares/master

    guilleiguaran committed Dec 17, 2012
    make sure we can use the latest driver gems from AR-adapter gems
  2. make sure we can use the latest jdbc driver gems with AR gems :

    kares committed Dec 17, 2012
    - for MS SQL we have the jTDS 1.3.0 JDBC driver
    - for Postgres we now recommend the 9.2 driver
    - for Derby we shall allow to package latest (10.9.1) driver
  3. we do not really need to load the JDBC driver here

    kares committed Dec 17, 2012
    happens when the jdbc-adapter gets required (on connection initialization) 
    @see f15684f
  4. BigDecimal is only required in MySQL adapter

    kares committed Dec 17, 2012
    (BigDecimal nor #to_d ain't used anywhere else)
Commits on Dec 14, 2012
  1. Merge pull request #270 from kares/master

    ajuckel committed Dec 14, 2012
    finish driver-jar (related) updates
  2. finish updating (explicitly loaded) driver-jars

    kares committed Dec 14, 2012
    besides we make sure that (jdbc-xxx gem) .jars are only loaded (required) when first connection is attempted this avoids e.g. sqlite-jdbc.jar being always among loaded features when discover AR-JDBC extensions run
Commits on Dec 10, 2012
  1. Merge pull request #238 from gregors/consolidate_methods

    ajuckel committed Dec 10, 2012
    consolidate modify_types methods across different places in the code
  2. Merge pull request #263 from jruby/driver-jar

    ajuckel committed Dec 10, 2012
    Updated driver-jar work
  3. Continue updating driver-jars

    ajuckel committed Dec 10, 2012
      * A few drivers weren't updated with the new load_driver method
      * Define test_jdbc_#{adapter} tasks to test each adapter with
        the generic jdbc adapter.
Commits on Dec 8, 2012
  1. Further travis-ci tweaks

    ajuckel committed Dec 8, 2012
    New .travis.yml is travis-lint clean, so we'll see if this actually
    does what I want w.r.t. rails23 builds.
  2. Travis build tweak

    ajuckel committed Dec 8, 2012
    Perhaps I was hasty in removing rails23 entirely.  Found the
    allow_failures option for .travis.yml, so we can run the suite
    but not fail the whole build just due to rails23 incompatibility.