Many to many best practice


#1

Hi,

I’m working on an Ember app that involves some many to many relationships. We have a legacy SQL data base with the following scenario which is exposed via a RESTful API.

Workers
  id
  name

Clients
  id
  name

WorkerClientHistory
  FK workerId
  FK clientID
  DATE assignmentDate

The WorkerClientHistory table is not exposed by the API because it is a server side entity with new records being written via triggers when new records are added to either Clients or Workers.

Because the WorkerClientHistory records are embedded in the Client and Worker JSON data I have written an Ember model for worker-client-history but when I loop over the list of these records it just lists lots of unresolved promises.

I know I haven’t posted any code but I’m just trying to get some ideas on what is considered best practice in this situation and whether my approach is valid.

Thanks Rob