Doctrine_manual-1-2-en

Chapter 16: Behaviors 258
CREATE TABLE job (id BIGINT AUTO_INCREMENT,
title VARCHAR(255),
description LONGTEXT,
PRIMARY KEY(id)) ENGINE = INNODB
ALTER TABLE job_index ADD FOREIGN KEY (id) REFERENCES job(id) ON UPDATE
CASCADE ON DELETE CASCADE
Notice how the job_index table is automatically created for you and a foreign key
between job and job_index was automatically created.
Because the Searchable behavior is such a large topic, we have more information on this
that can be found in the Searching (page 267) chapter.
Geographical
The below is only a demo. The Geographical behavior can be used with any data record for
determining the number of miles or kilometers between 2 records.
Listing
16-57
// models/Zipcode.php
class Zipcode extends Doctrine_Record
{
public function setTableDefinition()
{
$this->hasColumn('zipcode', 'string', 255);
$this->hasColumn('city', 'string', 255);
$this->hasColumn('state', 'string', 2);
$this->hasColumn('county', 'string', 255);
$this->hasColumn('zip_class', 'string', 255);
}
}
public function setUp()
{
$this->actAs('Geographical');
}
Listing
16-58
Here is the same example in YAML format. You can read more about YAML in the YAML
Schema Files (page 195) chapter:
---
# schema.yml
# ...
Zipcode:
actAs: [Geographical]
columns:
zipcode: string(255)
city: string(255)
state: string(2)
county: string(255)
zip_class: string(255)
Lets check the SQL that is generated by the above models:
Listing
16-59
----------------- Brought to you by