On 10/04/2010, at 8:39 AM, AJ Mercer wrote: > yeah - I was wondering about datetimelastupdated too. > > Can I get confirmation from the team Daemom > > On 10 April 2010 00:42, Tomek Kott <[email protected]> wrote: > couldn't you use "datetimelastupdated" as a proxy? Since FC reads/sets that > data at the time it is locked (pretty sure), I think that would be exactly > what you're looking for... or am I misunderstanding it?
No, datetimelastupdated should only be updated on an update. Otherwise we'd have "touched" the object every time somebody opened an edit handler -- even if they hit cancel. Adding something like a datetimelocked would mean adding it to "types" abstract class, which in turn would mean adding it to *every* content type for now and forever after. I'm not sure there is enough benefit to the user. A better proxy might be to look at the user who locked it -- which we already do. But we could enhance this possibly by looking at whether or not the user is logged in, or at least how long ago they logged in. This would give you a good handle on whether or not there was a danger of overriding their work. -- geoff http://www.daemon.com.au/ -- You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry To unsubscribe, reply using "remove me" as the subject.
