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

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

    dkubb committed May 19, 2010
Commits on May 18, 2010
  1. Use #to_prepare hooks for properly reloading models

    snusnu committed May 18, 2010
    This should ideally fix most of the reloading issues
    that previously occured mostly in development mode.
    
    The way it works now, is the following:
    
    Production mode:
    All models are required once on application bootup
    and all FK properties get initialized. Subsequent
    request won't reload the models.
    
    Development mode:
    All models are required once on application bootup
    and all FK properties get initialized. Subsequent
    requests will do the same before being processed.
  2. Let's be honest. There are no specs yet

    snusnu committed May 18, 2010
    The DM related part of the provided functionality
    will be tested in the upcoming dm-config gem on
    which dm-rails will depend on. Once that's done
    dm-rails will get proper specs itself, testing the
    integration with rails.
Commits on May 17, 2010
Commits on Apr 30, 2010
Commits on Apr 10, 2010
  1. Removed unused method

    snusnu committed Apr 10, 2010
Commits on Apr 9, 2010
Commits on Apr 1, 2010
  1. Depend on rails-3.0.0.beta2

    snusnu committed Apr 1, 2010
Commits on Mar 30, 2010
  1. Better ruby interpreter compatibility

    snusnu committed Mar 30, 2010
    This is partly a regression from a jruby fix that
    has been applied some time ago
    
      See http://is.gd/b7fGz
    
    Also, it solves the following issue on ruby-1.9
    
      Implicit argument passing of super from method
      defined by define_method()
    
    [#1228 state:resolved]
  2. Use a Benchmarking mixin instead of an Adapter wrapper

    snusnu committed Mar 30, 2010
    This patch completely drops the use of the adapter
    cascade along with adapter wrappers.
    
    This will hopefully work around the problems with
    transactions and migrations, which both need real
    AbstractAdapter descendants to work. The previous
    adapter wrappers were'nt properly recognized which
    basically rendered transactions and migrations
    useless for the sake of being able to display some
    benchmarking information in rails' server logs.
    
    This patch should get around that by only extending
    the adapter behavior with our benchmarking needs,
    instead of wrapping it in a new object that's not
    a descendant of AbstractAdapter.
    
    Thx to Xavier Shay for the idea!
    
    In the hopefully not so longterm, the benchmarking
    mixin will go away anyway, because (at least) the
    DO adapters will provide useful benchmarking info
    by means of passing a struct containing the info
    to a Connection#log(info) method that's defined in
    ruby instead of only in the native driver
    implementations (as is the case currently).
Commits on Mar 28, 2010
Commits on Mar 27, 2010
Commits on Mar 26, 2010
  1. Set config.data_mapper to our very own object

    snusnu committed Mar 26, 2010
    This was made possible in http://is.gd/b0MA0
    Previously the "toplevel" railtie config key was
    specified by
    
      railtie_name :data_mapper
    
    which forced us to put our custom configuration
    object into
    
      config.data_mapper.configuration
  2. Added .bundle to .gitignore

    snusnu committed Mar 26, 2010
Commits on Mar 12, 2010
Commits on Mar 11, 2010
  1. Update Benchmarking method definitions to use class_eval

    dkubb committed Mar 11, 2010
    * This works-around some problems with JRuby 1.4 not being able to
      handle a block with the arguments that were defined.
  2. Minor whitespace fix

    dkubb committed Mar 11, 2010
Commits on Mar 1, 2010
  1. Updated Contributors

    snusnu committed Mar 1, 2010
  2. Use require_dependency to preload models and lib

    Patrik Sundberg committed with snusnu Feb 25, 2010
    When STI is used for models the auto-require feature
    of active_support may require a parent model when
    requiring a child model before preload_models then
    requires the same parent model again causing the
    descendants of the parent to get corrupted and
    relationship properties in the children end up not
    getting defined correctly.
    
    Maybe this could get fixed in dm-core? Sounds like
    something weird is going on when STI related classes
    are required/loaded twice? To be honest, I don't
    exactly understand what's going on here, but Patrik
    confirms that this patch fixes / works around the
    STI issues.
Commits on Feb 25, 2010
Commits on Feb 23, 2010
  1. Updated gemspec

    snusnu committed Feb 23, 2010