Thanks for your reply
@Julian
each message belongs to a single user only. Its not shared between users. So
I am creating entity group for the list of messages per user. And other
reason is if I am not using entity group for messages per user then I am
getting problem in saving list of messages (
I would just add one short comment to this and that is there are other
good reasons to use an entity group besides the transaction support.
First, the parent child relationship can be a powerful construct from
a design perspective. Second, queries "within" an entity group will
tend to be fast as I
Your model won't work if one message can have several recipients. Is
this OK?
And is there a particular reason why you create an entity group for a
user and its messages ?
You only need an entity group if you plan to update different entities
transactionally.
Also, you might be interested by this
