How to update records without triggering the updatedAt timestamp?

[Renand]

Hello,
I need to update some records without triggering the automatic updatedAt timestamp. Is there a way to do this?
Thank you in advance.

V 2.5.1

[dbelanger]

On the update method, there is an argument called allowExplicitTimestamps. You can set that to true and force the old updatedAt like so:

post = model("post").findByKey(params.key);
post.update(
    createdAt=post.createdAt,
    updatedAt=post.updatedAt,
    deletedAt=post.deletedAt,
    properties=PARAMS.post
);

This example of course assumes the post params you need to update are coming in through a post struct in your PARAMS.

[Renand]

Thank you !

You confirm that it is possible to use allowExplicitTimestamps only for certain updates ?

, e.g.:

post = model("post").findByKey(params.key, allowExplicitTimestamps=false); post.update(

createdAt=post.createdAt,
updatedAt=post.updatedAt,
deletedAt=post.deletedAt,
properties=PARAMS.post

);

[Renand]

Sorry, I misunderstood. The cleanliness: allowExplicitTimestamps is part of the update() function — I have this code, but it doesn’t work.

local.user = model("user").findByKey(key=session.user.id);
if (IsObject(local.user)) {
local.user.action = params.action;
local.user.logType = "success";
local.user.rememberToken = "";
local.user.update(allowExplicitTimestamps=true, updatedAt=local.user.updatedAt);
}

[zainforbjs]

@Renand The approach shown here (using the update() method with the allowExplicitTimestamps argument to prevent updatedAt from being changed) does work in the latest Wheels 3.0 version. Wheels 3.0 includes the underlying feature that lets you explicitly set timestamp columns with allowExplicitTimestamps=true when updating records — so you can keep your updatedAt value untouched when needed.

[zainforbjs]

@Renand Thanks for reporting this. We’ve tested it and were able to reproduce the issue as well. We’re actively working on a fix and will keep you updated. Appreciate you bringing this to our attention.