duplicate row
| User, date | Message |
|---|---|
|
Written by BubikolRamios
6 months ago Category: General 273 posts since Thu, 14 Jan 10 |
data view/rigt click/ duplicate row If the source field is type of timestamp and default is current_timestamp, I think that value should not be copyed, instead field new row should have current_timestamp. The only reason I use duplicate row is to create new record where only some columns data are changed manualy, that is I think the purpose of it ? |
|
Written by BubikolRamios
6 months ago 273 posts since Thu, 14 Jan 10 |
Rewriten: I think that timestamp value should not be copyed, instead in new row, field of type timestamp should have current_timestamp. |
|
Written by ansgar
6 months ago 3950 posts since Fri, 07 Apr 06 |
I'm sure there are users expecting the opposite, don't you? |
|
Written by BubikolRamios
6 months ago 273 posts since Thu, 14 Jan 10 |
Nope,I don't, as I said: The only purpose of 'duplicate row' command is to manualy create new record , sparing some time not having to manualy insert some values, which are same for source and destination row. New record means , at conditions stated in first post, that the date field of new row should be timestamped automaticaly (even if it is part of key). Unless there is some other purpose of 'duplicate row' command which I don't see. |
|
Written by TTSneko
6 months ago 15 posts since Thu, 19 Jul 12 |
"... The only purpose of 'duplicate row' command is to manualy create new record ..." That statement is actually a contradiction in terms: DUPLICATE ROW creates a COPY (a duplicate) of an existing row. If you want a NEW row, you use NEW ROW. What you *WANT* it to do is to create a copy of an existing row whilst the copy process itself then checks and updates certain DEPENDENCIES, e.g. the status of "current_timestamp". That is a completely different and complex matter. Not every user needs that - in fact, many users, applications or cross-table situations do not want/allow data to be automatically altered (e.g. because it may corrupt cross-table data integrity). |
|
Please login to leave a reply, or register at first. |