|
|
Posted by Cimode on 10/02/59 11:50
It is a limited scope attempt for correctly implementing UNIQUENESS on
all table rows...If you want to understand why it is a *good* practice
you need to learn more about rules of relational modeling and
especially database design and definition of primary keys...
Look for "Introduction to Database Systems" from CJ Date (at Amazon)
Hope this helps...
CK wrote:
> Hi All,
> Quick question, I have always heard it best practice to check for exist, if
> so, drop, then create the proc. I just wanted to know why that's a best
> practice. I am trying to put that theory in place at my work, but they are
> asking for a good reason to do this before actually implementing. All I
> could think of was that so when you're creating a proc you won't get an
> error if the procedure already exists, but doesn't it also have to do with
> Compilation and perhaps Execution. Does anyone have a good argument for
> doing stored procs this way? All feedback is appreciated.
> TIA,
> ~CK
Navigation:
[Reply to this message]
|