<?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 for TeamFuze</title>
	<atom:link href="http://blogs.inside.quest.com/teamfuze/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.inside.quest.com/teamfuze</link>
	<description>Fusing Oracle professionals into Visual Studio Team System</description>
	<pubDate>Mon, 22 Mar 2010 02:43:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Let&#8217;s get cracking! by dwood</title>
		<link>http://blogs.inside.quest.com/teamfuze/2009/02/23/lets-get-cracking/#comment-72</link>
		<dc:creator>dwood</dc:creator>
		<pubDate>Mon, 11 Jan 2010 22:40:13 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.inside.quest.com/teamfuze/?p=4#comment-72</guid>
		<description>Jim, now that we're getting close to our public release we're in a better position to comment on your concern about package and schema support. We incorporated your early comments into our design principles and now require that every object in an Oracle project be prefixed with a schema name. When you import objects from a database we automatically import the DDL script as "schema.object". Also programmatic objects such as views/packages/procs/functions are all imported with the create or replace syntax.</description>
		<content:encoded><![CDATA[<p>Jim, now that we&#8217;re getting close to our public release we&#8217;re in a better position to comment on your concern about package and schema support. We incorporated your early comments into our design principles and now require that every object in an Oracle project be prefixed with a schema name. When you import objects from a database we automatically import the DDL script as &#8220;schema.object&#8221;. Also programmatic objects such as views/packages/procs/functions are all imported with the create or replace syntax.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Let&#8217;s get cracking! by Jim OGrady</title>
		<link>http://blogs.inside.quest.com/teamfuze/2009/02/23/lets-get-cracking/#comment-4</link>
		<dc:creator>Jim OGrady</dc:creator>
		<pubDate>Mon, 13 Apr 2009 22:19:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.inside.quest.com/teamfuze/?p=4#comment-4</guid>
		<description>I've explored using "ODP for .NET" in contrast with ".NET Framework Data Provider for Oracle" within Visual Studio 2008 and noticed that while "ODP for .net" does expand vastly upon the capabilities of the ".NET Framework Data Provider for Oracle", it is still limiting.  Specifically, you can view the source code for packages, but the source objects are missing their schema prefix.  It should say SchemaName.ObjectName, and it only has ObjectName.  Also, the source code is missing a "CREATE AND REPLACE" command in front of the keyword PACKAGE when you view the source code from the Server Explorer window. You only see "PACKAGE Pk_Mail_Pkg", whereas the actual source code contains "CREATE OR REPLACE PACKAGE MASTER.Pk_Mail_Pkg".  Hopefully, these will be controlled via configuration/setup parameters.  Also, both providers allow you the ability to "Run" or "Run on" (meaning Compile) for procedures and functions, but not packages.  It seems that the ability to support packages is still a little lacking by both data providers.  Hopefully, this will not be neglected when Quest develops their DSP for Oracle.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve explored using &#8220;ODP for .NET&#8221; in contrast with &#8220;.NET Framework Data Provider for Oracle&#8221; within Visual Studio 2008 and noticed that while &#8220;ODP for .net&#8221; does expand vastly upon the capabilities of the &#8220;.NET Framework Data Provider for Oracle&#8221;, it is still limiting.  Specifically, you can view the source code for packages, but the source objects are missing their schema prefix.  It should say SchemaName.ObjectName, and it only has ObjectName.  Also, the source code is missing a &#8220;CREATE AND REPLACE&#8221; command in front of the keyword PACKAGE when you view the source code from the Server Explorer window. You only see &#8220;PACKAGE Pk_Mail_Pkg&#8221;, whereas the actual source code contains &#8220;CREATE OR REPLACE PACKAGE MASTER.Pk_Mail_Pkg&#8221;.  Hopefully, these will be controlled via configuration/setup parameters.  Also, both providers allow you the ability to &#8220;Run&#8221; or &#8220;Run on&#8221; (meaning Compile) for procedures and functions, but not packages.  It seems that the ability to support packages is still a little lacking by both data providers.  Hopefully, this will not be neglected when Quest develops their DSP for Oracle.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Let&#8217;s get cracking! by Brent Ozar</title>
		<link>http://blogs.inside.quest.com/teamfuze/2009/02/23/lets-get-cracking/#comment-3</link>
		<dc:creator>Brent Ozar</dc:creator>
		<pubDate>Tue, 24 Feb 2009 13:45:56 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.inside.quest.com/teamfuze/?p=4#comment-3</guid>
		<description>Congratulations, man.  When Rony said you guys were taking on this project, the only thing I could say is, "Wow."  It must have been a hell of a tough challenge, and I'm looking forward to seeing the results.  Way to go!</description>
		<content:encoded><![CDATA[<p>Congratulations, man.  When Rony said you guys were taking on this project, the only thing I could say is, &#8220;Wow.&#8221;  It must have been a hell of a tough challenge, and I&#8217;m looking forward to seeing the results.  Way to go!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
