Cesare Zecca
Member²
Hi all!
I'm quite new to the PL/SQL Developer...
I apologize in advance if my question will result naive to any of you.
I need to keep distinct (for a number of reasons)
the interfaces (specification files) from the
implementations (body files).
Well, I've realized that
o - it'is possibile to specify file extensions
for both specs and bodies (Tools - Preferences... Files)
o - when File - Save(ing) as...
it's possible to select either body or spec-
It would seem that PL/SQL Developer supports
the distinction but...
But...
o - when using the VCS, e.g., the Add command
allows you only to add to the module/repositoy
as a unique file (.pck)
even if you have saved spec&body in two different files
o - if you either View or Edit Spec & Body
the IDE looses that the two files were originally distinct and tends to save them into a unique file
regardless of the explicit selection of the
proper extension (Packages specification vs Packase bodies)
Is there any option that forces PL/SQL developer
to handle and to treat consistently
separated files for bodies and specs?
Is this a known limitation (if it's can be
ragarded to as limitation)?
Any plan to improve the consistency
of handling of separated Specs & bodies?
For instance, the expected behaviour for the
View(Edit) Spec and Body, when the Spec and Body
are in distinct files
should be to open both files in one shot
(a kind of user facility, a macro)
while keeping them distinct, also when the files
should be saved later...
Currently (ver. 6.0.5.926), in such a case,
PL/SQL Developer saves in one file both the spec
and the body...
Thanks in advance for any help.
Regards
Cesare
I'm quite new to the PL/SQL Developer...
I apologize in advance if my question will result naive to any of you.
I need to keep distinct (for a number of reasons)
the interfaces (specification files) from the
implementations (body files).
Well, I've realized that
o - it'is possibile to specify file extensions
for both specs and bodies (Tools - Preferences... Files)
o - when File - Save(ing) as...
it's possible to select either body or spec-
It would seem that PL/SQL Developer supports
the distinction but...
But...
o - when using the VCS, e.g., the Add command
allows you only to add to the module/repositoy
as a unique file (.pck)
even if you have saved spec&body in two different files
o - if you either View or Edit Spec & Body
the IDE looses that the two files were originally distinct and tends to save them into a unique file
regardless of the explicit selection of the
proper extension (Packages specification vs Packase bodies)
Is there any option that forces PL/SQL developer
to handle and to treat consistently
separated files for bodies and specs?
Is this a known limitation (if it's can be
ragarded to as limitation)?
Any plan to improve the consistency
of handling of separated Specs & bodies?
For instance, the expected behaviour for the
View(Edit) Spec and Body, when the Spec and Body
are in distinct files
should be to open both files in one shot
(a kind of user facility, a macro)
while keeping them distinct, also when the files
should be saved later...
Currently (ver. 6.0.5.926), in such a case,
PL/SQL Developer saves in one file both the spec
and the body...
Thanks in advance for any help.
Regards
Cesare