Permalink
Commits on Jun 22, 2010
Commits on Jun 8, 2010
  1. Version bump to 1.0.0

    dkubb committed Jun 8, 2010
Commits on May 27, 2010
  1. Version bump to 1.0.0.rc3

    dkubb committed May 27, 2010
Commits on May 26, 2010
Commits on May 24, 2010
Commits on May 23, 2010
Commits on May 22, 2010
  1. Mixin the constraint API into each loaded adapter

    * The previous approach relied on the adapters being setup, which
      may not always be true if bundler is being used. Sure, we could tell
      people to use :require => nil on adapters, but I would rather not have
      to explain that exception every-time this or related problems appear.
    
    * Even though this was not strictly related to #1280, I am tagging it
      with the bug because it is the exact same problem as with transactions
    
    [#1280]
    dkubb committed May 22, 2010
Commits on May 20, 2010
  1. Updated copyright year

    dkubb committed May 20, 2010
Commits on May 19, 2010
  1. Bumped gem deps to latest versions

    dkubb committed May 19, 2010
  2. Version bump to 1.0.0.rc2

    dkubb committed May 19, 2010
  3. Stripped whitespace

    dkubb committed May 19, 2010
  4. Version bump to 1.0.0.rc1

    dkubb committed May 19, 2010
Commits on May 18, 2010
  1. Ingore Gemfile.lock and *.rbc files

    * Minor rearrangement of .gitignore file
    dkubb committed May 18, 2010
Commits on May 17, 2010
  1. The constraints API is supported on all adapters

    However, only some adapters will provide true
    native constraints in the backend.
    
    This brings spec failures down to one (the same on
    1.8.6, 1.8.7 and 1.9.1) for in_memory and yaml
    adapters
    snusnu committed May 17, 2010
Commits on May 4, 2010
  1. Resolved require order dependency issues

    Fixed true foreign key constraint generation in
    backends that support it.
    
    It is now possible to require 'dm-constraints'
    either before or after DataMapper.setup has been
    called, and the behavior will always be the same.
    
    The API for DataMapper and Model gets included
    when the first adapter that supports constraints
    is required.
    
    If one or more adapters that support constraints
    are already set up, the API for these adapter(s)
    is included into all those adapters.
    
    In any case, a DataMapper::Adapters.const_added
    extension gets installed at the time that the gem
    gets required. This extension will make sure that
    the adapter related constraint API will get
    included into any new adapter that might get set
    up. This is guaranteed to happen if the newly set
    up adapter properly calls const_added(:AdapterName)
    after it was defined.
    
    This will also make sure that the automigration
    code gets included into the DataMapper and
    DataMapper::Model modules as soon as a supported
    adapter is used.
    
    Since establishing native foreign key constraints
    in the backend involves automigration (at least
    for all current adapters), this commit also adds a
    runtime dependency on dm-migrations to this gem.
    snusnu committed May 4, 2010
Commits on Apr 30, 2010
  1. Use DataMapper::Spec.setup for setting up spec runs

    Run specs on supported adapters simply by setting
    the ADAPTER env variable
    snusnu committed Apr 30, 2010
Commits on Apr 1, 2010
  1. [dm-more] Removed unnecessary :branch => 'master' from Gemfiles

    * The master branch is the default branch anyway, so specifying this
      explicitly was redundant.
    dkubb committed Apr 1, 2010
Commits on Mar 22, 2010
Commits on Mar 20, 2010
  1. [all] Only require the gem under test in spec_helpers

    This will make sure that all the gems require
    everything they need to be fully functional.
    snusnu committed Mar 17, 2010