distal-attribute
distal-attribute
distal-attribute
distal-attribute

Timestamp/duplicate row

BubikolRamios posted 10 months ago in General
Noted this:
1. have a row, with timestamp field (default current timestamp, on update current timestamp)

2. Dulicate that row. The timestamp value is copyed. I think this should not be done. It should be new current timestamp timestamped upon save of new record.
BubikolRamios posted 10 months ago
Dulicate is realy duplicate (-:
ansgar posted 10 months ago
Exactly - duplicating a timestamp is possible and should be done as it is now I think. But I understand that this is at least a bit worth of a discussion.
BubikolRamios posted 10 months ago
The discussion:

The only purpose of duplicating row is to spare some time, not have to, manual enter stuff that is the same for original and duplicated record.

Key fields are not copyed by default, doh I think they should be. Forinstance, if I have key from 3 columns, I have to manual enter all of them, not just change wanted one(or two in that case). It is I guess supposed that is inteligent creature duing duplicate record (-: And anyway insert would be aborted due to duplicate key violation.

So. looking at first paragraph, stating that I'm creating new record, timestamped field should be new timestamp.

Example: have a zilion of records, all with same timestamp, then I duplicate one --> create new, save. Damn I just seen something wrong entered. How to find that record --> by timestamp - if it would work as suggested, otherwise it submerge into pile of data.

If it would be normal DATETIMNE, I agree it should be copyed.

Please login to leave a reply, or register at first.