<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>SQL::newQuery()</title>
	<atom:link href="http://sqlnewquery.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://sqlnewquery.com</link>
	<description>An SQL Query Builder Project</description>
	<lastBuildDate>Tue, 22 Feb 2011 18:34:58 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.3</generator>
		<item>
		<title>A Chaining Breakthrough!</title>
		<link>http://sqlnewquery.com/2011/02/a-chaining-breakthrough/</link>
		<comments>http://sqlnewquery.com/2011/02/a-chaining-breakthrough/#comments</comments>
		<pubDate>Tue, 22 Feb 2011 18:34:58 +0000</pubDate>
		<dc:creator>Tom Spizuoco</dc:creator>
				<category><![CDATA[Composing A Statement]]></category>
		<category><![CDATA[Thought Process]]></category>

		<guid isPermaLink="false">http://sqlnewquery.com/?p=152</guid>
		<description><![CDATA[To further steal the great foundation of jQuery method chaining, I have realized a way to use a &#8220;back&#8221; function that will regress backward through the chained functions and return the last object that was manipulated. Wow, that makes it sound confusing but it is not. Imagine the following chained code. $objSelect-&#62;addTable('table'); Previously this would [...]]]></description>
		<wfw:commentRss>http://sqlnewquery.com/2011/02/a-chaining-breakthrough/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>My First Statement</title>
		<link>http://sqlnewquery.com/2011/02/my-first-statement/</link>
		<comments>http://sqlnewquery.com/2011/02/my-first-statement/#comments</comments>
		<pubDate>Fri, 18 Feb 2011 17:44:02 +0000</pubDate>
		<dc:creator>Tom Spizuoco</dc:creator>
				<category><![CDATA[Composing A Statement]]></category>
		<category><![CDATA[Thought Process]]></category>

		<guid isPermaLink="false">http://sqlnewquery.com/?p=146</guid>
		<description><![CDATA[Well I have managed to create a simple SELECT statement. It is cumbersome at best and follows along the process flow introduced in the last post, &#8220;Select Statement&#8220;. I show this only to demonstrate the foundation of how the statement is ultimately put together. You will notice that each class is initiated using a &#8220;create&#8221; [...]]]></description>
		<wfw:commentRss>http://sqlnewquery.com/2011/02/my-first-statement/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SELECT Statement</title>
		<link>http://sqlnewquery.com/2011/01/select-statement/</link>
		<comments>http://sqlnewquery.com/2011/01/select-statement/#comments</comments>
		<pubDate>Fri, 28 Jan 2011 17:34:30 +0000</pubDate>
		<dc:creator>Tom Spizuoco</dc:creator>
				<category><![CDATA[Composing A Statement]]></category>
		<category><![CDATA[Thought Process]]></category>

		<guid isPermaLink="false">http://sqlnewquery.com/?p=137</guid>
		<description><![CDATA[Let us break down the simplest of statements, the SELECT statement. I will try to walk through the process of creating the following: &#8220;SELECT column FROM table WHERE column = value;&#8221;.  This will be the &#8220;long&#8221; way of doing it, by explicitly creating each instance of the statement components. In the end, I wish to [...]]]></description>
		<wfw:commentRss>http://sqlnewquery.com/2011/01/select-statement/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Statement Types</title>
		<link>http://sqlnewquery.com/2011/01/statement-types/</link>
		<comments>http://sqlnewquery.com/2011/01/statement-types/#comments</comments>
		<pubDate>Fri, 28 Jan 2011 17:15:23 +0000</pubDate>
		<dc:creator>Tom Spizuoco</dc:creator>
				<category><![CDATA[Composing A Statement]]></category>
		<category><![CDATA[Thought Process]]></category>

		<guid isPermaLink="false">http://sqlnewquery.com/?p=130</guid>
		<description><![CDATA[I can now determine each SQL statement type that I want to build. Each type will be represented by a class, each extending the abstract sqlStatement class. These classes will be made up of multiple instances of sqlRelationship and sqlComponent classes. The statement classes will verify each object passed to determine if it &#8220;fits&#8221; within [...]]]></description>
		<wfw:commentRss>http://sqlnewquery.com/2011/01/statement-types/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Order/Group/Having Clauses</title>
		<link>http://sqlnewquery.com/2011/01/ordergrouphaving-clauses/</link>
		<comments>http://sqlnewquery.com/2011/01/ordergrouphaving-clauses/#comments</comments>
		<pubDate>Tue, 11 Jan 2011 20:56:29 +0000</pubDate>
		<dc:creator>Tom Spizuoco</dc:creator>
				<category><![CDATA[Breaking Down The Statement]]></category>
		<category><![CDATA[Thought Process]]></category>

		<guid isPermaLink="false">http://sqlnewquery.com/?p=119</guid>
		<description><![CDATA[There are a few last minute clauses to an SQL statement that I need to address. The HAVING clause is fairly straight forward. I requires a WHERE condition, so that is what I will use. Any statement class that can take a HAVING clause will accept an sqlConditionGroup as an argument as long as it [...]]]></description>
		<wfw:commentRss>http://sqlnewquery.com/2011/01/ordergrouphaving-clauses/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Condition Groups</title>
		<link>http://sqlnewquery.com/2011/01/condition-groups/</link>
		<comments>http://sqlnewquery.com/2011/01/condition-groups/#comments</comments>
		<pubDate>Wed, 05 Jan 2011 22:36:56 +0000</pubDate>
		<dc:creator>Tom Spizuoco</dc:creator>
				<category><![CDATA[Breaking Down The Statement]]></category>
		<category><![CDATA[Thought Process]]></category>

		<guid isPermaLink="false">http://sqlnewquery.com/?p=100</guid>
		<description><![CDATA[So I have five sqlRelationship classes that can be passed to the SQL statement class. (not discussed yet) The SELECT expressions, SET expressions, and table references can all be stored as arrays within the SQL  statement class. However, because any WHERE/ON condition can be a complex AND or OR expression, and that they can be [...]]]></description>
		<wfw:commentRss>http://sqlnewquery.com/2011/01/condition-groups/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Relationship Components</title>
		<link>http://sqlnewquery.com/2011/01/relationship-components/</link>
		<comments>http://sqlnewquery.com/2011/01/relationship-components/#comments</comments>
		<pubDate>Sat, 01 Jan 2011 17:30:27 +0000</pubDate>
		<dc:creator>Tom Spizuoco</dc:creator>
				<category><![CDATA[Breaking Down The Statement]]></category>
		<category><![CDATA[Thought Process]]></category>

		<guid isPermaLink="false">http://sqlnewquery.com/?p=90</guid>
		<description><![CDATA[Much of the arguments passed to any of the sqlRelationship objects will be strings. However, upon my initial analysis, there are a couple of potential arguments that may benefit from an encapsulation into a class. This will help not only with conversion of these arguments to strings for inclusion into the SQL statement, but for [...]]]></description>
		<wfw:commentRss>http://sqlnewquery.com/2011/01/relationship-components/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Last Relationship, I Think</title>
		<link>http://sqlnewquery.com/2010/12/the-last-relationship-i-think/</link>
		<comments>http://sqlnewquery.com/2010/12/the-last-relationship-i-think/#comments</comments>
		<pubDate>Wed, 22 Dec 2010 21:54:25 +0000</pubDate>
		<dc:creator>Tom Spizuoco</dc:creator>
				<category><![CDATA[Breaking Down The Statement]]></category>
		<category><![CDATA[Thought Process]]></category>

		<guid isPermaLink="false">http://sqlnewquery.com/?p=71</guid>
		<description><![CDATA[There is one last statement clause that need to determine if I can fit the pieces into my &#8220;relationship&#8221; idea. That clause is the table reference. Each table reference will be a single relationship. Of course, a simple table reference will only be a name, no value or operator needed. Any JOIN table will need [...]]]></description>
		<wfw:commentRss>http://sqlnewquery.com/2010/12/the-last-relationship-i-think/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Expanding the Relationship Theory</title>
		<link>http://sqlnewquery.com/2010/12/expanding-the-condition-theory/</link>
		<comments>http://sqlnewquery.com/2010/12/expanding-the-condition-theory/#comments</comments>
		<pubDate>Wed, 15 Dec 2010 20:27:39 +0000</pubDate>
		<dc:creator>Tom Spizuoco</dc:creator>
				<category><![CDATA[Breaking Down The Statement]]></category>
		<category><![CDATA[Thought Process]]></category>

		<guid isPermaLink="false">http://sqlnewquery.com/?p=31</guid>
		<description><![CDATA[Lets continue to fit the SQL relationship theory into basic SQL statement syntax. You may recall, a statement &#8220;relationship&#8221;, as defined by myself, is a name/value pair used to create the building blocks of a complete SQL statement. The next step is to analyze the name/value pairs that make up the SET/VALUES expressions used within [...]]]></description>
		<wfw:commentRss>http://sqlnewquery.com/2010/12/expanding-the-condition-theory/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Relationships</title>
		<link>http://sqlnewquery.com/2010/12/statement-conditions/</link>
		<comments>http://sqlnewquery.com/2010/12/statement-conditions/#comments</comments>
		<pubDate>Mon, 13 Dec 2010 23:29:01 +0000</pubDate>
		<dc:creator>Tom Spizuoco</dc:creator>
				<category><![CDATA[Breaking Down The Statement]]></category>
		<category><![CDATA[Thought Process]]></category>
		<category><![CDATA[condition]]></category>
		<category><![CDATA[expression]]></category>
		<category><![CDATA[function]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[query]]></category>
		<category><![CDATA[statement]]></category>
		<category><![CDATA[subselect]]></category>

		<guid isPermaLink="false">http://sqlnewquery.com/?p=19</guid>
		<description><![CDATA[My initial thought was to break down an SQL statement into pieces. Seems like a fairly obvious idea so I am inclined to go with it. Let us assume these basic pieces: Statement Type, SELECT expression, FROM table references, JOIN clauses, INSERT/REPLACE/UPDATE values, WHERE clauses, and lastly and ORDER/GROUP/HAVING type clause. I think, and I [...]]]></description>
		<wfw:commentRss>http://sqlnewquery.com/2010/12/statement-conditions/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

