Choose your database:
AnySQL
MySQL
MS SQL Server
PostgreSQL
SQLite
Firebird
Oracle
SQL Anywhere
DB2
MaxDB

Subscribe to our news:
Partners
Testimonials
Carl Schammel: "I have been in search of a software product that was rich in features and easy for using, but was unable to find one until I came upon Firebird Maestro. Not only does it have all-inclusive integrated functionality, but SQL Maestro Group have provided me with superior support. I now have the management tools at my hand that I have been looking for".
Neil McPherson: "Thanks very much for your advice. I would just like to add that SQL Maestro makes life so much easier to work with Firebird, I have tried some of the other management tools but Maestro is such a nicely organized product and it has never let me down".

More

Add your opinion

Firebird Maestro online Help

Prev Return to chapter overview Next

Package bodies

Firebird packages come in two parts: a  header (keyword PACKAGE) and a  body (keyword PACKAGE BODY). This division is very similar to a Delphi unit, the header corresponding to the interface part and the body corresponding to the implementation part.

 

The package is created first and the package body follows. Whenever a packaged routine determines that it uses a certain database object, a dependency on that object is registered in Firebird system tables. Thereafter, to drop, or maybe alter that object, you first need to remove what depends on it. As it is a package body that depends on it, that package body can just be dropped, even if some other database object depends on this package. When the body is dropped, the header remains, allowing you to recreate its body once the changes related to the removed object are done.

 

On the package creation the corresponding body is created. To specify its definition, select the package body in the Explorer tree and select the Edit Package Body... item from the popup menu.

 



Prev Return to chapter overview Next