Save pkg spec and body

LO,
When using the "save package spec and body", a single file (pls extension) is generated with package spec and package body, including '/' characters, which is what is expected.
The trouble is that if you open this file back with SQL developer, a PL/SQL editor is opened with both spec and body. This prevents the compilation, since either spec or body is expected, not both.
Suggestion #1: open two PL/SQL windows, one for spec and the other for body
Suggestion #2: do not open PL/SQL editor, but rather SQL Worksheet for pls files
I do not indicate a version since it happens in every version.
Thanks to correct,
Olivier.

Added default file filter *.sql -- the choice between PL/SQL editor and SQL Worksheet is based upon file extension. Expect fix in 3.1.1

Similar Messages

Schema name not present on filename for "Save Package Spec and Body"

In versions previous to 3.0 EA, the filename defaulted to schema.object.sql when using the "Save Package Spec and Body" on the right click of the package/body. This appears to have disappeared. Also, it now defaults to the .PLS ext/type, which I prefer to save them as .SQL (which i can override, but it would be nice in the file type dropdown). Also, I had posted a suggestion about the actual file not including the schema name prefixing the object name when using the "Save Package Spec and Body". i.e. it does create or replace package reader_package instead of what it should be doing which is create or replace package schema.reader_package

Would be nice indeed having the real name as default, and all supported PL/SQL types (as in the preferences) in the extensions dropdown.
As for the schema name inside, I reckon that would do damage for more users than it would do good for others. But a preference would be best of course.
K.

Bug SQL Developer 3.0.04 Save Package Spec and Body to ips file bug

Hi.
I have problem with export package body end header. Exported ips file have some rows switched compared to original source code.
SQL Developer version: 3.0.04. Build MAIN-04.34
Error simulation:
- Click on package header with right mouse button in SQL Developers Connections bar
- In context menu choose 'Save Package Spec and Body...'
- Save ips file... (Small bug: Offered file name is wrong (= last saved package/file, not actual name of package) :-( )
- This file(source code) compare with original source code in Developer and u will see switched rows every +-90. row in source code.
Can u fix this in next version of SQL Developer?
Thanks...
Edited by: 880809 on 22.8.2011 6:57

Bug 12904494 has been created.
Michael

Save package spec and body in lower case ?

I'm using sqldeveloper 3.1.07. We have the convention to save all source files in lower case. However, when I do "Save package spec and body" the filename that is suggested is always upper case. Is there a setting for this that I missed or any way I can change this ?

Buntoro,
thank you very much - that worked just fine (if I start from the Tools menu and then can select only the packages and package body options - and then in the next step do the name filtering for the selected objects).
I was trying to use shift key and select multiple packages from the browser and then unload - that does not give you the "package body" selection option. In that particular case, the related package bodies for the selected packages should be automatically included - but I don't know if that can be classified as a bug or even an improvement, given that this can be achieved from the Tools menu (then unload).
I understand what you mean by
========================================================
"Note that the Package Spec displays only the choosen ones.
But, why on earth unloading all of package body instead of the ones which we chose before?
Simply forward, the output of this caused all of the package body to be exported.
So please be aware before using this."
========================================================
I also believe this is a bug and needs to be fixed.
Buntoro, thanx again.
R/ Zaf
Edited by: zaferaktan on Jan 12, 2011 10:57 AM

30EA2 Save package spec and body - saves only spec?

It seems that the "Save package spec and body" in the popup menu on the spec in the object tree view actually only saves the spec (.pls).
Is that so?

Buntoro,
thank you very much - that worked just fine (if I start from the Tools menu and then can select only the packages and package body options - and then in the next step do the name filtering for the selected objects).
I was trying to use shift key and select multiple packages from the browser and then unload - that does not give you the "package body" selection option. In that particular case, the related package bodies for the selected packages should be automatically included - but I don't know if that can be classified as a bug or even an improvement, given that this can be achieved from the Tools menu (then unload).
I understand what you mean by
========================================================
"Note that the Package Spec displays only the choosen ones.
But, why on earth unloading all of package body instead of the ones which we chose before?
Simply forward, the output of this caused all of the package body to be exported.
So please be aware before using this."
========================================================
I also believe this is a bug and needs to be fixed.
Buntoro, thanx again.
R/ Zaf
Edited by: zaferaktan on Jan 12, 2011 10:57 AM

Saving package spec and body

In previous versions of SQL Developer, there was always an All Files option in the dropdown when saving package spec and body. Now we're using the latest version 3.1.07.42 and the only option available is to save as a .pls extension. We do not use .pls files in our system, and it's annoying to have to save as .pls and then copy the code into another file. Does anyone know a way around this, and also why Oracle has put such a restriction on the save function?

Hi,
Welcome to the forum. This behavior of the chooser UI for Save Package Spec and Body changed between 3.0 and 3.1, mostly for the better, I assume, except perhaps for the issue on which you comment. In general, I believe there was an effort to make the user experience more consistent across the product when opening or saving files.
Checking this area in the code line up next for release, I see that pls and sql are the file extension choices, but not all files. Will that help?
Regards,
Gary
SQL Developer Team

How to retreive contents of package spec and body over jdbc

is there a query i can issue that would return the contents (both spec and body) of a database package? similar to "desc schema.pkg" ?
i want to issue this query via jdbc and get back the contents of the package spec/body.

solved:
select * from user_source where name='my_pkg'
Message was edited by:
user612126

Bulk Export Package Spec and Body as single file

Is there a way to bulk export the package spec and body into a single file, you can export spec and body if you choose each individual proc/package but if you just choose the spec/body individually from the connection - > packages list it only exports that part of the code. If not i will raise as an enhancement.
Thanks
Trotty

Thanks for your update K.
Have tried that and you can sort of do it however you still have to choose/select the spec/body individually so twice the overhead selescting them.
Will raise an enhancement and see where it goes.
Thanks
Trotty

EA2 - Export Wizard - No forward slash after package spec and body in sql

I exported a schema with the export wizard. My stand alone functions and sql types in the script have have a forward slash after the "end;" statement Great. However, package specs and body create statements do not have a forward slash after the "end;" and I believe they also should have this.

This appears to be a DB issue as we are just using DBMS_METADATA to generate the ddl. Please test manually using worksheet or sqlplus
exec DBMS_METADATA.SET_TRANSFORM_PARAM( DBMS_METADATA.SESSION_TRANSFORM, 'SQLTERMINATOR' , TRUE );
select dbms_metadata.get_ddl('PACKAGE', 'PACKAGE_NAME','SCHEMA') from dual;
I looked through the DB bugs briefly and noticed a few on other objects that were fixed in 9.2.0.6 but I didn't see one for Packages...
This is not something I would fix in SQL Developer as the core issue is with DBMS_MEATADATA and your version of the DB.
As this is fixed in 10 I'm sure you can work with support and request a backport if it's not a currently available patch.

Package Spec and Body

I'm exploring an existing package and I can find in the package spec number of procedures are different than the number of procedure in the package Body, how can that happen; and if I try to create a package with different number it gives an error like "object defined in spec and not in body"

duplicate thread
Pachage Spec and Body
Please continue with other one.

Reg: Package Spec and Body

All,
I am adding a function to an existing package. I have added the function code only in the package body and compiled. I have received the below error.
PLS-00313: 'Fun_check' not declared in this scope
Where as, I have declared the same function in the package specification, then no issues.
So, my question is, Can't we add the function/procedure without the declaration of it inside the package specification.Because,I see, there were many functions inside the same package body, which were not declared in the package specification. What will happen, if we declare the function/proc inside the package spec and what if not.
Thanks in advance.
Thanks,

EV259 wrote:
PLS-00313: 'Fun_check' not declared in this scope
For this error need to define the local programs before these being called by another program in package body.
Check below example for giving proper scope to local program in package body.
create or replace package p1
as
procedure p1;
function f1 return number;
end p1;
create or replace package body p1
as
procedure p1
is
var number;
begin
null;
var := f_l; -- first:- calling local f_l before defining will throw error
end;
function f_l   --second:- defining local f_l
return number
is
begin
     null;
return 2;
end;
function f1
return number
is
begin
   null;
   return 1;
end;
end p1;
Warning: Package Body created with compilation errors.
SQL> show err
Errors for PACKAGE BODY P1:
LINE/COL ERROR
8/3      PL/SQL: Statement ignored
8/10     PLS-00313: 'F_L' not declared in this scope
------ Now Creating scope for local function f_l through out pkg body by defining it first!
create or replace package body p1
as
------- can be called in any program below it
function f_l
return number
is
begin
     null;
return 2;
end;
procedure p1
is
var number;
begin
null;
var := f_l;
end;
function f1
return number
is
begin
   null;
   return 1;
end;
end p1;
Package body created.

Split a PL/SQL Package Spec and Body

I hope this was not discussed in some other thread somewhere (haven't found it), but my problem is:
How to split the Package Spec and Package Body in JDeveloper if you want to have both (for database deployment) as files in e.g. a subversion repository?
The problem arises if you have a couple of packages that are dependent on each other, so that you have to deploy the specs first to have the "public" part in place and afterwards the bodies to define the package functions/procedures.
Is there a way to do this?
TIA.
--Ciao, FD.

If you want to store for example the package "mypackage" source code in a subversion repository
one possibility is to define 2 svn files:
- mypackage.pks (which contains the package "specification") and
- mypackage.pkb ( package "body").
I haven't tried this from JDev 11.2 but it works for example when using a single-user
svn repository from Sql Developer 2.1.1. ( in SQL Dev if you specify a database
connection you can compile the file based pakage specification and after then the
package body ...)
Regards
user_alex

How to open and compile a package specification and body in SQL Developer

I'm currently evaluating a possible migration to SQL Developer.
Our PL/SQL code base is stored in scripts files named as follows: <schema>.<package_name>_<package|package_body>.sql and managed in SVN.
If now trying open a sql script containing the package specification or body and trying to compile it, I get no or strange error messages as if SQLDeveloper would not recognize the source as a PL/SQL code.
If I open an already compiled package from the database it seems to work as expected.
On the other hand I cannot find any option to write a package specification or body to a script except for the "Save package spec and body" option that only generates a single (!) script containing package specification and body in one single file and without any configuration options on how to name the generated file.
Any help is appreciated!

What strange error messages ? Make sure to configure your extensions as PL/SQL file type under Preferences - File Types.
To save, just Save As under the File menu.
Hope that helps,
K.

Excel file(.xls) as attachment and Body(Signature) via Receiver Mail Adapter

Hi PI Experts,
I have a requirement File(.txt) - PI(7.4) - mail (.xls attachment and signature in the body). Can anyone pls help me with the best approach to send excel file as mail attachment and signature in the body.
Thanks,
Sri

Hi
You can try this approach
1. use mail package and java mapping to populate the mail package.
inside the java mapping do the following
a. read the text file and convert it to excel and then set it as additional attachment.
b. map the signature and body with the field 'content' of mail package.
2. on the receiver mail adapter check both mail package and keep attachment options.
Hopefully this will work.
Reference links
excel write : Excel and Java - Read and Write Excel with Java - Tutorial
set attachment: How to save MainDocument as additonal attachment in sender channel?

Why we need specification and body in Packages

Hi all
Why we need specification and body in packages
is Package body is not enough?
It is an interview question asked
How can I explain
regds

1. Package specification is the interface.
Package body is the implementation or detail code.
If one has built a package, he/she just need to publishs
the interface without a need to publish the detail implementation, so it will simplify to end user by hiding the detail.
2. Using only a Package body is identical to make separate subroutine. One pkg body will need one subroutine, if there are 10 pkgs body there will be 10 individual subroutine. Using package will give simplicity to manage the code, and also give speed in execution.

Save pkg spec and body

Similar Messages

Maybe you are looking for