Chapter 13: Data Validati

Chapter 13: Data Validation 226 } } $this->hasColumn('name', 'string', 255); $this->hasColumn('code', 'string', 2, array( 'usstate' => true ) ); Listing 13-50 Listing 13-51 Here is the same example in YAML format. You can read more about YAML in the YAML Schema Files (page 195) chapter: --- # schema.yml # ... State: columns: name: string(255) code: type: string(2) usstate: true Now if I try and save a State with an invalid state code then the validation will fail. $state = new State(); $state->name = 'Tennessee'; $state->code = 'ZZ'; if ( ! $state->isValid()) { echo 'State is invalid because "ZZ" is not a valid state code'; } Conclusion If we want Doctrine to validate our data before being persisted to the database, now we have the knowledge on how to do it. We can use the validators that are provided with the Doctrine core to perform common validations of our data. The next chapter (page 231) is an important one as we will discuss a great feature of Doctrine, Inheritance (page 231)! Inheritance is a great way accomplish complex functionality with minimal code. After we discuss inheritance we will move on to a custom strategy that provides even better functionality than inheritance, called Behaviors (page 239). ----------------- Brought to you by

Chapter 14: Data Hydrators 227 Chapter 14 Data Hydrators Doctrine has a concept of data hydrators for transforming your Doctrine_Query instances to a set of PHP data for the user to take advantage of. The most obvious way to hydrate the data is to put it into your object graph and return models/class instances. Sometimes though you want to hydrate the data to an array, use no hydration or return a single scalar value. This chapter aims to document and demonstrate the different hydration types and even how to write your own new hydration types. Core Hydration Methods Doctrine offers a few core hydration methods to help you with the most common hydration needs. Record The first type is HYDRATE_RECORD and is the default hydration type. It will take the data from your queries and hydrate it into your object graph. With this type this type of thing is possible. $q = Doctrine_Core::getTable('User') ->createQuery('u') ->leftJoin('u.Email e') ->where('u.username = ?', 'jwage'); Listing 14-1 $user = $q->fetchOne(array(), Doctrine_Core::HYDRATE_RECORD); echo $user->Email->email; The data for the above query was retrieved with one query and was hydrated into the object graph by the record hydrator. This makes it much easier to work with data since you are dealing with records and not result sets from the database which can be difficult to work with. Array The array hydration type is represented by the HYDRATE_ARRAY constant. It is identical to the above record hydration except that instead of hydrating the data into the object graph using PHP objects it uses PHP arrays. The benefit of using arrays instead of objects is that they are much faster and the hydration does not take as long. ----------------- Brought to you by