Re: Can a procedure contain only a SELECT statement?
Date: Sat, 20 Mar 2010 18:20:45 -0400
Robert Klemme <shortcutter_at_googlemail.com> writes:
> On 03/19/2010 08:39 PM, Sybrand Bakker wrote:
>> On Thu, 18 Mar 2010 22:26:44 -0400, Thomas Gagne
>> <TandGandGAGNE_at_gmail.com> wrote:
>>> My background is Sybase & SqlServer. On both, due I'm sure to a
>>> common heritage, a stored procedure is capable of being as simple
>>> or complex as the programmer wants. Sometimes, all that is needed
>>> is a select statement. Sometimes even simple projections may
>>> require multiple steps to prepare the last SELECT. Additionally,
>>> stored procedures are capable of returning multiple result sets. I
>>> assumed, incorrectly, such a thing was not so complicated that it
>>> couldn't be easily done inside Oracl
>> Mickeysoft has never understood the Procedure concept, and ignored the
>> formal defintiion and abused it to return a result set.
>> It seems like you belong to the class of sqlserver 'developers' which
>> is so narrow-minded they automatically reject everything done
>> differently by Oracle and start bashing Oracle for it.
>> Luckily sqlserver is incapable of being an enterprise class product,
>> just because of its poor architecture and vendor lock-in, so your
>> 'objections' are futile.
> I would not be too sure of that. SQL Sever isn't as bad as people are
> trying to make it look - and it's gaining ground, especially in the
> area of dealing with larger data sets. Maybe it's not as "enterprise
> class" as Oracle is (or is claimed to be) but the management tools
> with good graphical user interface were there before Oracle had Grid
> Control. Yes, I know - real DBA's use command line, but there are
> situations where a graphical visualization can greatly help.
One of the biggest winning arguments for Oracle, is that it run on almost all platforms, MS products only run on one.
-- Galen Boyer --- news://freenews.netfront.net/ - complaints: news_at_netfront.net ---Received on Sat Mar 20 2010 - 17:20:45 CDT