Hi Lele :)
I've already thought about this solution, but I've been programming
for a long time without this kind of problem, and the fact that no
other seems to have complained about this point seems a little strange
to me.
Anyway, I've tested the extraction with FB 1.0 and 1.02, same result.
The guys at EMS (IB_Manager) told me about a new algorithm to extract
metadata in the correct order, but I'm waiting too long for the next
release, and I do need this.
There should be a "natural order" for the metadata, that maybe IB_SQL
and IB_Manager overrides, or, if not, I will ask Jason about a solution :)
thanks
Marco Menardi

--- In ib-support@yahoogroups.com, Lele Gaifax <lele@n...> wrote:
> >>>>> On Tue, 21 Jan 2003 13:28:00 -0000, "Marco Menardi
<mmenaz@l...>" <mmenaz@l...> said:
>
> "M> Hi, I've always extracted metadata (with IB_Manager or
> "M> IB_SQL), modified and rebuild the database. Now that I've add
> "M> other more SP in my database, I can't rebuild because the
> "M> order in wich metatata is extracted makes a SP being created
> "M> before another SP that it calls (i.e. A calls B, and A is
> "M> created before B, so it does not found the B reference). If I
> "M> rearrange the SP order and build the database, next time I
> "M> extract and rebuild I have the same problem. Is there a way
> "M> to extract the SP in "creation" order? How can I avoid this?
>
> I think that most reasonable way to handle this kind of problem is
> having one stmt that CREATE the SP, *empty* (consider this step
> "declaring" the SPs), then do the ALTER with the real body.
>
> hth,
> ciao, lele.
> --
> nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri
> real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia.
> email: lele@s... | -- Fortunato Depero, 1929.