On Thu, Sep 11, 2008 at 8:50 PM, Artacus <artacus@comcast.net> wrote:
>
>> How is it that you can declare the default value of a column on insert
>> but not on update?
>
> You can do this without triggers (at least on 8.3).
>
> UPDATE foo
> SET field1 = 2,
> field2 = default
> WHERE field3 = 22
>
> I just tested it and it will set the value back to the default. The caveat
> here is that it won't FORCE the value like it would with a trigger. So while
> the trigger would happen automatically, using this approach, you'd have to
> remember to also update that field any time you did an update.
Right, but now you've moved the complexity of timestamping updates
into the application layer, where it has to be propagated to all
update queries. Miss one and it won't get updated.
i wonder if you could do it with a rule?