Design Patterns

More on one-to-many/many-to-one associations in Doctrine 2

September 10th, 2013

In my previous blog I explained how to handle the mythical "join tables with extra columns" in Doctrine 2. It comes down to _not_ creating a many-to-many association, but a one-to-many/many-to-one. But in the real world we usually treat this process a bit differently: We draw up a contract in which we specify the information that's needed, including the person and company it relates to.

Jasper N. Brouwer

Doctrine 2: How to handle join tables with extra columns

September 6th, 2013

A _join table_ table (also know as a _junction table_ or _cross-reference table_) is a table that links 2 (or more) other tables together within the same database by primary key. This means that a join table will only contain foreign keys, there is no place for these extra columns.

Jasper N. Brouwer

Wrapping your models snugly in ACL interfaces

May 21st, 2011

More and more we're encountering Zend Framework projects where people have written up their own model implementations. Which isn't a surprise of course, as the framework does not include ORM, and the models folder is still empty after running the "zf create project" command...

Ramon de la Fuente


January 21st, 2010

Once upon a time I stumbled across Ruby on Rails, a MVC framework on top of the programming language Ruby. Through RoR I became familiar with the MVC-pattern, ActiveRecord-pattern, and soon lots an lots of other patterns. About 4 months ago I came in contact with Zend Framework, which also follows the MVC-pattern.

Jasper N. Brouwer