On Oct 10, 11:53 am, Michael Moore <michaeljmo...@gmail.com> wrote: > Why would you put those constants in the spec rather than the body? > > Mike > > > > On Mon, Oct 10, 2011 at 11:43 AM, ddf <orat...@msn.com> wrote: > > > On Oct 10, 10:59 am, Michael Moore <michaeljmo...@gmail.com> wrote: > > > 11gR2 > > > > What measures should a pl/sql developer take to minimize disruption to > > > production processes when compiling changed plsql cod into prod.. > > > > For example, I have both Java and other PL/SQL code making calls to a > > > package which I need to modify. I make the modifications in DEV and now I > > > want to compile it in Prod. What measures can I take to avoid ORA-04068 > > and > > > other such problems. > > > > For example, if I have global package variables defined in the body, > > could > > > this cause problems? What if those variables were defined as CONSTANT, > > would > > > that make a difference. I've heard that making a separate package spec > > where > > > these global variables can be defined can be helpful, but I've also heard > > > that with 11gR2, that's not so much of a problem. > > > > Thanks, > > > Mike > > > As of 11.2.0.2 a package is considered stateless if the state is > > constant for the duration of the session. This makes it less likely > > that hot patching will disrupt running sessions (although it can > > occur). I've always divided packages into a spec and a body, where > > the spec can contain any constants global to the package; recompiling > > the body doesn't disrupt the state of the spec. > > > I hope that helps. > > > David Fitzjarrell > > > -- > > You received this message because you are subscribed to the Google > > Groups "Oracle PL/SQL" group. > > To post to this group, send email to Oracle-PLSQL@googlegroups.com > > To unsubscribe from this group, send email to > > oracle-plsql-unsubscr...@googlegroups.com > > For more options, visit this group at > >http://groups.google.com/group/Oracle-PLSQL?hl=en- Hide quoted text - > > - Show quoted text -
Habit, I guess. I really have no other reason for it. I don't write a lot of package code anymore so it's probably bad practice from years ago I haven't corrected. David Fitzjarrell -- You received this message because you are subscribed to the Google Groups "Oracle PL/SQL" group. To post to this group, send email to Oracle-PLSQL@googlegroups.com To unsubscribe from this group, send email to oracle-plsql-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Oracle-PLSQL?hl=en
