Triggering interceptors for mass updates

[runningjustin]

I have an interceptor to set updatedBy. Since interceptors run for update() but not createUpdate(), is there a way I can leverage the interceptor (or similar concept) when updating many records at once? Or do I simply just need to add updatedAt to my createUpdate statement? Would be nice if this is something I can do generically rather than remembering to pass the value with each createUpdate.

Thanks!

[babyfish-ct]

The DraftInterceptor needs to construct a new object for updates (createUpdate does not create objects) and query the old object (which may be null). Developers can even determine whether the upcoming operation is an insert or an update based on whether the old object is null. The save command is a powerful solution.

When you use createUpdate, you might update a large number of objects at once, and in such cases, queries should be avoided. Therefore, createUpdate is a solution optimized for performance.

Adding this feature is not difficult, but it would completely undermine the original design purpose of createUpdate. Thus, the more recommended approach is to manually update updateBy within createUpdate.