4 ms·

Beware, this behavior lets you shoot yourself in the foot because when you conduct your job, you might be working with a stale object that's changed since the j

Beware, this behavior lets you shoot yourself in the foot because when you conduct your job, you might be working with a stale object that's changed since the job went on the queue.

DouweM 12y ago
That's incorrect. This is not YAML-style full object serialization, but rather a global ID being sent along the wire that is transparently looked up at deserialization. See the example here: https://github.com/rails/rails/tree/master/activejob#globalid-support https://github.com/rails/rails/tree/master/activejob#globali...
- hayksaakian 12y ago
  Is it? I assumed it worked like delayed_job which gave me issues due to the problem I mentioned.
  - DouweM 12y ago
    It is! That's the exact problem ActiveJob+GlobalID tries to solve.
    - hayksaakian 12y ago
      I suppose I was mistaken then, thanks for helping me understand.
  - volkk 12y ago
    why bother spreading false information without even taking a minute to read into what it actually does?