|location||San Jose, CA|
|visits||member for||2 years, 1 month|
|seen||Oct 2 '12 at 14:46|
I'm an Ruby developer, DevOps Engineer, and Linux Systems Engineer.
|bio||website||uberobert.com||visits||member for||2 years, 1 month|
|location||San Jose, CA||seen||Oct 2 '12 at 14:46|
Intuitive way to present chained 1-N relationships
I like your idea of separate lists and see why you would need two places to store them if you are assigning workers way before activities are created. Rather than showing every worker for the Activities, I'd just limit the query to the workers assigned to the workOrder with a where clause.