Permalink
Commits on Sep 1, 2011
  1. @nicksieger
  2. @nicksieger
Commits on Aug 31, 2011
  1. @nicksieger
  2. @nicksieger
  3. @nicksieger
  4. @nicksieger
  5. @nicksieger

    Use readerToRuby for LONGVARCHARs on 1.9 only (guyboltonking)

    Conflicts:
    
    	src/java/arjdbc/jdbc/RubyJdbcConnection.java
    nicksieger committed Aug 31, 2011
Commits on Aug 25, 2011
  1. @nicksieger

    Avoid grep which isn't standard on Windows.

    Fixes #95.
    nicksieger committed Aug 25, 2011
  2. @nicksieger

    Merge pull request #94 from lukefx/sql2000

    fixing the double ORDER BY
    nicksieger committed Aug 25, 2011
  3. @lukefx

    fixing the double ORDER BY

    lukefx committed Aug 25, 2011
Commits on Aug 24, 2011
  1. @nicksieger

    Merge pull request #92 from jdmorani/master

    Rails 3.1 support for postgresql
    nicksieger committed Aug 24, 2011
  2. @nicksieger

    Merge pull request #91 from pazustep/arel22

    Naive attempt to support ARel 2.2
    nicksieger committed Aug 24, 2011
Commits on Aug 19, 2011
  1. @jdmorani
  2. @jdmorani
Commits on Aug 18, 2011
  1. @pazustep

    Naive attempt to support ARel 2.2

    The most important change works for all adapters: ARel now passes a
    TreeManager instead of the parsed SQL to adapters; This was handled by
    calling #to_sql on the manager (if the object actually responds to that)
    deep inside #substitute_parameters, which should cover all types of
    statements.
    
    Also, the global Arel::Visitors::VISITORS is deprecated, and instead
    each adapter should respond to :visitor_for returning an appropriate
    visitor. The MySQL adapter was changed to do that, but other adapters
    are still using the deprecated API.
    pazustep committed Aug 18, 2011
Commits on Aug 17, 2011
  1. @nicksieger

    Merge pull request #90 from albertosaurus/master

    Another fix to fetching indexes
    nicksieger committed Aug 17, 2011
  2. @albertosaurus

    Changing how we're getting indexes again. Previously we were supporting

    up to ten columns in a multi-column index.  This is wrong, because Postgres
    supports up to 32 columns in an index, and this may change.  Ideally, I'll
    rewrite this logic completely based on postgresql_adapter in active record.
    albertosaurus committed Aug 17, 2011
  3. @nicksieger

    Merge pull request #89 from albertosaurus/master

    Quick fix for column order when fetching indexes
    nicksieger committed Aug 17, 2011
  4. @albertosaurus

    In Postgres, the column order in indexes has significant performance …

    …implications.
    
    See http://www.postgresql.org/docs/9.0/static/indexes-multicolumn.html
    This fixes the issue where the Postgres adapter would ignore the column order when getting an index.
    albertosaurus committed Aug 17, 2011
Commits on Aug 12, 2011
  1. @nicksieger

    Merge pull request #85 from pazustep/index-lengths

    Include index length information for MySQL on connection#indexes
    nicksieger committed Aug 12, 2011
  2. @nicksieger
Commits on Aug 5, 2011
Commits on Aug 4, 2011
Commits on Jul 29, 2011
  1. @nicksieger
Commits on Jul 28, 2011
  1. @nicksieger
  2. @nicksieger

    Add ruby-debug to the project

    nicksieger committed Jul 28, 2011
  3. @nicksieger
  4. @nicksieger
Commits on Jul 27, 2011
  1. @nicksieger
  2. @nicksieger

    Merge pull request #81 from charl/master

    Added bindings support
    nicksieger committed Jul 27, 2011
  3. @nicksieger

    Get rid of pick_rails_version

    nicksieger committed Jul 27, 2011
  4. @nicksieger

    Add mocha

    nicksieger committed Jul 27, 2011
  5. @nicksieger

    Minor formatting tweak

    nicksieger committed Jul 27, 2011
Commits on Jul 26, 2011
  1. @nicksieger