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.
Unless we used datetime types in the database and relied on the code to provide the correct date rather than the database (as it does with the timestamp type). David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 > -----Original Message----- > From: koha-devel-boun...@lists.koha-community.org [mailto:koha-devel- > boun...@lists.koha-community.org] On Behalf Of Robin Sheat > Sent: Thursday, 13 November 2014 9:34 AM > To: koha-devel@lists.koha-community.org > Subject: Re: [Koha-devel] Ambiguous column names > > Marcel de Rooy schreef op wo 12-11-2014 om 14:58 [+0000]: > > While adding a timestamp to the borrowers table, > > What does timestamp mean? Would more granularity be a good thing? I'm > thinking something like "created" and "updated". On the other hand, maybe > it's overkill. > > -- > Robin Sheat > Catalyst IT Ltd. > ✆ +64 4 803 2204 > GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
