| From: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: autocommit vs TRUNCATE et al |
| Date: | 2002-10-22 14:35:46 |
| Message-ID: | 46C15C39FEB2C44BA555E356FBCD6FA4961ECD@m0114.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> What I just committed uses your idea of auto-committing TRUNCATE et al,
> but now that I review the thread I think that everyone else thought that
> that was a dangerous idea. How do you feel about simply throwing an error
> in autocommit-off mode, instead? (At least it's a localized
> change now)
Well, if I can throw in another opinion, I think what you did is perfect.
It will make Oracle users happy too. Only very shrewd applications would
commit previous changes with a "truncate" statement, and those will learn
to issue a commit before truncate. I don't like the solutions involving
"set autocommit ...".
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ryan Mahoney | 2002-10-22 14:41:06 | Re: integer array, push and pop |
| Previous Message | Andrew Sullivan | 2002-10-22 14:34:42 | Re: Hot Backup |