Skip to content
This repository

Jun 19, 2009

  1. Dan Kubb

    Updated gemspec and history

    dkubb authored

Jun 17, 2009

  1. Dan Kubb

    Remove coercion of octal, binary, hex for Integer properties

    * This extra behavior is probably unecessary and would be little used.
      In addition it would cause "0123" to be treated as 83 rather than 123,
      which I think is probably more expected to anyone familiar with how
      String#to_i works.  It's only really the Kernel::Integer() method that
      treats "0123" as an octal, and it's in far less frequent use than
      String#to_i.
    
      If specific octal, binary or hex coercion is necessary then I would
      probably suggest using a custom type rather than an Integer property.
    
      I am removing this for now, since if I'm wrong it will be easy to add
      back in, but it would be really difficult to remove behavior like this
      after a release.
    dkubb authored
  2. Property type casting didn't cast negative numbers, and it does now.

    Ted Han authored

Jun 16, 2009

  1. Dan Kubb

    Fixed regression due to variable clobbering

    * Added spec to ensure Collection#delegate_to_relationship returns
      the expected Collection when more than one Resource is returned
      from the results.
    dkubb authored
  2. Raimonds Simanovskis

    bugfix in PropetySet#<< method which affected property definition ove…

    …rrides in other repositories
    rsim authored dbussink committed
  3. Dan Kubb

    Refactored CRUD methods across Resource and Collections

    * Updated docs for 1:m and m:m CRUD methods
    dkubb authored
  4. Dan Kubb

    Added specs for Property#valid?

    * Refactored Property#valid? once all branches were covered
    dkubb authored
  5. Dan Kubb

    Array#concat does not work with a Set

    dkubb authored
  6. Dan Kubb

    Update Relationship#query_for to respect target model scope

    [#897 state:resolved]
    dkubb authored

Jun 15, 2009

  1. Dan Kubb

    Allow instances of the same base model to be comparable

    dkubb authored
  2. Dan Kubb

    Update YAML adapter to use Pathname object for path internally

    dkubb authored
  3. Dan Kubb

    Move URI specific normalization logic into normalize_options_uri

    * Use String#<< instead of String#+ where possible since it doesn't
      create a new String instance.
    dkubb authored
  4. Dan Kubb

    Spec passing in invalid options to DataMapper.setup

    dkubb authored
  5. Dan Kubb

    Minor formatting change to DataMapper.setup spec

    dkubb authored
  6. Dan Kubb

    Updated DataMapper.setup to delegate to DataMapper::Adapters.setup

    * Moved logic from DataMapper.setup to DataMapper::Adapters, and
      split up the work across smaller, single purpose methods.
    dkubb authored
  7. Dan Kubb

    Replaces occurences of class.equal? with instance_of?

    dkubb authored
  8. Dan Kubb

    Unrolled comparison logic

    dkubb authored
  9. Dan Kubb

    Factored out validity tests from Query::AbstractComparison

    * Created Relationship#valid? to test a Resource to see if it would be
      a valid target resource
    * Created Property#valid? to test a value to see if it matches the
      constraints for the Property
    dkubb authored

Jun 14, 2009

  1. Dan Kubb

    Pass relationship/resource/collection into adapter directly

    * Pushed foreign key mapping into the adapter so that it can handle more
      of the logic itself.  This allows adapters to storage engines that do
      not link relationships using the PK/FK concept used by RDBMS'.
    * Allows for the possible use of subqueries in engines that support it,
      since if we pass in a Collection, we should be able to use it's Query
      object to construct a subquery.
    dkubb authored
  2. Dan Kubb

    Compare in-memory records against expected value

    * Sometimes the @value needs to be passed through record_value
      to get the expected value.  This performs that function when the
      comparison is initialized.
    dkubb authored
  3. Dan Kubb

    Removed unecessary save in spec

    dkubb authored
  4. Dan Kubb

    Inclusion comparison should only allow Array, Range and Set

    dkubb authored
  5. Dan Kubb

    Updated Query::Path#kind_of? and #instance_of? to proxy to the Proper…

    …ty if available
    dkubb authored

Jun 13, 2009

  1. Dirkjan Bussink

    Don't use prepared transactions anymore

    dbussink authored
  2. Dan Kubb

    Bump extlib dep to 0.9.13

    dkubb authored
  3. Dan Kubb

    Delegate Resource#save and #update to #save! and #update!

    * Work should be performed by "unsafe" method, while the "safe" methods
      are used by hooks.
    * Changed Resource#_update to simply be available for hooks, and
      delegates to Resource#update!
    dkubb authored
  4. Dan Kubb

    Skip spec that fails with in-memory adapter and 1:1 through

    dkubb authored
  5. Dan Kubb

    Persist dirty parent resources when saving a Resource

    dkubb authored
  6. Dan Kubb

    Remove dependent Resources first

    * Minor tweak to code that loads plugins when running specs
    dkubb authored
  7. Dan Kubb

    Update specs to use similar variable naming conventions

    dkubb authored
  8. Dan Kubb

    Skip failing spec when using in-memory adapter and 1:1 through relati…

    …onship
    dkubb authored
  9. Dan Kubb

    Added Query#valid? to short-circuit invalid queries

    * Some queries were being sent to the adapter when they would not
      return *any* results because they were invalid (like specifying that
      the value must match one entry in an empty list).
    * Added AbstractCondition#valid? and AbstractOperation#valid?
    dkubb authored
  10. Dan Kubb

    Refactor Query#conditions_properties to use #each_comparison

    dkubb authored
  11. Dan Kubb

    Allow ManyToMany::Relationship subclasses/mix-ins to specify options …

    …for the join relationship
    dkubb authored

Jun 12, 2009

  1. Dan Kubb

    Use String#to_i for integer/float, and Integer() for octal/binary/hex

    * This represents a change in how we typecast values.  If the value
      does not match a format we know can be coerced into the object, then
      we skip typecasting and leave the value as-is.  If dm-validations is
      enabled, the value can be identified as invalid, but the original
      value is left alone by dm-core rather than turned into a nil.
    dkubb authored
Something went wrong with that request. Please try again.