"Doug Chamberlin" <DChamberlin@...> wrote in message
news:5.1.0.14.2.20011121221224.01b088b8@......

>
> Paulo replied:
> > For context take a look at my previous posting. But basically it means
> that doing:
> > SELECT * FROM someTable WHERE someCondition...;
> > will return a resultset.
>
> From other postings I see that Paulo knows about
> FOR...SELECT...INTO...DO...SUSPEND so I take it that he finds this syntax
> burdensome and thinks that it should simply be SELECT * FROM someTable
> WHERE someCondition...;
>
> Sorry, but I don't buy it. If that's all that the complaint is then I'm
> dismissing it as noise.

The fact is that in MsSql, you can create a procedure that returns rows
without declaring output parameters. So, he seems to be saying that you
avoid the burden of declaring as many output parameters as you need and the
INTO clause in IB/FB that loads fields into those output parameters.

I remember that Helen used to do the same cheap trick in IB5.1, but it was
due to a bug in the engine. You could skip parameters. IB4.2 never accepted
that to my knowledge and when IB 5.X was fixed, Helen lost the advantage.
:-)

C.
--
Claudio Valderrama C. - http://www.cvalde.com - http://www.firebirdSql.org
Independent developer
Owner of the Interbase® WebRing