AtkManyToOneRelation - Revision history

Sandy: /* Example atkMetaNode */

2010-10-04T09:30:01Z

Example atkMetaNode

← Older revision		Revision as of 09:30, 4 October 2010
Line 21:		Line 21:

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

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

2010-10-04T09:29:39Z

← Older revision		Revision as of 09:29, 4 October 2010
Line 16:		Line 16:

	When you use the AF_LARGE flag it is possible to customise the text for the select link, [[See Renaming_'add'_and_'select'_links_in_relations]].		When you use the AF_LARGE flag it is possible to customise the text for the select link, [[See Renaming_'add'_and_'select'_links_in_relations]].

			=== Example atkMetaNode ===
			An Employee has one department

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

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

2010-01-01T17:54:21Z

Add reference to customising Select link

← Older revision		Revision as of 17:54, 1 January 2010
Line 14:		Line 14:

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

			When you use the AF_LARGE flag it is possible to customise the text for the select link, [[See Renaming_'add'_and_'select'_links_in_relations]].

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

2008-08-19T17:20:52Z

atkManyToOneRelation

← Older revision		Revision as of 17:20, 19 August 2008
Line 2:		Line 2:

	== atkManyToOneRelation ==		== atkManyToOneRelation ==
	~~function atkManyToOneRelation($name, $destination, $flags=0)~~

	* $name The name of the attribute.
	* $destination The node we have a relationship with.

	If you do not want to use the default primary keys (for example when the * side has a combined PK), you can override them by using the functions:		If you do not want to use the default primary keys (for example when the * side has a combined PK), you can override them by using the functions:
			<syntaxhighlight lang="php">
	setLocalKey("a_id");		setLocalKey("a_id");
	setRemoteKey("b_id");		setRemoteKey("b_id");
			</syntaxhighlight>

	'''Example'''		'''Example'''

2008-08-18T21:53:29Z

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

	== atkManyToOneRelation ==		== atkManyToOneRelation ==
	function atkManyToOneRelation($name, $destination, $flags=0)		function atkManyToOneRelation($name, $destination, $flags=0)

2008-06-30T12:51:57Z

setLocalKey/setRemoteKey

← Older revision		Revision as of 12:51, 30 June 2008
Line 5:		Line 5:
	* $destination The node we have a relationship with.		* $destination The node we have a relationship with.

			If you do not want to use the default primary keys (for example when the * side has a combined PK), you can override them by using the functions:
			setLocalKey("a_id");
			setRemoteKey("b_id");

	'''Example'''		'''Example'''

2006-12-28T10:08:33Z

← Older revision		Revision as of 10:08, 28 December 2006
Line 1:		Line 1:
	~~#REDIRECT~~ [[~~ATK_Relations#atkManyToOneRelation~~]]		== atkManyToOneRelation ==
			function atkManyToOneRelation($name, $destination, $flags=0)

			* $name The name of the attribute.
			* $destination The node we have a relationship with.


			'''Example'''

			Projects all have one coordinator (node B), but one coordinator can have multiple projects (node A). So in the project class, there's a atkManyToOneRelation to a coordinator.

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

			[[Category:Relations]]

2006-12-28T01:57:57Z

New page

#REDIRECT [[ATK_Relations#atkManyToOneRelation]]