Open GoogleCodeExporter opened 9 years ago
I should have read that last section again :)
In Objectify 4.1 this worked great, but after upgrading to 5.x, Objectify
CHECKS if the key is set (which is not the case) and then throws an exception
without calling the OnSave method. Is this intended behavior? Am I missing
something?
Original comment by mann.mue...@gmail.com
on 13 Jun 2014 at 12:46
It is intended behavior. Updating @Id or @Parent is not supported in v5. Dev
Docs say, "Caution: You can't update @Id or @Parent fields in a @OnSave
callback"
https://code.google.com/p/objectify-appengine/wiki/LifecycleCallbacks
Original comment by ashish.a...@gmail.com
on 14 Jul 2014 at 4:04
Okay, I did not see this. Would be cool though in cases where the entity key is
aggregated from field-values. Any plans changing this some time?
Original comment by mann.mue...@gmail.com
on 14 Jul 2014 at 4:10
Original comment by lhori...@gmail.com
on 3 Oct 2014 at 6:00
Original issue reported on code.google.com by
mann.mue...@gmail.com
on 13 Jun 2014 at 12:44