[Deprecated] DMZ 1.5.3 (DataMapper OverZealous Edition)

[eluser]OverZealous[/eluser]
@MeanStudio
There are some examples in the include RTF file. I know they aren't great, but they should help.

Now, as for your question, I'm not sure what you are asking. What item do you want to relate o itself?

As far as I can tell, there is no relationship going on. I think simply storing each version in the DB with a $has_many relationship, along with a version #, would be enough, then diff (or whatever) your changes. There's no need for self references. To get the latest version, just query

Code:

$client->quote->order_by('version', 'DESC')->get(1);
// although, this might work, if you don't need version numbers:
$client->quote->order_by('id', 'DESC')->get(1);

If you really want to store the history as a self-reference, you would write something like this:

Code:

class Quote extends DataMapper {
    $has_many = array(
        'quote_history' => array(
            'class' => 'quote',
            'other_field' => 'current_quote'
        )
    );

    $has_one = array(
        'current_quote' => array(
            'class' => 'quote',
            'other_field' => 'quote_history'
        ),
        'client'
    );
}

You can store the relationship wither on quotes, as current_quote_id (highly recommended), or in a dedicated current_quotes_quote_histories table, which current_quote_id and quote_history_id columns. Obviously

You'll still probably want to keep track of a version number, or use something like DataMapper's automatic created_on or updated_on column.

PS: Why would you serialize your quote data? It's not searchable (via the DB) that way. It's usually far better to store the data in multiple columns, so it is searchable, unless the data is binary, or would never need to be searched. Since you are looking at storing a versioned history, I think being searchable would be very useful. Just an opinion / question, and I'm sure you have a good reason!