package body and spec in seperate file or in same file?

[sunitha reghu]

I have a package body named tss_app_body.sql and package spec as another file tss_app_spec.sql. my coworker saying these two can be combined to one file tss_app.sql. i said these two should be sperate and he is saying im wrong. so pls let me how it should be. any help appreciated

[Pradeep bhatt]

I ran the command
@d:\test.sql
The out put was
Package created.

Package body created.
The file is
CREATE or replace PACKAGE emp_actions AS

PROCEDURE calc_bonus (date_hired DATE);
END emp_actions;
/
CREATE or replace PACKAGE BODY emp_actions AS
PROCEDURE calc_bonus (date_hired DATE) IS
-- parameter declaration raises an exception because 'DATE'
-- does not match 'emp.hiredate%TYPE' word for word
BEGIN null; END;
END emp_actions;
/
---
Hope this helps

[sunitha reghu]

pradeep,
i have already created package but body in one file and spec in another file. que is making spec and body in one file make any diff. i know it will work but wanna know anyother diff?

[Remar Uy]

Sunitha,
One advantage of separating the package specs from the package body file is when you're running multiple package scripts, invalid reference error could be avoided. Suppose we have two package X and Y. Package X references Y. If we have only one file for both body and spec (X.sql and Y.sql), we have to run the Y.sql first before X.sql or else will have an invalid reference error. But it we separate the package spec and body files, we can run the specs file first (X_spec.sql and Y_spec.sql in any order) without considering the reference. Running the X_body.sql and Y_body.sql would then be reference error free since the specifications has been declared.
Hth,
Remar

[sunitha reghu]

thanks......

[sunitha reghu]

I aslo read its good idea to keep packages small fr pinning in to memory.also the pl/sql complier build an internal tree known as Diana.The max limit prior to 8i is 32k