Mike, I see you already have some good answers.
In terms of good practice, here are some reasons DROP has been good practice: nothing bad happens if you drop a non-existing cursor bad things happen if you declare a cursor that already exists when you are developing and tracing, you will sometimes want to break out of a loop leaving a cursor declared and open Bill On Sunday, November 8, 2009, Michael J. Sinclair <[email protected]> wrote: > > > > > > Hi all, > Is there a way to tell if a cursor has already been declared before I drop it > and the recreate it? Or do most programmers just drop the cursor before > creating it to make sure it can be created? > > I am trying to improve my coding skills. I don't know if dropping a cursor > that has not already been created is considered a "bad practice" beause it > genereates an error (even though the error message can be turned off) or > a "good practice" because it helps to ensure that the cursor will be created > properly. > > Mike > > > > >
