Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.misc -> Re: guideline for creating temporary (working) table
Ed Avis wrote:
> rgaffuri_at_cox.net (Ryan Gaffuri) writes:
>
>
>>Reason for not having truncate in production is because you might >>truncate the wrong table.
While I agree with your statement in general there is a far greater danger with truncate than with delete.
As DJ states a rollback is possible from a delete but not with a truncate. But in addition, and perhaps more importantly, I can flashback from a delete after commit but can not with a truncate until 10g.
Missing from all of this, however, is that no one should ever be allowed to perform an unrestricted delete or a truncation in a production database. If the design allows either of these actions the design is bad by definition.
Murphy's law has not been repealed.
-- Daniel Morgan http://www.outreach.washington.edu/ext/certificates/oad/oad_crs.asp http://www.outreach.washington.edu/ext/certificates/aoa/aoa_crs.asp damorgan_at_x.washington.edu (replace 'x' with a 'u' to reply)Received on Sun Feb 01 2004 - 13:28:14 CST