DataMapper 1.6.0

[eluser]bEz[/eluser]
Well, Phil... the bad seems to come with the good, at least for now...

[quote author="OverZealous.com" date="1239854546"]
There's nothing "wrong" with saving to the id's directly, I guess I should have made that clear. It can even save a lot of time on the DB, if you trust the users.
However, there's no validation being done on that id, so someone could send the server an invalid id, and really break your application, possibly even getting access to someone else's data. I always recommend writing code as if every user was trying to break the server.
[/quote]

I do trust the users because:
1) They are managed by a user authorization script.
2) The available Zone IDs are provided by a dropdown.
3) However, I do and will maintain the notion that "every user is trying to break the server"


[quote author="OverZealous.com" date="1239854546"]
In other words, I would look up the related object by id, and then save that object using the normal $object->save($related). Of course, if you decide to do this, you'll have to enable NULL values for the related columns, because DM doesn't save relationships until after saving $object.

As for needing the rule on both, it probably isn't necessary. The rule runs either way, and checking both just doubles the queries. The only drawback to running on just one is that you won't get an error message on the other field.
[/quote]
I updated the object_id for Zone and Season tables to allow NULLS
I modified the create method of the season model by:
A) instantiating a new zone object
B) getting data via get_by_id(zone_id) passed in from form dropdown.
C) checking if the zone->exists()

The problem is that if I try and save that object using the normal $object->save($related)

Code:

$s->save($z)

I can no longer use unique_pair validation on zone_id, because I would no longer be "DIRECTLY" saving the zone_id.
I had to remove the Validation portion for zone_id and the seq because without it being "directly set" it would fail to save.

Unfortunately, with it removed, if there was an attempt to duplicate a combination of the zone_id and the seq, it would save the season with a NULL zone_id. Also, I could not return any error strings when the save failed due to duplicate entry.

So basically, I did a mix of checking for zone existence, and if so, "directly saving" as before, as well as taking advantage of the unique_pair validation rule.

The problem I fair is that as I continue to develop, this will be a thorn in my side if your suggestions are possible and I did not resolved this.
For my scenario as it stands, i'm wondering if the functionality just isn't coded into DMZ, or is somehow a bug.

Provided the current "working" model file. Hope you can assist with further troubleshooting.

Code:

<?php if ( ! defined('BASEPATH')) exit('No direct script access allowed');

class Season extends DataMapper {
  
   var $table = 'seasons';
   var $has_many = array('commissioner', 'registration', 'conference');
   var $has_one = array('zone');
   var $validation = array(
          array(
            'field' => 'zone_id',
            'label' => 'Zone',
            'rules' => array('required', 'trim', 'unique_pair' => 'seq')
          ),
          array(
            'field' => 'seq',
            'label' => 'Season #',
            'rules' => array('required', 'trim', 'unique_pair' => 'zone_id')
          ),
        );

    function Season()
    {
        parent::DataMapper();
    }

    function create($data=NULL)
    {
    $zone_id = $data['zone_id'];
    $seq = $data['seq'];

    $z = new Zone();
    $z->get_by_id($zone_id);

    if ( $z->exists() )
    {
      $s = new Season();
      $s->zone_id = $zone_id;
      $s->seq = $seq;
      $s->gametitle_id = $data['gametitle_id'];

      if ( $s->save() )
        return array('success' => TRUE, 'message' => "Record successfully created.");
      else
      {
        $error_msg = $s->error->seq . 'Zone: ' . $zone_id . br() . ' Season: ' . $seq;
        return array('success' => FALSE, 'message' => $error_msg);
      }
    } else
    {
      $error_msg = 'Cannot Save Record, Zone no longer exist!';
      return array('success' => FALSE, 'message' => $error_msg);
    }
  }
}
/* End of file season.php */