<?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>Inside Oracle APEX by Patrick Wolf &#187; Caution</title>
	<atom:link href="http://www.inside-oracle-apex.com/category/oracle-apex/apex-caution/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.inside-oracle-apex.com</link>
	<description>Inside Oracle APEX - a blog that helps to get more out of Oracle Application Express (APEX) for your daily development work!</description>
	<lastBuildDate>Wed, 11 May 2011 09:08:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Caution with new &#8220;Runtime Where Clause&#8221; in Oracle APEX 3.1</title>
		<link>http://www.inside-oracle-apex.com/caution-with-new-runtime-where-clause-in-oracle-apex-31/</link>
		<comments>http://www.inside-oracle-apex.com/caution-with-new-runtime-where-clause-in-oracle-apex-31/#comments</comments>
		<pubDate>Thu, 22 May 2008 10:51:00 +0000</pubDate>
		<dc:creator>Patrick Wolf</dc:creator>
				<category><![CDATA[Bugs]]></category>
		<category><![CDATA[Caution]]></category>

		<guid isPermaLink="false">http://final.inside-oracle-apex.com/en/post/caution-with-new-runtime-where-clause-in-oracle-apex-31/</guid>
		<description><![CDATA[Found out the hard way that the new property &#8220;Runtime Where Clause&#8221; for processes (eg. Fetch, DML) has a serious bug. The value of the property gets exported and is contained in the export file of an application, but it isn&#8217;t set when you import an application!!! Because most of us are not developing on [...]]]></description>
		<wfw:commentRss>http://www.inside-oracle-apex.com/caution-with-new-runtime-where-clause-in-oracle-apex-31/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Caution: Apex_Item.Date_Popup and Oracle APEX 3.1</title>
		<link>http://www.inside-oracle-apex.com/caution-apex_itemdate_popup-and-oracle-apex-31-2/</link>
		<comments>http://www.inside-oracle-apex.com/caution-apex_itemdate_popup-and-oracle-apex-31-2/#comments</comments>
		<pubDate>Tue, 25 Mar 2008 21:55:54 +0000</pubDate>
		<dc:creator>Patrick Wolf</dc:creator>
				<category><![CDATA[Caution]]></category>

		<guid isPermaLink="false">http://final.inside-oracle-apex.com/en/post/caution-apex_itemdate_popup-and-oracle-apex-31/</guid>
		<description><![CDATA[Just to let you know in case you are hitting the following problem or plan to upgrade to 3.1. The version of Apex_Item.Date_Popup which comes with Oracle APEX 3.1.0.00.32 has a &#8220;small&#8221; bug. The Date Picker will always write the return value into the first row, independent for which row you have opened the Date [...]]]></description>
		<wfw:commentRss>http://www.inside-oracle-apex.com/caution-apex_itemdate_popup-and-oracle-apex-31-2/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Attention! Are you using the Drop in replacement for V and NV function?</title>
		<link>http://www.inside-oracle-apex.com/attention-are-you-using-drop-in-replacement-for-v-and-nv-function-2/</link>
		<comments>http://www.inside-oracle-apex.com/attention-are-you-using-drop-in-replacement-for-v-and-nv-function-2/#comments</comments>
		<pubDate>Wed, 12 Mar 2008 18:28:49 +0000</pubDate>
		<dc:creator>Patrick Wolf</dc:creator>
				<category><![CDATA[ApexLib]]></category>
		<category><![CDATA[Caution]]></category>

		<guid isPermaLink="false">http://final.inside-oracle-apex.com/en/post/attention-are-you-using-the-drop-in-replacement-for-v-and-nv-function/</guid>
		<description><![CDATA[If you are using my Drop in replacement for V and NV function and you are upgrading to Oracle APEX 3.1 then you have to alter the functions to reference the new schema FLOWS_030100!!! If you are not doing this your applications will not work because the functions are trying to read the session state [...]]]></description>
		<wfw:commentRss>http://www.inside-oracle-apex.com/attention-are-you-using-drop-in-replacement-for-v-and-nv-function-2/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Warning: DBMS_LDAP.simple_bind_s/ APEX_LDAP.authenticate and NULL password</title>
		<link>http://www.inside-oracle-apex.com/dbms_ldapsimple_bind_s-apex_ldapauthenticate-and-null-password/</link>
		<comments>http://www.inside-oracle-apex.com/dbms_ldapsimple_bind_s-apex_ldapauthenticate-and-null-password/#comments</comments>
		<pubDate>Thu, 10 Jan 2008 18:29:33 +0000</pubDate>
		<dc:creator>Patrick Wolf</dc:creator>
				<category><![CDATA[Caution]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[LDAP]]></category>
		<category><![CDATA[MS Active Directory]]></category>

		<guid isPermaLink="false">http://final.inside-oracle-apex.com/en/post/warning-dbms_ldapsimple_bind_sapex_ldapauthenticate-and-null-password/</guid>
		<description><![CDATA[Just came across a very strange behavior of the DBMS_LDAP.simple_bind_s and APEX_LDAP.authenticate procedure which I used to do a basic LDAP authentication against our MS Active Directory server. I used the following simple test code DECLARE vSession DBMS_LDAP.session; vResult PLS_INTEGER; BEGIN DBMS_LDAP.use_exception := TRUE; vSession := DBMS_LDAP.init ( hostname =&#62; 'your-active-directory-server' , portnum =&#62; 389 [...]]]></description>
		<wfw:commentRss>http://www.inside-oracle-apex.com/dbms_ldapsimple_bind_s-apex_ldapauthenticate-and-null-password/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>SQL embedded into PL/SQL</title>
		<link>http://www.inside-oracle-apex.com/sql-embedded-into-plsql/</link>
		<comments>http://www.inside-oracle-apex.com/sql-embedded-into-plsql/#comments</comments>
		<pubDate>Tue, 23 Oct 2007 20:12:00 +0000</pubDate>
		<dc:creator>Patrick Wolf</dc:creator>
				<category><![CDATA[Caution]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[PL/SQL]]></category>
		<category><![CDATA[SQL]]></category>

		<guid isPermaLink="false">http://www.inside-oracle-apex.com/en/?p=176</guid>
		<description><![CDATA[A few days ago I spoke with another developer about SQL embedded into PL/SQL code and how function calls are handled in the WHERE clause of SQL statements. There is sometimes confusion who (PL/SQL engine or SQL engine) is executing it, I thought it&#8217;s a good idea to write a posting about it. Last year [...]]]></description>
		<wfw:commentRss>http://www.inside-oracle-apex.com/sql-embedded-into-plsql/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Lock conflicts with Automatic Row Processing (DML)</title>
		<link>http://www.inside-oracle-apex.com/lock-conflicts-with-automatic-row-processing-dml/</link>
		<comments>http://www.inside-oracle-apex.com/lock-conflicts-with-automatic-row-processing-dml/#comments</comments>
		<pubDate>Wed, 02 May 2007 20:28:00 +0000</pubDate>
		<dc:creator>Patrick Wolf</dc:creator>
				<category><![CDATA[Caution]]></category>
		<category><![CDATA[locks]]></category>

		<guid isPermaLink="false">http://www.inside-oracle-apex.com/en/?p=116</guid>
		<description><![CDATA[Oracle APEX 3.0 contains a nice new feature you should be aware of. There is a new substitution variable APEX_DML_LOCK_WAIT_TIME which you can use to define how the behavior of the &#8220;Automatic Row Processing (DML)&#8221; and ApplyMRU/D processes should be in case if the processed row is locked. With the current setting APEX will wait [...]]]></description>
		<wfw:commentRss>http://www.inside-oracle-apex.com/lock-conflicts-with-automatic-row-processing-dml/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Slightly different behavior of $x in Oracle APEX 3.0</title>
		<link>http://www.inside-oracle-apex.com/slightly-different-behavior-of-x-in-oracle-apex-30/</link>
		<comments>http://www.inside-oracle-apex.com/slightly-different-behavior-of-x-in-oracle-apex-30/#comments</comments>
		<pubDate>Sun, 25 Mar 2007 11:10:00 +0000</pubDate>
		<dc:creator>Patrick Wolf</dc:creator>
				<category><![CDATA[Caution]]></category>
		<category><![CDATA[Javascript]]></category>

		<guid isPermaLink="false">http://www.inside-oracle-apex.com/en/?p=100</guid>
		<description><![CDATA[Just noticed a slightly different behavior of $x in Oracle APEX 3.0. Probably many of you just use it to pass the id-string of an element (eg. $x(&#8220;P4_TEST&#8221;)) to this function to get the object of this field/div/&#8230; id, but you can also call it with an object and in that case the function will [...]]]></description>
		<wfw:commentRss>http://www.inside-oracle-apex.com/slightly-different-behavior-of-x-in-oracle-apex-30/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Incomplete/Broken HTML output</title>
		<link>http://www.inside-oracle-apex.com/incompletebroken-html-output/</link>
		<comments>http://www.inside-oracle-apex.com/incompletebroken-html-output/#comments</comments>
		<pubDate>Tue, 27 Feb 2007 14:47:00 +0000</pubDate>
		<dc:creator>Patrick Wolf</dc:creator>
				<category><![CDATA[Caution]]></category>
		<category><![CDATA[installation]]></category>

		<guid isPermaLink="false">http://www.inside-oracle-apex.com/en/?p=87</guid>
		<description><![CDATA[A few days ago an ApexLib user from Norway contacted me and told me that the framework doesn&#8217;t work and he is getting JavaScript errors. I looked at the provided HTML output and I was scratching my head, because the output looked really strange and I couldn&#8217;t really come of with a good reason why [...]]]></description>
		<wfw:commentRss>http://www.inside-oracle-apex.com/incompletebroken-html-output/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Referencing non existing APEX items</title>
		<link>http://www.inside-oracle-apex.com/referencing-non-existing-apex-items/</link>
		<comments>http://www.inside-oracle-apex.com/referencing-non-existing-apex-items/#comments</comments>
		<pubDate>Thu, 30 Nov 2006 11:55:00 +0000</pubDate>
		<dc:creator>Patrick Wolf</dc:creator>
				<category><![CDATA[Caution]]></category>

		<guid isPermaLink="false">http://www.inside-oracle-apex.com/en/?p=11</guid>
		<description><![CDATA[Did you know that when you reference a non existing APEX item in your SQL statements or PL/SQL code, that you are not getting a runtime error? APEX will just return NULL in such a case! It doesn&#8217;t matter if you reference it with the bind variable- (eg 8_TEST), V or NV function- (eg V(&#8216;P8_TEST&#8217;) [...]]]></description>
		<wfw:commentRss>http://www.inside-oracle-apex.com/referencing-non-existing-apex-items/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>APEX items and implicit type conversion</title>
		<link>http://www.inside-oracle-apex.com/apex-items-and-implicit-type-conversion/</link>
		<comments>http://www.inside-oracle-apex.com/apex-items-and-implicit-type-conversion/#comments</comments>
		<pubDate>Wed, 29 Nov 2006 12:31:00 +0000</pubDate>
		<dc:creator>Patrick Wolf</dc:creator>
				<category><![CDATA[Caution]]></category>

		<guid isPermaLink="false">http://www.inside-oracle-apex.com/en/?p=8</guid>
		<description><![CDATA[Be aware when using bind variables or the V function to reference an Oracle APEX item in your SQL statements or your PL/SQL code that APEX/Oracle always stores this values as VARCHAR2&#8242;s in its internal arrays! So each time you reference an item with :YOUR_ITEM or V(&#8216;YOUR_ITEM&#8217;) the SQL/PL-Sql engine does a implicit data type [...]]]></description>
		<wfw:commentRss>http://www.inside-oracle-apex.com/apex-items-and-implicit-type-conversion/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

