Le dimanche 19 août 2007, Robin Helgelin a écrit :
> My question, is this interesting information enough to save on the
> table itself? If so, I guess this could easily be solved with a
> trigger, however, should one instead create a log table and log
> changes, etc?
>
> Hints and tips are apprecia
On 8/19/07, Michael Glaesemann <[EMAIL PROTECTED]> wrote:
> As you mention, you could use a trigger instead of explicitly setting
> updated_at to DEFAULT, which might be more convenient because you
> don't need remember to set the updated_at column explicitly on update.
>
> Whether or not this info
On Aug 19, 2007, at 14:04 , Robin Helgelin wrote:
When I started with MySQL I exploited their "bug" with timestamp
fields and always had a entered and updated field on my tables.
As I'm blissfully ignorant of MySQL's peculiarities, without a more
detailed explanation of what you're trying to
Hi,
When I started with MySQL I exploited their "bug" with timestamp
fields and always had a entered and updated field on my tables.
My question, is this interesting information enough to save on the
table itself? If so, I guess this could easily be solved with a
trigger, however, should one inst
