Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Jul 5, 2010
Commits on Jun 29, 2010
Commits on Jun 19, 2010
  1. * added a 'dialect' method to the adapter so the adapter itself decid…

    authored
    …es which sql dialect it needs (for migrations)
    
    * use the dialect method to determine the right sql-extension for the adapter
    
    * adjusted specs and added one spec to reflect above changes
Commits on Jun 8, 2010
  1. @dkubb

    Version bump to 1.0.0

    dkubb authored
Commits on May 27, 2010
  1. @dkubb

    Version bump to 1.0.0.rc3

    dkubb authored
Commits on May 26, 2010
  1. @dkubb
Commits on May 25, 2010
  1. @dkubb
  2. @dkubb
Commits on May 24, 2010
  1. @dkubb
  2. @dkubb
  3. @dkubb

    Minor formatting update

    dkubb authored
  4. @dkubb
  5. @dkubb
Commits on May 23, 2010
  1. @dkubb
Commits on May 22, 2010
  1. @dkubb

    Mixin the migration API into each loaded adapter

    dkubb authored
    * 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]
  2. @dkubb
Commits on May 20, 2010
  1. @dkubb

    Fixed failing specs

    dkubb authored
  2. @dkubb

    Updated copyright year

    dkubb authored
  3. @dkubb
Commits on May 19, 2010
  1. @dkubb
  2. @dkubb

    Version bump to 1.0.0.rc2

    dkubb authored
  3. @dkubb
  4. @dkubb

    Version bump to 1.0.0.rc1

    dkubb authored
Commits on May 18, 2010
  1. @dkubb

    Added guard clauses for in_memory and yaml adapters

    dkubb authored
    * While yaml has some limited support for migrations, it is not complete
      and in_memory has none. Future updates may include methods for
      these adapters, but for now migrations should be considered
      unsupported for these adapters.
  2. @dkubb
  3. @dkubb
  4. @snusnu

    More robust checks before checking module inclusion

    snusnu authored
    Specs for in_memory and yaml still fail, but at
    least they're running now. Previously they bailed
    out immediately because of calling [] (lambda.call)
    on nil.
    
    This (like many other dm-migrations specs) looks
    kinda weird and will probably be refactored soonish
Commits on May 17, 2010
  1. @dkubb
Commits on May 10, 2010
  1. @solnic @dkubb

    Updated to the new property API

    solnic authored dkubb committed
  2. @dkubb

    Stripped whitespace

    dkubb authored
Commits on May 4, 2010
  1. @snusnu

    Makes DataMapper.auto_migrate_down!/up! @api semipublic

    snusnu authored
    These methods need to be overwritten in dm-constraints
    to perform down/up migration of foreign key constraints
Commits on May 3, 2010
  1. @snusnu

    Resolved require order dependency issues

    snusnu authored
    It is now possible to require 'dm-migrations'
    either before or after DataMapper.setup has been
    called, and the behavior will always be the same.
    
    The API for Repository and Model gets included right
    when the gem is required.
    
    If one or more adapters that support migrations
    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 migrations 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.
  2. @snusnu

    DataMapper::Spec.setup now performs adapter setup

    snusnu authored
    See http://is.gd/bRyeL for the relevant commit in
    dm-core
Commits on Apr 30, 2010
  1. @snusnu
  2. @snusnu
Something went wrong with that request. Please try again.