Permalink
Commits on Jun 7, 2010
  1. Refactor to use property subclasses

    * Updated type_map structures to use references to the property subclass
      rather than the primitive
    * Remove all the special case code to support lookups via primitive
    * Minor spec fixes to cover the changes (these changes actually make
      this more consistent with auto-migrations)
    * TODO: need to make sure legacy Type objects are supported
    dkubb committed Jun 7, 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 25, 2010
Commits on May 24, 2010
  1. Minor formatting update

    dkubb committed May 24, 2010
Commits on May 23, 2010
Commits on May 22, 2010
  1. Mixin the migration 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. Fixed failing specs

    dkubb committed May 20, 2010
  2. 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. Version bump to 1.0.0.rc1

    dkubb committed May 19, 2010
Commits on May 18, 2010
  1. Added guard clauses for in_memory and yaml adapters

    * 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.
    dkubb committed May 18, 2010
  2. More robust checks before checking module inclusion

    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
    snusnu committed May 18, 2010
Commits on May 17, 2010
Commits on May 10, 2010
  1. Updated to the new property API

    solnic committed with dkubb May 5, 2010
  2. Stripped whitespace

    dkubb committed May 10, 2010
Commits on May 4, 2010
  1. Makes DataMapper.auto_migrate_down!/up! @api semipublic

    These methods need to be overwritten in dm-constraints
    to perform down/up migration of foreign key constraints
    snusnu committed May 4, 2010
Commits on May 3, 2010
  1. Resolved require order dependency issues

    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.
    snusnu committed May 3, 2010
  2. DataMapper::Spec.setup now performs adapter setup

    See http://is.gd/bRyeL for the relevant commit in
    dm-core
    snusnu committed May 3, 2010
Commits on Apr 30, 2010
Commits on Apr 28, 2010
Commits on Apr 9, 2010