On 2015/04/09 13:42, Michael Dykman wrote:
A trigger is far simpler than remodelling your data and adding extra
queries. They are nothing to be afraid of.
Not afraid of, but to be careful when writing. I have had trouble with
my triggers, because I left thisthat out. As for timestamping,
On 2015/04/08 11:42, Andrew Wallace wrote:
I think you'd have to do that with a trigger.
Yes, one can do that with a trigger, but it is a real pain. MySQL now allows
(new.a,new.b,new.c,new.d) (old.a,old.b,old.c,old.d)
but one needs to beware of NULL. Maybe it is better to split off
A trigger is far simpler than remodelling your data and adding extra
queries. They are nothing to be afraid of.
On Thu, Apr 9, 2015 at 10:46 AM, h...@tbbs.net wrote:
On 2015/04/08 11:42, Andrew Wallace wrote:
I think you'd have to do that with a trigger.
Yes, one can do that with a
I think you'd have to do that with a trigger.
On 4/8/15 6:36 AM, Martin Mueller wrote:
I understand how a timestamp column automatically changes when there is a
change in a data row. Is it possible to limit the update to changes in
particular columns? I have a table where I care about changes
W dniu 08.04.2015 o 17:42, Andrew Wallace pisze:
I think you'd have to do that with a trigger.
+1 for using triggers.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql
I understand how a timestamp column automatically changes when there is a
change in a data row. Is it possible to limit the update to changes in
particular columns? I have a table where I care about changes in any of
four different columns, but I don¹t care about changes in other columns or
added
