[Deprecated] DMZ 1.5.3 (DataMapper OverZealous Edition)

[eluser]OverZealous[/eluser]
I found a small bug where 'related' validation rules would show an error when using the in-table $has_one relationship columns.

Also, I made some small improvements to join_related(). These are:
* The $fields array is now optional. If you don't specify it, set it to NULL, or specify it as '*', all fields on the related object are included. (This might require creating a copy of the related object.)
* A third parameter, $append_name, allows you to override the default naming method. When ignored or set to TRUE, the model or $related_field is prepended to each field. If you set it to FALSE, nothing is prepended. Finally, you can set it to anything you want, and that will be prepended.
* If a field already exists on the current object (with the $append_name), that field will be skipped silently. This means you can call $post->join_related('user', '*', FALSE), and the id field will be the id value for $post, not user.

Examples:

Code:

// Post has one User
// User has fields id, firstname, lastname

$post->join_related('user')->get_by_id(1);
// This is the same as:
//   ->join_related('user', NULL)
//   ->join_related('user', '*')
echo($post->user_id);
echo($post->user_firstname);
echo($post->user_lastname);

$post->join_related('user', 'name')->get_by_id(1);
echo($post->user_name);

$post->join_related('user', '*', 'example')->get_by_id(1);
echo($post->example_id);
echo($post->example_firstname);
echo($post->example_lastname);

$post->join_related('user', '*', FALSE)->get_by_id(1);
// note: id will be ignored, since it already exists within $post
echo($post->firstname);
echo($post->lastname);

Not all of these features have been thoroughly tested, so let me know if anything doesn't work as expected.

You can download the latest copy from here.

Finally, I have some ideas I'm planning on adding to DMZ, and I thought I'd whet your appetites:

* Extensibility: I have a method figured out that will allow everyone to add simple extensions to DataMapper without editing the core file. This will allow us to share ideas (such as query caching, or converting an object into JSON). Also, the extensions can be enabled globally, or on a per model basis.
* Production Cache: When enabled, this feature will allow DataMapper to cache a lot of the dynamically generated data, including column names (removing one query per model for every request), and validation and relationship information. The idea will be that you can delete a single file to force DM to recreate the cache, or disable it (the default) while developing code.