[Deprecated] DMZ 1.5.3 (DataMapper OverZealous Edition)

[eluser]OverZealous[/eluser]
Whew, lotta stuff :-)

[quote author="ntheorist" date="1248493769"]I've been using a join_key() method i wrote up a while ago but what i really want to do is integrate 'extending' tables, which would be pretty much self joins but enforced automatically (like classes) – so say you had a 'person' model and you wanted a 'user' model to extend it (rather than being a separate relation on its own). It would be similar to the original self-joins (ie class User extends Person), but would automatically include the fields. I can see working it into DMZ using set_join_field perhaps?[/quote]

I'm not 100% sure what you are asking here. Currently, you can create more than one Model off the same table. There's nothing in the docs on that, but I haven't figured I needed to yet. I did it like this, though:

Code:

class Person extends DataMapper {
    $table = 'people';
    $model = 'person';

    $has_one = array('company');
}

class User extends Person {
    $table = 'people';
    $model = 'user';
    $has_one = array(
        'company' => array(
            'join_self_as' => 'person'
        )
    );
}

class Company extends DataMapper {
    $has_one = array(
        'person',
        'user' => array(
            'join_other_as' => 'person'
        )
    );
}

I don't like doing this, but I have a lot invested in existing code that looks similar to the above (different models). In hindsight, I should have just added an "is_user" flag to Person. It would be much easier to maintain! You could still handle simple joins like this:

Code:

class Widget extends DataMapper {
    $has_one = array(
        'user' => array(
            'class' => 'person'
        )
    );
}

$widget->user->get();

heh i can pick out parts of the original in there – y'know i wonder if stensi still cruises the forums and knows how far his original project had been taken?

I used the original DM docs as a starting point. Stensi knows, as I have contacted him. I was hoping (originally) to not have a completely separate fork, but he has been really busy. I don't know what to expect when/if he comes back. DMZ has made some major changes now, and "merging" them might be difficult. 8-/

one quick question i had (looking at the code) - is how does DMZ process queries with joined relations?

DMZ will automatically join related information if told to, but only then. You should check out include_related under the Get (Advanced) section.

btw i gotta say i really like how you laid out the development src.

Thanks. It's necessary, because my IDE was starting to give me fits. It's a huge file. Personally, if I could start over, I would have separated out all the validation rules, and probably broken the class into multiple classes that inherited each other, like CodeIgniter's DataBase classes. But that isn't practical, since it would require a significant effort, and provide minimal performance benefit, or even reduce performance.

Also I attempted to move the validation into a separate library

I have no plans to modify the way validation works as of now. It's pretty good, anyway, as it only loads the CI Form_Validation library when it is accessed, so it shouldn't load it if you never use rules from Form_Validation. Check out __get (in 15_magic.php) to see how it is done.