Zend Framework and Doctrine Putting the M in Zend

transcript

A Few Notes…

• On the presentation:– For the so inclined, the “model object” referred to

is equivalent to the DDD domain object (I think).• On Me:– Isaac Foster (isaac.z.foster@gmail.com)– Zend Framework Certified– Currently working for Tabula Digita.

Your Honor, I Intend to Prove…

• That Doctrine’s value added over Zend_Db is the framework it provides for business logic.

• Other features make it a complete, powerful tool.

First TLA: MVC

• Model – Behavior and data of the application.• View – Display information.• Controller – Takes inputs

from the user, invokes the model and chooses the view.

The M in MVC• Model objects hold business data and logic.• Model != DB:– True, data that a model acts on is often persisted in a db.– Db code in the model layer, not necessarily model object.– Model object should focus on what makes it special.

your models -->

Separate Business and Persistence Logic

• DBAL (Database Abstraction Layer)– One API to rule them all.

• ORM (Object Relational Mapper)– Put the object in, get the object out.

• ↑Consistency, ↑Reliability, ↑Reuse, ↑Ease…• It’s a Good Thing

Snoop shares histhoughts on the activerecord pattern.

Frameworks and Libraries Help us Achieve These (and other) Goals

and one of those frameworks is…

Zend Framework

• MVC Framework + Components• Great View and Controller framework:

IOC lets you focus on the ACTION, not the request, response, router, dispatcher …

• Components Zend_Acl for authorization. Zend_Auth for authentication Zend_Session for session management

… what about M?

The M in Z-E-N-D?

• Zend_Db wraps db driver for DBAL. • Zend_Db_Table wraps a table, gives some

structure to a model, ORM-ish.• Zend_DB_Table_Row wraps row, active record

features.

The M in Z-E-N-D?

• Provides:– Protection from SQL Injection– Query Construction API– Transactions– Profiler– Cache

So What’s the Problem?

Definitely Zend_Db, not Zend_Model• Not much from a business logic perspective:– Little help you stay DRY with business logic.–Not much in the way of model life-cycle hooks

(preSave, postSave, preDelete, etc).• Still thinking about db’s, tables, and table

references, not models and relationships.

Doctrine is… DBAL + ORM + Active Record + Model Framework

• Provides framework for business logic…– Plugins hook into events, core code

untouched.– Reuse code and structure with behaviors.– Configure validation and rules.– Doctrine model IOC ≈ ZF controllers IOC

• Think more about models, not tables.

Doctrine

• Will create your database tables.• Migration tools.• Performance tools and configurations.• Utilities– Command line interface– Pagination

Let’s Take It For a Spin

A Problem To Solve…

• Need to keep track of Users– Auto incremented id.– Email property must be valid email address.– Password must be hashed.– Want to send a confirmation email to new users

after they register.

A Doctrine Solution

A Harder Problem…

• Exercise 1st Amendment right to blog– Need to update blog post, track previous versions.– Want to attach images to a post.• Store them on Amazon S3

– Update author’s numPosts field after blogging.– Don’t feel like creating tables manually.

A Doctrine Solution

Doctrine Basics

Guideposts

• Doctrine_Connection ≈ Zend_Db• Doctrine_Table ≈ Zend_Db_Table_Abstract• Doctrine_Record ≈ Zend_Db_Table_Row_Abstract

Doctrine Core Classes

• Doctrine_Manager– Manages connections, knows available drivers.– Handles application wide options.

• Doctrine_Core– Manages autoloading.– Methods to create tables, export database, etc.

Connections

• Connect to a database:

• MySql, MsSql, Oracle, Postgre, DB2, Sqlite.

Bootstrapping

• Connections and autoloading in bootstrap.– Doctrine autoloader for models.– Zend Autoloader for Doctrine library files.

Defining Models: Goal

• Model creation should be like Lego building.– Configure when possible, code if necessary.• Let framework do the easy stuff.• Leverage framework for harder stuff.

Defining Models

• Each model has a Doctrine_Table.– Structure and meta-info stored there.

• setTableDefinition and setUp create the table:– hasColumn → add properties – hasOne → add one-to-one relationships– hasMany → add one-to-many and many-to-many

• Model can be defined in code or YAML config.

A More Detailed Problem…

• Need a Blog model with:– Unique integer key.– Title (non null, less than 150 chars)

– Text (non null).– Flag for whether it is published (default false).– Foreign key for relating to the author.

• DETAILS, REQUIREMENTS, RULES!! WHAT TO DO!!

Defining Models: Properties

Doctrine_Record::hasColumn()

• Adds properties to your model.– Blog has a title property, content property, etc.

• hasColumn($name, $type [,$length, $options])– name – “propertyName” or “columnName as propertyName”

– type - int, string, boolean, float, many more.– length – max length– options – options

Property Options

• default – sets default value.• primary – if the primary key.• autoincrement – if autoincrementing id.• notnull – enforce the value not be null.• email – enforce the value be a valid email.• Other validator indicators

More Details…

• Blog also needs:– An Author.– Images attached to it for upload and display.

• WHAT TO DO!!

Defining Models: Relationships

Doctrine_Record ::hasOne()

• Defines one-to-one associations between your model and another.

• hasOne($associationClass [, $options])– associationClass –either “associationClass” or

“associationClass as associationName”– options – the association options

Doctrine_Record::hasMany()

• Add one-to-many, many-to-many associations.• A Blog has Comments (1-to-many).

• A User can be in many Groups and a Group can have many Users (many-to-many).

• hasMany($associationClass [, $options])– name – “associationClass” or “associationClass as

associationName”– options – association options

Zend Framework and Doctrine Putting the M in Zend

Documents