<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[PunBB Forums — SQL queries issue (WHERE id= vs WHERE t.id=)]]></title>
		<link>https://punbb.informer.com/forums/topic/29517/sql-queries-issue-where-id-vs-where-tid/</link>
		<atom:link href="https://punbb.informer.com/forums/feed/rss/topic/29517/" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in SQL queries issue (WHERE id= vs WHERE t.id=).]]></description>
		<lastBuildDate>Fri, 17 Jul 2015 22:18:30 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[SQL queries issue (WHERE id= vs WHERE t.id=)]]></title>
			<link>https://punbb.informer.com/forums/post/154820/#p154820</link>
			<description><![CDATA[<p>Table names in FROMs and JOINs are aliased with &quot;AS&quot; statement in all the queries.<br />On the other hand, in WHEREs we have a plenty of unaliased clauses like id=some_condition (vs t.id=some_condition, where t is a table alias).</p><p>The problem is in high probability of column name indetermination when we trying to patch the query with a hook to join some extra tables. As a result we have a broken query to &quot;debug&quot;.</p><p>Of cause we can &quot;rewrite&quot; the WHERE statement with aliased conditions in the same hook or patch the php code in place. But i think it&#039;s better to get all of WHEREs aliased out of the box.</p>]]></description>
			<author><![CDATA[null@example.com (normalize.pro)]]></author>
			<pubDate>Fri, 17 Jul 2015 22:18:30 +0000</pubDate>
			<guid>https://punbb.informer.com/forums/post/154820/#p154820</guid>
		</item>
	</channel>
</rss>
