Permalink
Commits on Sep 7, 2010
Commits on Sep 3, 2010
  1. Version bump to 1.0.1

    dkubb committed Sep 3, 2010
Commits on Sep 1, 2010
Commits on Aug 30, 2010
  1. Updated gem dependencies

    dkubb committed Aug 30, 2010
Commits on Aug 25, 2010
  1. Updated Gemfile for rails rc2

    dkubb committed Aug 25, 2010
Commits on Aug 17, 2010
  1. Minor simplification to Gemfile

    dkubb committed Aug 17, 2010
Commits on Aug 16, 2010
  1. Updated to use patched rspec

    dkubb committed Aug 16, 2010
Commits on Jun 8, 2010
  1. Version bump to 1.0.0

    dkubb committed Jun 8, 2010
  2. Revert "Updated :position property to be required and set the minimum…

    dkubb committed Jun 8, 2010
    … value"
    
    This reverts commit c9a8089.
    
    * This looks like it conflicts with dm-validations. Will need to
      revisit this again later to see if it can be done in a way that
      works with dm-validations but also uses strong DB constraints.
Commits on May 27, 2010
  1. Version bump to 1.0.0.rc3

    dkubb committed May 27, 2010
Commits on May 26, 2010
  1. Removed useless comment

    dkubb committed May 26, 2010
Commits on May 25, 2010
  1. Removed embedded transaction calls

    dkubb committed May 25, 2010
    * Transactions should be used by caller code, and not by any dm gems, at
      least until nested transactions are supported by the DO drivers
Commits on May 24, 2010
Commits on May 23, 2010
Commits on May 20, 2010
  1. Updated copyright year

    dkubb committed May 20, 2010
Commits on May 19, 2010
  1. Version bump to 1.0.0.rc2

    dkubb committed May 19, 2010
  2. Update :scope to be coerced into an Array if it is not already

    dkubb committed May 19, 2010
    * Minor doc/spec update to show this new behaviour
  3. Version bump to 1.0.0.rc1

    dkubb committed May 19, 2010
  4. Reorganized specs pass on all adapters/rubies

    snusnu committed May 19, 2010
    See http://is.gd/cfnmf for the necessary commit to
    dm-transactions
Commits on May 18, 2010
Commits on May 17, 2010
Commits on May 14, 2010
  1. Ensure repair_list uses position and default order to reorder the list

    dkubb committed May 14, 2010
    * The reason for this change is that a datastore will sort the objects
      based on the order specified, but if any values are equal (and the
      order does not specify any further sorting) then the datastore is free
      to sort them however they like.
    
      In this case PostgreSQL sorted things differently from MySQL or SQLite,
      but this could've been inconsistent between any adapters.
    
      By providing default_order as a sort of "tie breaker" we can ensure
      that objects with equal position are sorted by the default_order after
      position. The default_order will be the model key unless a different
      default_order was specified for the model.
    * Alter code to only return true if the individual Resource#update
      statements also all return true