EMAIL PROTECTED]
Subject: Re: [ADMIN] "DELETE FROM" protection
Yuji Shinozaki wrote:
>
> I've gotten myself into the habit of always writing out a
>
> SELECT ... FROM ... WHERE ...;
>
> first, and then command-line editing it to
>
> DELETE FROM ..
Yuji Shinozaki wrote:
>
> I've gotten myself into the habit of always writing out a
>
> SELECT ... FROM ... WHERE ...;
>
> first, and then command-line editing it to
>
> DELETE FROM ... WHERE ...;
>
> Putting it in a transaction (BEGIN, COMMIT or ROLLBACK) is probably the
> best pr
I've gotten myself into the habit of always writing out a
SELECT ... FROM ... WHERE ...;
first, and then command-line editing it to
DELETE FROM ... WHERE ...;
Putting it in a transaction (BEGIN, COMMIT or ROLLBACK) is probably the
best practice.
yuji
On Fri, 20 Feb 2004
On Friday, 20.02.2004 at 10:12 +, Matt Clark wrote:
> > So now with pgsql, when I am typing "DELETE FROM" until I get to
> > the "WHERE" part of the statement, I get a little nervous because I
> > know hitting Enter by mistake will wipe out that table. [...]
How about typing the "WHERE"
BEGIN;
DELETE FROM mytable;
!!! OOOPS
ROLLBACK;
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Jeremy Smith
> Sent: 20 February 2004 06:06
> To: [EMAIL PROTECTED]
> Subject: [ADMIN] "DELETE FROM" protection
>
This may be an all-time idiotic question, but when I used phpmysql, when I
would type in a "DELETE FROM" query in the SQL window, it would make me
confirm it before I allowed it to go through. I don't think in all of the
presumably thousands of times that I used it that I ever canceled out of the
