Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Nov 16, 2011
  1. @solnic

    Remove VERSION file

    solnic authored
Commits on Nov 7, 2011
  1. @solnic
  2. @solnic
  3. @solnic

    Remove jeweler

    solnic authored
Commits on Oct 15, 2011
  1. @solnic

    Bump version to 1.3.0.beta

    solnic authored
  2. @solnic

    Merge branch 'release-1.2'

    solnic authored
    Conflicts:
    	lib/dm-migrations/adapters/dm-do-adapter.rb
Commits on Oct 9, 2011
  1. @solnic

    Version bump to 1.2.0

    solnic authored
  2. @solnic

    Merge pull request #33 from miegs3/master

    solnic authored
    Allowing bytea columns to migrate by ignoring length
Commits on Oct 4, 2011
  1. @miegs3
Commits on Sep 14, 2011
  1. @solnic

    Merge pull request #13 from maxsum-corin/master

    solnic authored
    Wrong quotes in field_exists? for sqlserver
  2. @solnic

    Version bump to 1.2.0.rc2

    solnic authored
  3. @jpr5 @solnic

    Fix bug related to migrating custom types derived from builtin types.

    jpr5 authored solnic committed
    When dm-migrations' dm-do-adapter runs, Adapter#property_schema_hash is invoked
    on each property to generate the SQL for it.
    
    For Property::Text, type_map[Property::Text] yields a schema of TEXT with no
    :length property.  When DM encounters a String primitive whose length exceeds
    the schema's capacity, it auto-adjusts the schema primitive to compensate
    (i.e. in MySQL, {SHORT,MEDIUM,LONG}TEXT).  Result: MEDIUMTEXT == AWESOME.
    
    The case is different for (1) a custom Property derived from (2) a builtin
    Property whose schema primitive changes based on the Property's size options.
    For Property::Json, the first type_map[property.class] lookup is nil because
    custom types can't/don't update Adapter#type_map -- custom properties can't know
    what model/repository/adapter they're going to be on at definition time, which
    they would need because the type_map is stored on the adapter *class*.
    
    So, the second lookup type_map[property.primitive] kicks in, which for
    Property::Json is type_map[String].  That in turn yields a schema of VARCHAR
    with a :length property.  As with Property::Text, when DM encounters a String
    primitive whose length exceeds the schema's capacity, it auto-adjusts the schema
    primitive to compensate (i.e. in MySQL, {SHORT,MEDIUM,LONG}TEXT).  However, when
    dm-migrations encounters any property_schema_hash with a :length option, it
    automatically appends "(%i)" % length to the SQL statement.  Result:
    MEDIUMTEXT(123412341234) == entire migration FKD.
Commits on Sep 13, 2011
  1. @solnic
  2. @jpr5

    Merge remote-tracking branch 'origin/master' into custom_type_migration

    jpr5 authored
    Conflicts:
    
        lib/dm-migrations/adapters/dm-do-adapter.rb
    
            Resolved by taking master and re-adding property.class.superclass
            lookup.
Commits on Sep 12, 2011
  1. @solnic
Commits on Sep 9, 2011
  1. @solnic
  2. @jpr5

    Fix bug related to migrating custom types derived from builtin types.

    jpr5 authored
    When dm-migrations' dm-do-adapter runs, Adapter#property_schema_hash is invoked
    on each property to generate the SQL for it.
    
    For Property::Text, type_map[Property::Text] yields a schema of TEXT with no
    :length property.  When DM encounters a String primitive whose length exceeds
    the schema's capacity, it auto-adjusts the schema primitive to compensate
    (i.e. in MySQL, {SHORT,MEDIUM,LONG}TEXT).  Result: MEDIUMTEXT == AWESOME.
    
    The case is different for (1) a custom Property derived from (2) a builtin
    Property whose schema primitive changes based on the Property's size options.
    For Property::Json, the first type_map[property.class] lookup is nil because
    custom types can't/don't update Adapter#type_map -- custom properties can't know
    what model/repository/adapter they're going to be on at definition time, which
    they would need because the type_map is stored on the adapter *class*.
    
    So, the second lookup type_map[property.primitive] kicks in, which for
    Property::Json is type_map[String].  That in turn yields a schema of VARCHAR
    with a :length property.  As with Property::Text, when DM encounters a String
    primitive whose length exceeds the schema's capacity, it auto-adjusts the schema
    primitive to compensate (i.e. in MySQL, {SHORT,MEDIUM,LONG}TEXT).  However, when
    dm-migrations encounters any property_schema_hash with a :length option, it
    automatically appends "(%i)" % length to the SQL statement.  Result:
    MEDIUMTEXT(123412341234) == entire migration FKD.
Commits on Sep 5, 2011
  1. @solnic

    Regenerated gemspec

    solnic authored
  2. @solnic

    Bump version in Gemfile

    solnic authored
  3. @solnic

    Version bump to 1.2.0.rc1

    solnic authored
Commits on Sep 1, 2011
  1. @dkubb

    Upgraded gem dependencies

    dkubb authored
  2. @dkubb

    Stripped whitespace

    dkubb authored
Commits on Aug 8, 2011
  1. @xaviershay
  2. @nevir @xaviershay

    Give MySQL adapters the ability to specify a default storage engine f…

    nevir authored xaviershay committed
    …or migrations
  3. @nevir @xaviershay

    Add support to specify table options when creating a table via migrat…

    nevir authored xaviershay committed
    …ions. (For things like specifying MySQL storage engines, etc)
  4. @xaviershay
Commits on Aug 2, 2011
  1. @ericgj
Commits on Aug 1, 2011
  1. @ericgj

    Add Rakefile to examples

    ericgj authored
Commits on Jul 2, 2011
  1. @jpr5

    Respect repository scope when specified.

    jpr5 authored
    Previously, given configured repositories :a and :b, auto_{upgrade,migrate}!(:a)
    would affect :b also.
Commits on Jun 17, 2011
  1. @dkubb
  2. @dkubb

    Use the property class methods instead of the DEFAULT_* constants

    dkubb authored
    * When the Property::String.length is overridden the constant value will not
      update, and will be (incorrectly) used in the migration.
    * Stop memoizing the type_map to allow overridden property options to be
      used.
  3. @dkubb

    Minor whitespace fixes

    dkubb authored
Commits on Jun 9, 2011
  1. @dkubb
Commits on May 23, 2011
  1. @solnic
Commits on May 5, 2011
Something went wrong with that request. Please try again.