If your application uses Oracle Forms, you'll defintely want to use
SIGNATURE mode. The newer versions of Forms tend to be more fragile in terms
of "panicking" after schema (package) changes, and tend to require frequent
recompilation in TIMESTAMP mode. Even in SIGNATURE mode, you'll still get
the occasional unwarranted ORA-4062 after a non-signature-changing change to
a package.
It seems to me there used to be a small bug in SIGNATURE mode... something
like if you changed the DEFAULT value of a procedure argument, the compiler
wouldn't detect this as a signature change. This was a while back so it may
be fixed now.
Hope this helps -
Tim
On 10/1/05, Amihay Gonen <AmihayG_at_ectel.com> wrote:
>
> Hi all ,
> I wander which mode is better ?
> I know that the default in oracle is timestamp , which is more suitable
> for development where table structures are happing , but I production I'm
> under impression the using signature may reduce overhead in recompilation ,
> especially when the code is related to partitions tables the maybe be change
> from time to time.
> What do you say ? If anyone has experience in when using signature ?
>
> *Amihay Gonen
> DBA,
> 972-3-90021678*
>
>
--
http://www.freelists.org/webpage/oracle-l
Received on Sun Oct 02 2005 - 09:52:29 CDT
