<?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>Prepared Statements &#8211; Database Research &amp; Development</title>
	<atom:link href="https://www.dbrnd.com/tag/prepared-statements/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.dbrnd.com</link>
	<description>BIGData &#124; NoSQL &#124; MSSQL &#124; MySQL &#124; PostgreSQL</description>
	<lastBuildDate>Mon, 28 Nov 2016 17:04:32 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.6</generator>
	<item>
		<title>PostgreSQL: Create Prepared Statement, to increase Session Performance</title>
		<link>https://www.dbrnd.com/2016/11/postgresql-create-prepared-statement-to-increase-session-performance-prevent-sql-injection/</link>
					<comments>https://www.dbrnd.com/2016/11/postgresql-create-prepared-statement-to-increase-session-performance-prevent-sql-injection/#comments</comments>
		
		<dc:creator><![CDATA[Anvesh Patel]]></dc:creator>
		<pubDate>Sun, 27 Nov 2016 17:04:08 +0000</pubDate>
				<category><![CDATA[PostgreSQL]]></category>
		<category><![CDATA[Anvesh Patel]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[database research and development]]></category>
		<category><![CDATA[dbrnd]]></category>
		<category><![CDATA[Parameterized Statements]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[plpgsql]]></category>
		<category><![CDATA[Postgres Query]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[PostgreSQL Administrator]]></category>
		<category><![CDATA[PostgreSQL Error]]></category>
		<category><![CDATA[PostgreSQL Programming]]></category>
		<category><![CDATA[PostgreSQL Tips and Tricks]]></category>
		<category><![CDATA[PREPARE]]></category>
		<category><![CDATA[Prepared Statements]]></category>
		<category><![CDATA[Session]]></category>
		<category><![CDATA[SQL Injection]]></category>
		<guid isPermaLink="false">https://www.dbrnd.com/?p=3933</guid>

					<description><![CDATA[The PostgreSQL Prepared Statement or Parameterized Statements are always good for specific purpose like: can create Prepared Statement for frequently executing query of a session, It also prevents from SQL Injections. Prepared Statements are faster for a particular session because It does not require parsing and compiling for each execution. It is only session specific [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><a class="a2a_button_facebook" href="https://www.addtoany.com/add_to/facebook?linkurl=https%3A%2F%2Fwww.dbrnd.com%2F2016%2F11%2Fpostgresql-create-prepared-statement-to-increase-session-performance-prevent-sql-injection%2F&amp;linkname=PostgreSQL%3A%20Create%20Prepared%20Statement%2C%20to%20increase%20Session%20Performance" title="Facebook" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_twitter" href="https://www.addtoany.com/add_to/twitter?linkurl=https%3A%2F%2Fwww.dbrnd.com%2F2016%2F11%2Fpostgresql-create-prepared-statement-to-increase-session-performance-prevent-sql-injection%2F&amp;linkname=PostgreSQL%3A%20Create%20Prepared%20Statement%2C%20to%20increase%20Session%20Performance" title="Twitter" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_linkedin" href="https://www.addtoany.com/add_to/linkedin?linkurl=https%3A%2F%2Fwww.dbrnd.com%2F2016%2F11%2Fpostgresql-create-prepared-statement-to-increase-session-performance-prevent-sql-injection%2F&amp;linkname=PostgreSQL%3A%20Create%20Prepared%20Statement%2C%20to%20increase%20Session%20Performance" title="LinkedIn" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_pinterest" href="https://www.addtoany.com/add_to/pinterest?linkurl=https%3A%2F%2Fwww.dbrnd.com%2F2016%2F11%2Fpostgresql-create-prepared-statement-to-increase-session-performance-prevent-sql-injection%2F&amp;linkname=PostgreSQL%3A%20Create%20Prepared%20Statement%2C%20to%20increase%20Session%20Performance" title="Pinterest" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_reddit" href="https://www.addtoany.com/add_to/reddit?linkurl=https%3A%2F%2Fwww.dbrnd.com%2F2016%2F11%2Fpostgresql-create-prepared-statement-to-increase-session-performance-prevent-sql-injection%2F&amp;linkname=PostgreSQL%3A%20Create%20Prepared%20Statement%2C%20to%20increase%20Session%20Performance" title="Reddit" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_pocket" href="https://www.addtoany.com/add_to/pocket?linkurl=https%3A%2F%2Fwww.dbrnd.com%2F2016%2F11%2Fpostgresql-create-prepared-statement-to-increase-session-performance-prevent-sql-injection%2F&amp;linkname=PostgreSQL%3A%20Create%20Prepared%20Statement%2C%20to%20increase%20Session%20Performance" title="Pocket" rel="nofollow noopener" target="_blank"></a><a class="a2a_dd addtoany_share_save addtoany_share" href="https://www.addtoany.com/share#url=https%3A%2F%2Fwww.dbrnd.com%2F2016%2F11%2Fpostgresql-create-prepared-statement-to-increase-session-performance-prevent-sql-injection%2F&#038;title=PostgreSQL%3A%20Create%20Prepared%20Statement%2C%20to%20increase%20Session%20Performance" data-a2a-url="https://www.dbrnd.com/2016/11/postgresql-create-prepared-statement-to-increase-session-performance-prevent-sql-injection/" data-a2a-title="PostgreSQL: Create Prepared Statement, to increase Session Performance"></a></p><p>The PostgreSQL Prepared Statement or Parameterized Statements are always good for specific purpose like: can create Prepared Statement for frequently executing query of a session, It also prevents from SQL Injections. </p>
<blockquote><p>Prepared Statements are faster for a particular session because It does not require parsing and compiling for each execution. It is only session specific and once a session kill, Prepared Statements automatically destroy. </p></blockquote>
<p>Here, You can access more on Prepared Statements. </p>
<blockquote class="wp-embedded-content" data-secret="XqVzPdXZbn"><p><a href="https://www.dbrnd.com/2015/08/prepared-or-parameterized-statements-in-database-system/">Prepared or Parameterized Statements in Database System</a></p></blockquote>
<p><iframe class="wp-embedded-content" sandbox="allow-scripts" security="restricted"  src="https://www.dbrnd.com/2015/08/prepared-or-parameterized-statements-in-database-system/embed/#?secret=XqVzPdXZbn" data-secret="XqVzPdXZbn" width="600" height="338" title="&#8220;Prepared or Parameterized Statements in Database System&#8221; &#8212; Database Research &amp; Development" frameborder="0" marginwidth="0" marginheight="0" scrolling="no"></iframe></p>
<p><strong>Small demonstration of PostgreSQL Prepared Statement:</strong></p>
<p><strong>Create a table with sample records:</strong></p>
<pre class="crayon-plain-tag">CREATE TABLE tbl_Students 
(
	StudID INTEGER PRIMARY KEY
	,StudName CHARACTER VARYING
	,StudClass CHAR(1)	
);

INSERT INTO tbl_Students 
VALUES (1,'Anvesh','A')
,(2,'Neevan','B'),(3,'Jenny','C')
,(4,'Roy','C'),(5,'Martin','C');</pre> </p>
<p><strong>Create a Prepared Statement to SELECT Students data:</strong></p>
<pre class="crayon-plain-tag">PREPARE pre_GetStudents (INT) AS 
SELECT *FROM tbl_Students WHERE StudID = $1;</pre> </p>
<p><strong>Execute a Prepared Statement:</strong></p>
<pre class="crayon-plain-tag">EXECUTE pre_GetStudents(2);</pre> </p>
<p><strong>System view to check the Prepare statements of session:</strong></p>
<pre class="crayon-plain-tag">SELECT *FROM pg_prepared_statements;</pre> </p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.dbrnd.com/2016/11/postgresql-create-prepared-statement-to-increase-session-performance-prevent-sql-injection/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
	</channel>
</rss>
