On Fri, 25 Aug 2000, Tom Lane wrote: > I think you are getting burnt by premature constant folding --- see > nearby discussion of how to define a column default that gives the > time of insertion. You need to write this as > NEW.ChangedAt := now(); > to prevent the system from reducing timestamp('now') to a constant > when the function is first executed. This doesn't work, too. It just puts allways the constant time when the function was created into the database. May be it has to be escaped in somw way?? I don't know how to follow hlefebvre's hint to "put null" into the field. Bay the way: If we once solved the problem it might be a topic for the FAQ, perhaps? Kind regards Andreas.
- [SQL] Date of creation and of change Andreas Tille
- Re: [SQL] Date of creation and of change hlefebvre
- [SQL] Re: Date of creation and of change Andreas Tille
- Re: [SQL] Re: Date of creation and of change hlefebvre
- [SQL] Re: Date of creation and of change Andreas Tille
- Re: [SQL] Re: Date of creation and of ... hlefebvre
- [SQL] Re: Date of creation and of ... Andreas Tille
- Re: [SQL] Re: Date of creation... hlefebvre
- Re: [SQL] Re: Date of creation... Tom Lane
- Re: [SQL] Re: Date of creation... Andreas Tille
- Re: [SQL] Re: Date of creation... hlefebvre
- Re: [SQL] Re: Date of creation... hlefebvre
- [SQL] Re: Date of creation and... Andreas Tille
- [SQL] Re: Date of creation and of change Andreas Tille