[Koha-devel] Ambiguous column names

[Robin Sheat]

David Cook schreef op do 13-11-2014 om 12:12 [+1100]:
> I think the best option, if we were to change away from timestamp,
> would have to be "lastmodified", as timestamp types will get updated
> after every insert/update, I believe. But since they'd all be called
> "lastmodified", changing it from "timestamp" would become a bit moot,
> I think.

Well, I was thinking both, "created" and "updated." So you know when the
record was created, and when it was last changed. Both very handy for
simple auditing or bug finding.

It's possible to have a timestamp field that is initialised to the
current date automatically on creation, and another that is auto
updated.

http://dev.mysql.com/doc/refman/5.1/en/timestamp-initialization.html

This would nicely mean that there's no code at all in Koha required to
maintain this.

Anyway, I was just sticking my oar in, I've no desire to bikeshed it
into the ground, anything is better than nothing :)

-- 
Robin Sheat
Catalyst IT Ltd.
✆ +64 4 803 2204
GPG: 5FA7 4B49 1E4D CAA4 4C38  8505 77F5 B724 F871 3BDF
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: This is a digitally signed message part
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20141113/0b904b43/attachment.pgp>