Subject | Re: [ib-support] Metadata SP order extraction problem |
---|---|
Author | Martijn Tonies |
Post date | 2003-01-21T13:38:09Z |
Hi Marco,
The "usual" way of extracting procedures in order to avoid this is
actually quite simple:
First, extract all "headers":
CREATE PROCEDURE ...
BEGIN
SUSPEND;
END;
After that, all procedures are created with the right amount of
parameters etc...
Next, extract the "bodies":
ALTER PROCEDURE ...
BEGIN
.. full procedure code ..
END;
With regards,
Martijn Tonies
InterBase Workbench - the developer tool for InterBase & Firebird
Firebird Workbench - the developer tool for Firebird
Upscene Productions
http://www.upscene.com
"This is an object-oriented system.
If we change anything, the users object."
The "usual" way of extracting procedures in order to avoid this is
actually quite simple:
First, extract all "headers":
CREATE PROCEDURE ...
BEGIN
SUSPEND;
END;
After that, all procedures are created with the right amount of
parameters etc...
Next, extract the "bodies":
ALTER PROCEDURE ...
BEGIN
.. full procedure code ..
END;
With regards,
Martijn Tonies
InterBase Workbench - the developer tool for InterBase & Firebird
Firebird Workbench - the developer tool for Firebird
Upscene Productions
http://www.upscene.com
"This is an object-oriented system.
If we change anything, the users object."
> Hi, I've always extracted metadata (with IB_Manager or IB_SQL),
> modified and rebuild the database.
> Now that I've add other more SP in my database, I can't rebuild
> because the order in wich metatata is extracted makes a SP being
> created before another SP that it calls (i.e. A calls B, and A is
> created before B, so it does not found the B reference).
> If I rearrange the SP order and build the database, next time I
> extract and rebuild I have the same problem.
> Is there a way to extract the SP in "creation" order? How can I avoid
> this?