I just learnt that transactional tasks cannot be named. Why is that? It’s as though naming a task is an action on a different entity group, but “unnamed” tasks are actually given api-generated names.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I just learnt that transactional tasks cannot be named. Why is that? It’s as though naming a task is an action on a different entity group, but “unnamed” tasks are actually given api-generated names.
Task names are unique, so if you add a task named “foo”, subsequent adds of tasks named “foo” will fail. This check for uniqueness needs to be done within a transaction itself, so all named tasks in an application would have to have the same entity group.
If you’re trying to atomically enqueue tasks within a transaction then the tasks will have to have the same entity group as the other entities in the transaction and uniqueness check would not be reliable.