<?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: To Specify the location for New Column in Oracle</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/to-specify-the-location-for-new-column-in-oracle-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/to-specify-the-location-for-new-column-in-oracle-2/</link>
	<description></description>
	<lastBuildDate>Thu, 20 Jun 2013 03:04:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: kccrosser</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/to-specify-the-location-for-new-column-in-oracle-2/#comment-89310</link>
		<dc:creator>kccrosser</dc:creator>
		<pubDate>Fri, 11 Mar 2011 21:13:06 +0000</pubDate>
		<guid isPermaLink="false">#comment-89310</guid>
		<description><![CDATA[DangerMouse - the same comment about &quot;select *&quot; applies in reverse for Insert statements.  Instead of using 
&lt;pre&gt;insert into tablename values (...valuelist...)&lt;/pre&gt;you should always enumerate the inserted column names, like 
&lt;pre&gt;insert into tablename (...columnnamelist...) values (...valuelist...)&lt;/pre&gt;

Then, as long as any new columns are not specified as Non-Null, your old Insert statements will still work.  Using positional assumptions about database table columns is not a recommended practice with any database.]]></description>
		<content:encoded><![CDATA[<p>DangerMouse &#8211; the same comment about &#8220;select *&#8221; applies in reverse for Insert statements.  Instead of using </p>
<pre>insert into tablename values (...valuelist...)</pre>
<p>you should always enumerate the inserted column names, like </p>
<pre>insert into tablename (...columnnamelist...) values (...valuelist...)</pre>
<p>Then, as long as any new columns are not specified as Non-Null, your old Insert statements will still work.  Using positional assumptions about database table columns is not a recommended practice with any database.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: carlosdl</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/to-specify-the-location-for-new-column-in-oracle-2/#comment-89207</link>
		<dc:creator>carlosdl</dc:creator>
		<pubDate>Thu, 10 Mar 2011 13:51:08 +0000</pubDate>
		<guid isPermaLink="false">#comment-89207</guid>
		<description><![CDATA[I don&#039;t see how the last comments relate to the original question, which was about adding new columns to a table (not about inserting new rows).]]></description>
		<content:encoded><![CDATA[<p>I don&#8217;t see how the last comments relate to the original question, which was about adding new columns to a table (not about inserting new rows).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dagnermouse</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/to-specify-the-location-for-new-column-in-oracle-2/#comment-89181</link>
		<dc:creator>dagnermouse</dc:creator>
		<pubDate>Wed, 09 Mar 2011 22:00:21 +0000</pubDate>
		<guid isPermaLink="false">#comment-89181</guid>
		<description><![CDATA[That&#039;s just not true. If you&#039;re writing COBOL code that gets run through the Pro*COBOL precompiler, and you&#039;re using VARCHAR2 or LOB data types, and you do an INSERT, and your column order as spec&#039;d in the COBOL does not match EXACTLY the column ids of your Oracle table definition, the INSERT will flat out fail.  So how in the hell do we get around this, eh?  Nobody seems to know, but the problem clearly exists.]]></description>
		<content:encoded><![CDATA[<p>That&#8217;s just not true. If you&#8217;re writing COBOL code that gets run through the Pro*COBOL precompiler, and you&#8217;re using VARCHAR2 or LOB data types, and you do an INSERT, and your column order as spec&#8217;d in the COBOL does not match EXACTLY the column ids of your Oracle table definition, the INSERT will flat out fail.  So how in the hell do we get around this, eh?  Nobody seems to know, but the problem clearly exists.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: meandyou</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/to-specify-the-location-for-new-column-in-oracle-2/#comment-68348</link>
		<dc:creator>meandyou</dc:creator>
		<pubDate>Thu, 24 Sep 2009 20:19:18 +0000</pubDate>
		<guid isPermaLink="false">#comment-68348</guid>
		<description><![CDATA[My favorite answer to questions such as &quot;Why doesn&#039;t company/product XYZ allow ...&quot;
is to say that during development this very topic was discussed, they flipped a coin, and it came up heads, and they decided not to ...]]></description>
		<content:encoded><![CDATA[<p>My favorite answer to questions such as &#8220;Why doesn&#8217;t company/product XYZ allow &#8230;&#8221;<br />
is to say that during development this very topic was discussed, they flipped a coin, and it came up heads, and they decided not to &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: carlosdl</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/to-specify-the-location-for-new-column-in-oracle-2/#comment-68305</link>
		<dc:creator>carlosdl</dc:creator>
		<pubDate>Thu, 24 Sep 2009 01:08:42 +0000</pubDate>
		<guid isPermaLink="false">#comment-68305</guid>
		<description><![CDATA[Valuable points, and explanations.

However, &lt;b&gt;Why Oracle doesn&#039;t let you do the same&lt;/b&gt;, and &quot;&lt;b&gt;Is there any option/chances in the up coming versions of Oracle&lt;/b&gt;&quot; are unanswered questions so far, and that&#039;s why I said &quot;I&#039;m afraid only Oracle could answer these questions&quot;.]]></description>
		<content:encoded><![CDATA[<p>Valuable points, and explanations.</p>
<p>However, <b>Why Oracle doesn&#8217;t let you do the same</b>, and &#8220;<b>Is there any option/chances in the up coming versions of Oracle</b>&#8221; are unanswered questions so far, and that&#8217;s why I said &#8220;I&#8217;m afraid only Oracle could answer these questions&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mrdenny</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/to-specify-the-location-for-new-column-in-oracle-2/#comment-68302</link>
		<dc:creator>mrdenny</dc:creator>
		<pubDate>Thu, 24 Sep 2009 00:43:04 +0000</pubDate>
		<guid isPermaLink="false">#comment-68302</guid>
		<description><![CDATA[MySQL may appear to let you do this, but what it is probably doing in the background is creating a new table with the column where you place it, moving all the data into the new table, dropping the old table, then renaming the new name.

Microsoft SQL allows you do to this, by using that exact process.  It even shows you that its doing this.]]></description>
		<content:encoded><![CDATA[<p>MySQL may appear to let you do this, but what it is probably doing in the background is creating a new table with the column where you place it, moving all the data into the new table, dropping the old table, then renaming the new name.</p>
<p>Microsoft SQL allows you do to this, by using that exact process.  It even shows you that its doing this.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 6/8 queries in 0.015 seconds using memcached
Object Caching 339/340 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-06-20 03:32:31 -->