Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on Feb 10, 2012
  1. @mackstar @nateabele

    Syntax fixes

    mackstar committed with nateabele
Commits on Jan 3, 2012
  1. @gwoo

    Happy 2012!

    gwoo committed
Commits on Aug 15, 2011
  1. @nateabele
  2. @Howard3 @nateabele

    Doing a general QA and Docblock

    Howard3 committed with nateabele
  3. @Howard3 @nateabele

    Query: Removed the hasMany & limit check that is only applicable to r…

    Howard3 committed with nateabele
    …elational databases from
     the _associate method and did a general QA cleanup.
    Database: Added the hasMany & limit check from query into the read method. Did a general QA
Commits on Jun 17, 2011
  1. @davidpersson
Commits on Jun 12, 2011
  1. @Howard3

    Doing a general QA and Docblock

    Howard3 committed
Commits on Jun 11, 2011
  1. @Howard3 @nateabele

    Fixed a condition where a hasmany relationship used in conjunction wi…

    Howard3 committed with nateabele
    …th both limit and order
    would result in improperly applying order.
  2. @Howard3 @nateabele

    Query: Added a 'relationships' key to the default array.

    Howard3 committed with nateabele
    1: Added a test for removing the limit value.
    2: Added the new default 'relationships' key to  the export test.
    3: Fixed a failing test. Note: QueryTest uses a MockDatabase which the database now distinguishes
    fields by Table.field, since Query relies on a MockDatabase, this had to be changed to reflect
    the Database Changes.
    4: Added a test for 'with' associations.
    5: Added a test for removing the group value.
    MockQueryPost: Added an association; hasMany MockqueryComment.
  3. @nateabele

    Implementing `\data\source\Database::group()`, and refactoring group …

    nateabele committed
    …key formatting in `\data\model\Query`.
  4. @Howard3 @nateabele

    Query: Added alias so that models are properly joined. (nate)

    Howard3 committed with nateabele
        1:modelName resolves to an alias if it exists (used for relationships)
        2: schema now returns mappings for fields that are sub-arrays with a key pointing to their
        relationship (or master database) see below
        3: fields now accept arrays mapped to their models so that limiting fields can be done in
        such a fashion 'fields' => array('ModelName' => array('id', 'name'),
        'ModelTwo' => array('text'));
        1:Removed the Mock model class within the file
        2: Fixed tests
        3: Added tests for new relationships & syntax for fields
     Added MockCompany & MockEmployees files to mocks/data
        These exist alongside Companies and Employees to help test the dynamics of the joins using
        different class, table, and alias names.
  5. @Howard3 @nateabele

    Recordset - _columnMap was returning relationships that weren't runni…

    Howard3 committed with nateabele
    …ng - they are now stripped
    Query -
      1:_associate now runs against the array that is 'with', previously it would iterate through
     the data in foreach, when it can already do that in the method
      2: _associate, removed unused variables
      3: Fixed errors due to referencing the wrong variable (primarily $query when it should have
      been $this)
      4: instantiated a new query object for hasMany relations to grab the ID count and run a
      datasource->read against it
      5: mapping $ids->data(); so that array_map doesn't invoke it every call
      6: removed query remapping (fields, group etc) as it was no longer necessary because of the
      $ids instantiated query object
     Database::read $defaults has two 'returns', one with a newline in it,
     removed the improper one and fixed the newline
  6. @nateabele

    `RecordSet`s now iterate properly. Implemented `Result::prev()` so th…

    nateabele committed
    …at result sets could be iterated backwards.
  7. @Howard3 @nateabele

    Reworking Relationships

    Howard3 committed with nateabele
  8. @nateabele
  9. @nateabele
  10. @nateabele

    RecordSet: Added management for relations (particularly hasMany), fix…

    unknown committed with nateabele
    …ed fetching of fields so
    they properly reflect the fields that were pulled rather than the tables actual schema
    Query: limit(false) now returns the object instance for chaining, groups can be removed using
    Database:  moved relationship management into the filter, finished hasMany relationship (for
    fetching), added a post processing hack for queries with a hasmany relationship
    Entity: Added depth support for recursively calling data so that numeric arrays (such as those
    generated by hasMany) will have their contents parsed to arrays as well
    Source: Added depth management so that you item can be called on a top level and still have full
    coverage of the related model data
  11. @nateabele

    Query: Allow removing of "limit" through Query->limit(false)

    unknown committed with nateabele
    Relationship: Constraints are arrays again
    Database: Implementing relationships
    Model: Moved relationship code to database
Commits on Jun 7, 2011
  1. @nateabele
Something went wrong with that request. Please try again.