<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Private vs Public Global Variables</title>
	<atom:link href="http://database-geek.com/2009/04/01/private-vs-public-global-variables/feed/" rel="self" type="application/rss+xml" />
	<link>http://database-geek.com/2009/04/01/private-vs-public-global-variables/</link>
	<description>Database Stuff, from a Geek</description>
	<lastBuildDate>Tue, 15 Feb 2011 16:33:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: JT</title>
		<link>http://database-geek.com/2009/04/01/private-vs-public-global-variables/comment-page-1/#comment-177</link>
		<dc:creator>JT</dc:creator>
		<pubDate>Wed, 01 Apr 2009 17:36:03 +0000</pubDate>
		<guid isPermaLink="false">http://database-geek.com/2009/04/01/private-vs-public-global-variables/#comment-177</guid>
		<description>Good post Lewis.  I generally try to avoid globals.  Usually, nothing but headaches later.
I&#039;m pretty sure having them in the spec will lead to &quot;&lt;code&gt;ORA-04068: existing state of packages has been discarded&lt;/code&gt;&quot; errors for any active session.  Which is not a good thing in a HA environment.
Another exposure is the controlling process changing the value of the global. Meaning between calls to the package the calling program could change the value of the global.
If memory serves me right, both are due to the package state living for the life of the session, not the transaction or call.
 
 </description>
		<content:encoded><![CDATA[<p>Good post Lewis.  I generally try to avoid globals.  Usually, nothing but headaches later.<br />
I&#8217;m pretty sure having them in the spec will lead to &#8220;<code>ORA-04068: existing state of packages has been discarded</code>&#8221; errors for any active session.  Which is not a good thing in a HA environment.<br />
Another exposure is the controlling process changing the value of the global. Meaning between calls to the package the calling program could change the value of the global.<br />
If memory serves me right, both are due to the package state living for the life of the session, not the transaction or call.<br />
 <br />
 </p>
]]></content:encoded>
	</item>
</channel>
</rss>

