<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Storing the SQL queries in the database</title>
	<atom:link href="http://blog.forret.com/2006/03/storing-the-sql-queries-in-the-database/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.forret.com/2006/03/storing-the-sql-queries-in-the-database/</link>
	<description>and I mean it</description>
	<pubDate>Sun, 23 Nov 2008 14:33:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Abhishek</title>
		<link>http://blog.forret.com/2006/03/storing-the-sql-queries-in-the-database/#comment-180340</link>
		<dc:creator>Abhishek</dc:creator>
		<pubDate>Tue, 27 Nov 2007 20:49:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.forret.com/2006/03/storing-the-sql-queries-in-the-database/#comment-180340</guid>
		<description>Hi,

How can i put substitution varable into the Access Database sql query, It will ask user to give the prompt answer</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>How can i put substitution varable into the Access Database sql query, It will ask user to give the prompt answer</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://blog.forret.com/2006/03/storing-the-sql-queries-in-the-database/#comment-576</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Sun, 02 Apr 2006 14:22:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.forret.com/2006/03/storing-the-sql-queries-in-the-database/#comment-576</guid>
		<description>Good question.
If one were to start using stored procedures, and then add logical naming of the procedures, add web-based editing with versioning, add a mechanism for passing a variable number of parameters and encapsulate everything in a piece of code, one would probably arrive at something quite similar.
My system would work with a sissy database like Access, but once you have a more mature RDBMS (SQL-Server, mySQL, Oracle, Postgres), using stored procedures to implement it is obviously a best practice. But it's more than just that.</description>
		<content:encoded><![CDATA[<p>Good question.<br />
If one were to start using stored procedures, and then add logical naming of the procedures, add web-based editing with versioning, add a mechanism for passing a variable number of parameters and encapsulate everything in a piece of code, one would probably arrive at something quite similar.<br />
My system would work with a sissy database like Access, but once you have a more mature RDBMS (SQL-Server, mySQL, Oracle, Postgres), using stored procedures to implement it is obviously a best practice. But it&#8217;s more than just that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LVB</title>
		<link>http://blog.forret.com/2006/03/storing-the-sql-queries-in-the-database/#comment-555</link>
		<dc:creator>LVB</dc:creator>
		<pubDate>Sat, 01 Apr 2006 18:03:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.forret.com/2006/03/storing-the-sql-queries-in-the-database/#comment-555</guid>
		<description>What's the essential difference between your idea and stored procedures? I mean, which of your 5 advantages cannot be obtained by applying the standard stored procedures approach?</description>
		<content:encoded><![CDATA[<p>What&#8217;s the essential difference between your idea and stored procedures? I mean, which of your 5 advantages cannot be obtained by applying the standard stored procedures approach?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.390 seconds -->
