5 Dec
2003
5 Dec
'03
9:19 a.m.
<RANT FRUSTRATION=HIGH>
Who's the asshole that decided an UPDATE command in SQL without a WHERE
clause defaults to ALL?
</RANT>
--
Sellam Ismail Vintage Computer Festival
------------------------------------------------------------------------------
International Man of Intrigue and Danger http://www.vintage.org
[ Old computing resources for business || Buy/Sell/Trade Vintage Computers ]
[ and academia at www.VintageTech.com || at http://marketplace.vintage.org ]
5 Dec
5 Dec
9:28 a.m.
Hope you had a backup...
Lyle
On Friday 05 December 2003 12:19, Vintage Computer Festival wrote:
<RANT FRUSTRATION=HIGH>
Who's the asshole that decided an UPDATE command in SQL without a WHERE
clause defaults to ALL?
</RANT>
--
Lyle Bickley
Bickley Consulting West Inc.
Mountain View, CA 94040
"Black holes are where God is dividing by zero"
6 Dec
6 Dec
6:54 a.m.
On Fri, 5 Dec 2003, Lyle Bickley wrote:
Hope you had a backup...
No, but I did have the original source data file so I just had to
reimport.
I really need to get my backup system automated :/
--
Sellam Ismail Vintage Computer Festival
------------------------------------------------------------------------------
International Man of Intrigue and Danger http://www.vintage.org
[ Old computing resources for business || Buy/Sell/Trade Vintage Computers ]
[ and academia at www.VintageTech.com || at http://marketplace.vintage.org ]
5 Dec
5 Dec
11:30 a.m.
New subject: Necessary rant
<RANT FRUSTRATION=HIGH>
Who's the asshole that decided an UPDATE command in SQL without a WHERE
clause defaults to ALL?
</RANT>
Ouch. Same for DELETE by the way.
This may be a good opportunity to pick up the thread about MySQL and other
databases. :-)
One of the things that mission-critical-appropriate databases provide, IMHO,
is a running transaction log or similar mechanism that facilitates not only
transaction management and rollback, but also backup and recovery up to a
point in time. I'm pretty sure MySQL doesn't offer this. Does anyone know
if PostgreSQL does?
Patrick
12:09 p.m.
New subject: Necessary rant
Oracle 10g can do that.
Basically you can do a flashback of a database or a table to a point in history.
Ed
Patrick Rigney wrote:
--
The Wanderer | Politici zijn onbetrouwbaar
quapla(a)xs4all.nl | Europarlementariers: zakkenvullers
http://www.groenenberg.net | en neuspeuteraars.
Unix Lives! M$ Windows is rommel! | Wie mij te na komt zal het weten.
'97 TL1000S |
<RANT FRUSTRATION=HIGH>
Who's the asshole that decided an UPDATE command in SQL without a WHERE
clause defaults to ALL?
</RANT>
Ouch. Same for DELETE by the way.
This may be a good opportunity to pick up the thread about MySQL and other
databases. :-)
One of the things that mission-critical-appropriate databases provide, IMHO,
is a running transaction log or similar mechanism that facilitates not only
transaction management and rollback, but also backup and recovery up to a
point in time. I'm pretty sure MySQL doesn't offer this. Does anyone know
if PostgreSQL does?
Patrick 
9:27 p.m.
New subject: Necessary rant
On Fri, 5 Dec 2003, Patrick Rigney wrote:
One of the things that mission-critical-appropriate
databases provide, IMHO,
is a running transaction log or similar mechanism that facilitates not only
transaction management and rollback, but also backup and recovery up to a
point in time. I'm pretty sure MySQL doesn't offer this. Does anyone know
if PostgreSQL does?
MySQL does with InnoDB. PostgreSQL has for a longer period of time;
I've used MySQL for many years now. It's an incredible database. I've yet
to need anything else... perhaps thats a reflection on my hubris in
accepting an RDBMS - but I've released multiple pieces of software that
run on MySQL, and never wanted.
Of course, I'm biased. But until you try it, you never appreciate it.
Perhaps the same could be said for my not trying Oracle... but you know,
that lacking multiple hundreds of thousands of dollars for licences :)
I've never used PostgreSQL either - but I know its an extremely fine
RDBMS, not as fast as My, but has a number of extra features that is
desirable to many developers.
At any rate, for what its worth, my opinion. I've only been using MySQL
for five years now :)
JP
6 Dec
6 Dec
8:53 a.m.
New subject: OT: RE: Necessary rant
On Sat, 6 Dec 2003, JP Hindin wrote:
Of course, I'm biased. But until you try it, you
never appreciate it.
Perhaps the same could be said for my not trying Oracle... but you know,
that lacking multiple hundreds of thousands of dollars for licences :)
I believe you can now download a copy free for development purposes.
--
Sellam Ismail Vintage Computer Festival
------------------------------------------------------------------------------
International Man of Intrigue and Danger http://www.vintage.org
[ Old computing resources for business || Buy/Sell/Trade Vintage Computers ]
[ and academia at www.VintageTech.com || at http://marketplace.vintage.org ]
7:43 a.m.
New subject: Necessary rant
On Fri, 5 Dec 2003, Patrick Rigney wrote:
I know, which made it easy to zap the table so I could reload it :)
I mean, I knew that this is the behavior of the UPDATE and DELETE
commands, but when you're not paying attention you can easily hork up your
database. TOO easily! It's just stupid!
<RANT
FRUSTRATION=HIGH>
Who's the asshole that decided an UPDATE command in SQL without a WHERE
clause defaults to ALL?
</RANT>
Ouch. Same for DELETE by the way. This may be a good opportunity to pick up the thread
about MySQL and other
databases. :-)
One of the things that mission-critical-appropriate databases provide, IMHO,
is a running transaction log or similar mechanism that facilitates not only
transaction management and rollback, but also backup and recovery up to a
point in time. I'm pretty sure MySQL doesn't offer this. Does anyone know
if PostgreSQL does?
How about just modifying the command to require an ALL clause to delete or
update all, rather than that being the default behavior? You'd think this
would be the case. WHO is the jackass that designed this?
Fortunately, MySQL tables are easy to backup. Just copy the files in the
data directory. It would be nice to have rollback features though.
--
Sellam Ismail Vintage Computer Festival
------------------------------------------------------------------------------
International Man of Intrigue and Danger http://www.vintage.org
[ Old computing resources for business || Buy/Sell/Trade Vintage Computers ]
[ and academia at www.VintageTech.com || at http://marketplace.vintage.org ]
7 Dec
7 Dec
5 a.m.
New subject: Necessary rant
On Sat, Dec 06, 2003 at 10:43:25AM -0800, Vintage Computer Festival wrote:
The guys designing the SQL92/99 standards?
On Fri, 5 Dec 2003, Patrick Rigney wrote:
I know, which made it easy to zap the table so I could reload it :)
I mean, I knew that this is the behavior of the UPDATE and DELETE
commands, but when you're not paying attention you can easily hork up your
database. TOO easily! It's just stupid!
The old problem with powerful tools: you can get all kinds of stuff
done, but if you are not careful, bad things are going to happen.
Yes, once upon time this one came to bite me in the ass. When one
directly messes with UPDATE on the grant tables (because the wannabe
database in questions didn't support doing it the right way, and no, it
also didn't support transactions) to change a users DB password,
forgeting the WHERE clause is a good way to get lots of attention
<RANT
FRUSTRATION=HIGH>
Who's the asshole that decided an UPDATE command in SQL without a WHERE
clause defaults to ALL?
</RANT>
Ouch. Same for DELETE by the way. from coworkers ;-)
This may be a
good opportunity to pick up the thread about MySQL and other
databases. :-)
One of the things that mission-critical-appropriate databases provide, IMHO,
is a running transaction log or similar mechanism that facilitates not only
transaction management and rollback, but also backup and recovery up to a
point in time. I'm pretty sure MySQL doesn't offer this. Does anyone know
if PostgreSQL does?
How about just modifying the command to require an ALL clause to delete or
update all, rather than that being the default behavior? You'd think this
would be the case. WHO is the jackass that designed this? Fortunately, MySQL tables are easy to backup. Just
copy the files in the
data directory. It would be nice to have rollback features though.
Simple: wrap your critical operations in a transaction. Start the
transaction, do your changes, check them. If everything is ok, commit
else rollback. Ok, with MySQL you might have to use a special table type
to get support for transactions, but thats just one of the warts one has
to accept for not using a real RDBMS ;-)
Regards,
Alex.
--
"Opportunity is missed by most people because it is dressed in overalls and
looks like work." -- Thomas A. Edison
7539
days inactive
7541
days old
8 comments
6 participants
participants (6)
-
als＠thangorodrim.de -
jplist＠kiwigeek.com -
lbickley＠bickleywest.com -
patrick＠evocative.com -
quapla＠xs4all.nl -
vcf＠siconic.com