https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10459
--- Comment #27 from Marcel de Rooy <[email protected]> --- Thanks for reviving this. The reason I left this pending however, is probably as valid as then. If you call the field timestamp, we will have clashes in SQL joins here and there in the codebase where another table also has the same field timestamp. Especially think about the SELECT * statements with timestamp in another clause as well. So to prevent the ambiguous column name errors, we need to track these cases, test.. and hope we found them all. An older alternative to add bortimestamp, introducing a new name, did not meet much approval. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
