Base DooModel Class for all models

[kostik]

I am proposing to add a base class DooModel from which all other models will be extended. The main purpose of this class is to provide a bunch of useful methods which should be inherited by all models. for example i propose the following interface

Code: Select all

abstract class DooModel{

    public function __construct($assocArray = NULL) {
      if ($assocArray != NULL) {
        $this->update($assocArray);
      }
    }

    public function update($assocArray = NULL) {
      $myAttributes = get_object_vars($this);
      foreach ($myAttributes as $attribute => $value) {
        if( isset($assocArray[$attribute]) ) {
          $this->$attribute = $assocArray[$attribute];
        }
      }
    }

    public function save()  {
      return $this->db()->insert($this);
    }

    public function delete()  {
      return $this->db()->delete($this);
    }

    public function getById()  {
      return Doo::db()->find($this, array('limit'=>1));
    }

    public function getAll()  {
      return Doo::db()->find(get_class($this));
    }
   
   public function getByField($fieldName, $fieldValue) {
      // to do
   }
}


So as you can see this will simplify retrieving, deleting and saving objects. Also you can create object from a associative array which could be your form data.
so instead of saying $article = new Article; $article->name = $_POST['name']; $article->text = $_POST['text']; you can say $article = new Article($_POST);
Also right here we can implement caching (this is another issue).

DB Caching
Concept is simple for now,
When u getById, cache result, when u delete/save, invalidate the entry

Waiting for feedback.

[kostik]

no one has any thoughts at all?

[leng]

The extra query methods will be really useful. On the cache, we will need to think of a nice way to implement it.

[roman]

Where would form input data validation fit?

[kostik]

Roman, that is up to you. The concept merely states that u could create a model from an associative array.
But to address validation you could for example create something like this.

Code: Select all

private $_rules=array('name'=>'[a-z]/i','phone'=>'[0-9_-.\s]'); //which is an associative array of expected field names and regular expression to validate;

public function validate() //this would validate and return $errors array


so u can create an object from $_POST and then validate() object and return any $errors
I think we could implement DooForm class which would handle all of the form's stuff.

[leng]

Hey guys did you miss out the update_attributes and insert_attributes in DooSqlMagic? It is meant for $_POST or $_GET stuffs

[kostik]

leng, do u ever sleep?
and yes, I haven't got to those yet.

[leng]

I am on an abnormal routine... sometimes*

[roman]

Kostik, that was a good tip. Thanks. And I like the idea of having a class or something that would handle most, if not all, things related to handling form input.

Hey guys did you miss out the update_attributes and insert_attributes in DooSqlMagic? It is meant for $_POST or $_GET stuffs

Is that intended to do something along the lines of what kostik was talking about?

I am on an abnormal routine... sometimes*

Leng, as a short off-topic comment for you (it applies to me too as my day schedule is abnormal as well), take a look at http://www.pslgroup.com/dg/13D2F2.htm. That, combined with other articles in http://www.google.com/search?q=study+healthy+subjects+sleep+5+hours+hormones, should inspire one to sleep enough night hours I am dropping everything right now and going to bed while it's still just little after midnight

[Ming]

hi

i think its not so good , because you can't inheriting your classes later
better : OrmEngine::loadValue( UserModel, $array );

like pojo pattern in java

Ming