Using the union methods in database queries - Revision history

Cmb: Replace deprecated 'source' tags with 'syntaxhighlight' tags.

2022-08-26T15:00:11Z

Replace deprecated 'source' tags with 'syntaxhighlight' tags.

← Older revision		Revision as of 15:00, 26 August 2022
Line 42:		Line 42:
	</translate>		</translate>

	<~~source~~ lang="php">		<syntaxhighlight lang="php">
	$query		$query
	->select('name, email')		->select('name, email')
Line 48:		Line 48:
	;		;
	$mailshot = $db->setQuery($query)->loadObjectList();		$mailshot = $db->setQuery($query)->loadObjectList();
	</~~source~~>		</syntaxhighlight>

	<translate>		<translate>
Line 55:		Line 55:
	</translate>		</translate>

	<~~source~~ lang="php">		<syntaxhighlight lang="php">
	$query		$query
	->select('name, email')		->select('name, email')
Line 61:		Line 61:
	;		;
	$mailshot = $db->setQuery($query)->loadObjectList();		$mailshot = $db->setQuery($query)->loadObjectList();
	</~~source~~>		</syntaxhighlight>

	<translate>		<translate>
Line 68:		Line 68:
	</translate>		</translate>

	<~~source~~ lang="php">		<syntaxhighlight lang="php">
	$query		$query
	->select('name, email')		->select('name, email')
Line 75:		Line 75:
	;		;
	$mailshot = $db->setQuery($query)->loadObjectList();		$mailshot = $db->setQuery($query)->loadObjectList();
	</~~source~~>		</syntaxhighlight>

	<translate>		<translate>
Line 91:		Line 91:
	</translate>		</translate>

	<~~source~~ lang="php">		<syntaxhighlight lang="php">
	$q1->select('name, email')->from('customers');		$q1->select('name, email')->from('customers');
	$q2->select('name, email')->from('suppliers');		$q2->select('name, email')->from('suppliers');
	$q3->select('name, email')->from('shareholders');		$q3->select('name, email')->from('shareholders');
	</~~source~~>		</syntaxhighlight>

	<translate>		<translate>
Line 102:		Line 102:
	</translate>		</translate>

	<~~source~~ lang="php">		<syntaxhighlight lang="php">
	// The union method can be chained.		// The union method can be chained.
	$q1->union($q2)->union($q3);		$q1->union($q2)->union($q3);
Line 114:		Line 114:
	// It doesn't matter which query object is at the "root" of the query. In this case the actual query that is produced will be different but the result set will be the same.		// It doesn't matter which query object is at the "root" of the query. In this case the actual query that is produced will be different but the result set will be the same.
	$q2->union(array($q1, $q3));		$q2->union(array($q1, $q3));
	</~~source~~>		</syntaxhighlight>

	<translate>		<translate>
Line 146:		Line 146:
	</translate>		</translate>

	<~~source~~ lang="php">		<syntaxhighlight lang="php">
	$query		$query
	->select('*')		->select('*')
Line 154:		Line 154:
	;		;
	$products = $db->setQuery($query)->loadObjectList();		$products = $db->setQuery($query)->loadObjectList();
	</~~source~~>		</syntaxhighlight>

	<translate>		<translate>
Line 161:		Line 161:
	</translate>		</translate>

	<~~source~~ lang="php">		<syntaxhighlight lang="php">
	$query		$query
	->select('*')		->select('*')
Line 174:		Line 174:
	$query->union($q2);		$query->union($q2);
	$products = $db->setQuery($query)->loadObjectList();		$products = $db->setQuery($query)->loadObjectList();
	</~~source~~>		</syntaxhighlight>

	<translate>		<translate>
Line 196:		Line 196:
	</translate>		</translate>

	<~~source~~ lang="php">		<syntaxhighlight lang="php">
	$q2		$q2
	->select('name , email')		->select('name , email')
Line 208:		Line 208:
	;		;
	$mailshot = $db->setQuery($query)->loadObjectList();		$mailshot = $db->setQuery($query)->loadObjectList();
	</~~source~~>		</syntaxhighlight>

	<translate>		<translate>
Line 215:		Line 215:
	</translate>		</translate>

	<~~source~~ lang="php">		<syntaxhighlight lang="php">
	$q2		$q2
	->select('name , email')		->select('name , email')
Line 228:		Line 228:
	;		;
	$mailshot = $db->setQuery($query)->loadObjectList();		$mailshot = $db->setQuery($query)->loadObjectList();
	</~~source~~>		</syntaxhighlight>

	<translate>		<translate>
Line 240:		Line 240:
	</translate>		</translate>

	<~~source~~ lang="php">		<syntaxhighlight lang="php">
	$q2		$q2
	->select('name , email, 1 as sort_col')		->select('name , email, 1 as sort_col')
Line 252:		Line 252:
	;		;
	$mailshot = $db->setQuery($query)->loadObjectList();		$mailshot = $db->setQuery($query)->loadObjectList();
	</~~source~~>		</syntaxhighlight>

	<translate>==Advanced ordering== <!--T:33--></translate>		<translate>==Advanced ordering== <!--T:33--></translate>
Line 261:		Line 261:
	</translate>		</translate>

	<~~source~~ lang="php">		<syntaxhighlight lang="php">
	$q2		$q2
	->select('name , email, 1 as sort_col')		->select('name , email, 1 as sort_col')
Line 283:		Line 283:
	;		;
	$mailshot = $db->setQuery($query)->loadObjectList();		$mailshot = $db->setQuery($query)->loadObjectList();
	</~~source~~>		</syntaxhighlight>

	<translate>		<translate>
Line 291:		Line 291:

	<translate><!--T:37-->		<translate><!--T:37-->
	If you're experiencing errors reproducing this example, check the issue and related patch: [https://issues.joomla.org/tracker/joomla-cms/4127 4127]</translate>		If you're experiencing errors reproducing this example, check the issue and related patch: [https://issues.joomla.org/tracker/joomla-cms/4127 4127]</translate>

	<translate>		<translate>

MATsxm: Marked this version for translation

2016-09-25T17:49:26Z

Marked this version for translation

← Older revision		Revision as of 17:49, 25 September 2016
Line 290:		Line 290:
	</translate>		</translate>

	<translate>If you're experiencing errors reproducing this example, check the issue and related patch: [https://issues.joomla.org/tracker/joomla-cms/4127 4127]</translate>		<translate><!--T:37-->
			If you're experiencing errors reproducing this example, check the issue and related patch: [https://issues.joomla.org/tracker/joomla-cms/4127 4127]</translate>

	<translate>		<translate>

MATsxm at 17:49, 25 September 2016

2016-09-25T17:49:11Z

← Older revision		Revision as of 17:49, 25 September 2016
Line 289:		Line 289:
	It's necessary to use a dummy query in this case because otherwise the <tt>order</tt> and <tt>setLimit</tt> methods would be applied to the final result set rather that the individual one.		It's necessary to use a dummy query in this case because otherwise the <tt>order</tt> and <tt>setLimit</tt> methods would be applied to the final result set rather that the individual one.
	</translate>		</translate>

			<translate>If you're experiencing errors reproducing this example, check the issue and related patch: [https://issues.joomla.org/tracker/joomla-cms/4127 4127]</translate>

	<translate>		<translate>

MATsxm: Reverted edits by Bicudomaschio (talk) to last revision by Abulafia

2016-09-25T17:42:58Z

Reverted edits by Bicudomaschio (talk) to last revision by Abulafia

← Older revision		Revision as of 17:42, 25 September 2016
Line 288:		Line 288:
	<!--T:35-->		<!--T:35-->
	It's necessary to use a dummy query in this case because otherwise the <tt>order</tt> and <tt>setLimit</tt> methods would be applied to the final result set rather that the individual one.		It's necessary to use a dummy query in this case because otherwise the <tt>order</tt> and <tt>setLimit</tt> methods would be applied to the final result set rather that the individual one.
	~~If you experience errors reproducing this example, check if a patch is necessary: ticket tracker 4127~~
	</translate>		</translate>

Bicudomaschio at 17:40, 25 September 2016

2016-09-25T17:40:29Z

← Older revision		Revision as of 17:40, 25 September 2016
Line 288:		Line 288:
	<!--T:35-->		<!--T:35-->
	It's necessary to use a dummy query in this case because otherwise the <tt>order</tt> and <tt>setLimit</tt> methods would be applied to the final result set rather that the individual one.		It's necessary to use a dummy query in this case because otherwise the <tt>order</tt> and <tt>setLimit</tt> methods would be applied to the final result set rather that the individual one.
			If you experience errors reproducing this example, check if a patch is necessary: ticket tracker 4127
	</translate>		</translate>

Abulafia at 19:10, 25 September 2015

2015-09-25T19:10:12Z

← Older revision		Revision as of 19:10, 25 September 2015
Line 10:		Line 10:
	\| image = content		\| image = content
	\| text = <translate><!--T:2-->		\| text = <translate><!--T:2-->
	'''Although the union methods are present in Joomla! 2.5 and 3.x, they ''do not work'' in any release prior to 3.3.</translate>}}		'''Although the union methods are present in Joomla! 2.5 and 3.x, they ''do not work'' in any release prior to 3.3.'''</translate>}}

	<translate>		<translate>

MATsxm: agree or disagree... "!" added to Joomla! the way it should be :D

2015-04-09T14:22:24Z

agree or disagree... "!" added to Joomla! the way it should be :D

← Older revision		Revision as of 14:22, 9 April 2015
Line 7:		Line 7:
	\| type = serious		\| type = serious
	\| title = <translate><!--T:1-->		\| title = <translate><!--T:1-->
	This page covers Joomla 3.3 or later only</translate>		This page covers Joomla! 3.3 or later only.</translate>
	\| image = content		\| image = content
	\| text = <translate><!--T:2-->		\| text = <translate><!--T:2-->
	'''Although the union methods are present in Joomla 2.5 and 3.x, they ''do not work'' in any release prior to 3.3.</translate>}}		'''Although the union methods are present in Joomla! 2.5 and 3.x, they ''do not work'' in any release prior to 3.3.</translate>}}

	<translate>		<translate>
Line 79:		Line 79:
	<translate>		<translate>
	<!--T:12-->		<!--T:12-->
	The result set obtained from the union query will actually be a little different from running the individual queries separately because the union query will automatically eliminate duplicates. If you don't mind that the result set may contain duplicates (which mathematically speaking means it isn't a set) then using <tt>unionAll</tt> instead of <tt>union</tt> will improve performance.		The result set obtained from the union query will actually be a little different from running the individual queries separately because the union query will automatically eliminate duplicates. If you don't mind that the result set may contain duplicates (which mathematically speaking means it isn't a set), then using <tt>unionAll</tt> instead of <tt>union</tt> will improve performance.
	</translate>		</translate>