Why are relations an array? about php-activerecord HOT 7 CLOSED

Initially, we were considering using PHP's ArrayObject for a collection returned form the database, but we decided not to because of the overhead involved. If someone wanted to provide some benchmarks that shows a large performance hit is not incurred when using ArrayObject, then we could implement the feature.

from php-activerecord.

I think this would provide a lot of flexibility. See my hack there: https://github.com/greut/php-activerecord/blob/relation_count/lib/Relationship.php#L453-470

from php-activerecord.

Can you please go through this?

greut@1383d64

Cheers,

from php-activerecord.

What about this?

<?php
class Person extends ActiveRecord\Model
{
    static $has_many = array(
        array('addresses')
    );
}

$person = Person::find(1);
// all the addresses, no hit on the DB. (obj1)
$addresses = $person->addresses;
// the last five addresses, no hit on the DB (obj2)
$addresses = $addresses(array('limit' => 5, 'order' => 'id desc'));
// hits the DB and cache the result
var_dump($addresses[0]);

obj1 and obj2 are two different objects, so calling it results in creating a modified copy.

• the commit
• the branch

from php-activerecord.

little resurrection .

Could this be merged into master ?
This will greatly benefit, in all poly relations.

If there are anything thats missing, before it can be merged, I'll try to find the time to finish it.
Btw, would it be possible to implement it same as ruby with .. find / where on the collection ?

from php-activerecord.

@nakashu See #108, which introduces a fix for this. We're looking at pulling it into v1.1 ATM. Thanks for the ping!

from php-activerecord.

closing in favor of #376

from php-activerecord.