It's not illogical at all. You often want (sometimes need) that field to
make sure a record has not changed when you go back to update the row. MS
Access (and others) uses this so as not to overwrite changes made since the
record was retrieved. You can't always rely on the client to set
field=N
CTED]]
Sent: Friday, April 05, 2002 10:48 AM
To: 'Rick Emery'
Subject: RE: Problems with UPDATE in v3.23.49 (is this a bug)
Yes I did, but it is very long, and it was very long ago.
Could someone please explain to me why this was done? It seems more
confusing to do this than to not do t
t "reply to all")
-Original Message-
From: Rick Emery [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 05, 2002 11:34 AM
To: Hihn Jason; '[EMAIL PROTECTED]'
Subject: RE: Problems with UPDATE in v3.23.49 (is this a bug)
No, this is NOT a bug.
According to the manual (you rea
Hi,
> I have a table whose schema contains:
> id INTEGER AUTO_INCREMENT,
> gen_time TIMESTAMP,
> rec_time TIMESTAMP,
> repeats INTEGER DEFAULT 0,
> PRIMARY KEY (id),
> INDEX (rec_time))
>
> When I do an:
> UPDATE table SET repeats=repeats+1
>
> gen_time gets updated as well:
[snip]
> mysql> sel
From: "Hihn Jason" <[EMAIL PROTECTED]>
> I have a table whose schema contains:
> id INTEGER AUTO_INCREMENT,
> gen_time TIMESTAMP,
> rec_time TIMESTAMP,
> repeats INTEGER DEFAULT 0,
> PRIMARY KEY (id),
> INDEX (rec_time))
>
> When I do an:
> UPDATE table SET repeats=repeats+1
>
> gen_time gets upd
At 18:33 +0200 4/5/02, Hihn Jason wrote:
>I have a table whose schema contains:
>id INTEGER AUTO_INCREMENT,
>gen_time TIMESTAMP,
>rec_time TIMESTAMP,
>repeats INTEGER DEFAULT 0,
>PRIMARY KEY (id),
>INDEX (rec_time))
>
>When I do an:
>UPDATE table SET repeats=repeats+1
>
>gen_time gets updated as w
[mailto:[EMAIL PROTECTED]]
Sent: Friday, April 05, 2002 10:33 AM
To: '[EMAIL PROTECTED]'
Subject: Problems with UPDATE in v3.23.49 (is this a bug)
I have a table whose schema contains:
id INTEGER AUTO_INCREMENT,
gen_time TIMESTAMP,
rec_time TIMESTAMP,
repeats INTEGER DEFAULT 0,
PRIMA
I have a table whose schema contains:
id INTEGER AUTO_INCREMENT,
gen_time TIMESTAMP,
rec_time TIMESTAMP,
repeats INTEGER DEFAULT 0,
PRIMARY KEY (id),
INDEX (rec_time))
When I do an:
UPDATE table SET repeats=repeats+1
gen_time gets updated as well:
mysql> select id, gen_time, rec_time, repea
