[ZF] How do you define a 1-to-1 relationship?

[konsama]

I'm reading Rob Allens Zend Framework in Action book and he has examples for Many-to-Many, and in the below case a 1-to-Many relationship.
But he never showed any examples on how to do a 1-to-1 relationship. Can somebody teach me how it should be done?



1-to-Many example

class Books extends Zend_Db_Table_Abstract 
{
    protected $_name = 'books';
    protected $_dependentTables = array('Reviews');
}

class Reviews extends Zend_Db_Table_Abstract 
{
    protected $_name = 'reviews';
    protected $_referenceMap    = array(
        'Book' => array(
            'columns'           => array('book_id'),
            'refTableClass'     => 'Books',
            'refColumns'        => array('id')
        )        
    );
} 

Let's say that I want to connect Class Books with Class Genre, a 1-to-1 relationship. How do I determine which of the tables should use either one of these? Which table is depending on the other table?

• $_dependentTables
• $_referenceMap

Do I still define their relationship exactly like how the 1-to-Many example is done?

[Jake Arkinstall]

One genre has many books... Though to map the two it'd be a case of mapping ID to ID.

[konsama]

One genre has many books...

Yeah you're right, now my memory is starting to come back to me. All I need is 1:M and N:M to make a basic database web application.

The 1:1 relationship was only for the more advanced database theorists out there.
I've been working 2-dimensionally for so long that I forgot how to think 4th-dimensionally. Like Doc says from "Back to the future".

Thanks arkinstall!

class Genre extends Zend_Db_Table_Abstract 
{
    protected $_name = 'genre';
    protected $_dependentTables = array('Books');
}


class Books extends Zend_Db_Table_Abstract 
{
    protected $_name = 'books';
    protected $_referenceMap    = array(
        'Genre' => array(
            'columns'           => array('genre_id'),
            'refTableClass'     => 'Genre',
            'refColumns'        => array('id')
        )        
    );
} 

[felgall]

The simplest solution to a 1:1 is to put them into the one table. No second table required.

[konsama]

Thanks for the tip now I'm a database theorist too