Yeah, we had some stored procedures that were using views on a table
that had changed. So we wanted to update the view and in order to drop
it we had to first remove the view from the stored procedures. Not a
big deal, but still a pain.

-steve

On Thu, 2005-06-30 at 15:02 +0200, Martijn Tonies wrote:

> > > I thought the only downfall of selectable stored procedures was
> that if
> > > you joined to something else it would not use any indexes. I
> might be
> > > wrong or out of date though. With that said, however, we don't
> use
> > > views anymore because of the lack of altering.
> >
> > ? why would you need 'ALTERING'
> > A view is just looking at the existing tables, I just drop, and load
> the
> > revised schema. You do document the schemas? ;)
> >
> > Views are a nice quick way to build a simple view of complex data
>
> You cannot drop a view if it's used by other views, procedures or
> triggers.
>
> :-(
>
> With regards,
>
> Martijn Tonies
> Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS
> SQL
> Server
> Upscene Productions
> http://www.upscene.com
> Database development questions? Check the forum!
> http://www.databasedevelopmentforum.com
>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://firebird.sourceforge.net and click the Resources item
> on the main (top) menu. Try Knowledgebase and FAQ links !
>
> Also search the knowledgebases at http://www.ibphoenix.com
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Yahoo! Groups Links
>
>
>
>
>
>
>


[Non-text portions of this message have been removed]