AtkOneToOneRelation - Revision history

Sandy: /* Example (atkMetaNode) */

2010-10-04T09:28:11Z

Example (atkMetaNode)

← Older revision		Revision as of 09:28, 4 October 2010
Line 29:		Line 29:
	An employee has one address		An employee has one address

	$policy->hasOne('address');		public static function meta(atkMetaPolicy $policy) {
			$policy->hasOne('address');
			}

	[[Category:Relations]]		[[Category:Relations]]

2010-10-04T09:25:13Z

← Older revision		Revision as of 09:25, 4 October 2010
Line 24:		Line 24:

	Referential key a_id is in the same node, so this is the slave-configuration.		Referential key a_id is in the same node, so this is the slave-configuration.

			=== Example (atkMetaNode) ===

			An employee has one address

			$policy->hasOne('address');


	[[Category:Relations]]		[[Category:Relations]]

2008-08-18T21:51:53Z

← Older revision		Revision as of 21:51, 18 August 2008
Line 1:		Line 1:
			{{relation}}

	An atkOneToOneRelation defines a [[ATK Relations\|relation]] between two tables where there is one record in the first table that belongs to one record in the second table.		An atkOneToOneRelation defines a [[ATK Relations\|relation]] between two tables where there is one record in the first table that belongs to one record in the second table.

2006-12-28T10:03:40Z

← Older revision		Revision as of 10:03, 28 December 2006
Line 22:		Line 22:

	Referential key a_id is in the same node, so this is the slave-configuration.		Referential key a_id is in the same node, so this is the slave-configuration.

			[[Category:Relations]]

2006-12-28T09:54:23Z

← Older revision		Revision as of 09:54, 28 December 2006
Line 1:		Line 1:
	~~#REDIRECT~~ [[~~ATK_Relations##~~atkOneToOneRelation]]		An atkOneToOneRelation defines a [[ATK Relations\|relation]] between two tables where there is one record in the first table that belongs to one record in the second table.

			The atkOneToOneRelation supports two configurations: master mode and slave mode. The mode to use is detected automatically based on the value of the $refKey parameter.

			function atkOneToOneRelation($name, $destination, $refKey="", $flags=0)

			* $name: The unique name of the attribute.
			* $destination: the destination node (in module.nodename notation)
			* $refKey: foreign-key field (master mode) or empty (slave mode)

			=== Master mode example ===
			The node in which the relation is implemented, is considered the master (code is in node A). And the referential key pointing to the master record (a_id) is in the destination node (node B).

			[[image:atkOneToOne_master.jpg\|center]]

			Referential key a_id is in the other node, so this is the master-configuration.

			=== Slave mode example ===
			The node in which the relation is implemented (code is in node B), is considered the child. And the referential key pointing to the master record (a_id) is in the current node (node B).

			[[image:atkOneToOne_slave.jpg\|center]]

			Referential key a_id is in the same node, so this is the slave-configuration.

2006-12-28T01:58:24Z

New page

#REDIRECT [[ATK_Relations##atkOneToOneRelation]]