Update sqlite3 binary handling
Accidentally let a minitest-ism slip into master
Prior code rearrangement didn't work well on travis-ci, though it
tested locally just fine.  Moving the code for PostgresHelper back to
test/helper.rb (which is safe, now that test/helper.rb doesn't include
test/unit) and doing explicit requires within the rake tasks that need
it.
Some dope forgot to commit the delete of this file.  Oh, right.  That
was me.
Removing rails23 from the travis test suite.  Rails 2.3 support is
getting sketchy at best, and users of 2.3 would probably be better
off using an old version of activerecord-jdbc-adapter.  Naturally,
pull requests to fix 2.3 support (as long as they don't break
support for more recent AR versions) would be accepted.
Mark test_update_all_with_joins_and_offset_and_order to only run if
AR version is 3.2 or higher
Move test_create_xml_column to a shared module, and only run the test
in AR 3.1 or higher.
Travis build tweak

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.
Further travis-ci tweaks

New .travis.yml is travis-lint clean, so we'll see if this actually
does what I want w.r.t. rails23 builds.
Merge branch 'driver-jar' of https://github.com/kares/activerecord-jdbc-adapter into kares-driver-jar
Continue updating driver-jars

  * 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.
Merge pull request #263 from jruby/driver-jar

Updated driver-jar work
Merge pull request #238 from gregors/consolidate_methods

consolidate modify_types methods across different places in the code
finish updating (explicitly loaded) driver-jars
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
JDBC driver names should be on one (re-usable) place
Merge pull request #270 from kares/master

finish driver-jar (related) updates
no need for poluting Kernel (#jdbc_require_driver) anymore
BigDecimal is only required in MySQL adapter
(BigDecimal nor #to_d ain't used anywhere else)
we do not really need to load the JDBC driver here 
happens when the jdbc-adapter gets required (on connection initialization) 
@see f15684f687a8259cd6cfec87234245b8ffd86adc
make sure we can use the latest jdbc driver gems with AR gems :
- 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