> -----Original Message-----
> From: Helen Borrie [mailto:helebor@...]
> Sent: Thursday, May 31, 2001 10:30 AM
>
> At 09:19 AM 31-05-01 -0700, you wrote:
> >Stored procs are no good. They don't allow you to run the same query on
> >different tables etc.
> >
> >And while we are on the subject of changes. I was really disappointed to
> >discover that IB wont allow me to select from a select result,
> even crappy
> >access allows you to do that.
>
> Why would you want to do that anyway, when you have views and
> selectable stored procedures which can themselves be selectively
> queried? (Notwithstanding you've already rejected SPs and
> triggers because they spoil your cached updates!)

The feature makes a lot of sense to me.

I use what Peter describes (SELECTing from a SELECT result) in Oracle to get
a range of rows (using a ROWNUM and so). When I am generating SQL on user
request I do not want to crowd my database with zillions of objects that
will only be used a couple of times.

BTW, I also do not want to go trough the trouble of managing a pool of
temporary database objects.


Can I live without such feature? YES.

Would I live better with such feature? YES.


I have also used SELECTs over SELECTs for several other situations involving
dynamic SQL generation... and I have missed a lot such a feature on other
database servers (MS SQL Server 6.5?) for situations where that would have
saved me dozens of hours of coding.


Have fun,
Paulo Gaspar