Hi, I'd like to know the accepted approach to the following: I have a Customer object and a Downloads object. There is a one-to-one relationship between them. The downloads object is basically a class to encapsulate functionality for downloads. E.g. it has AddAlbumDownload(), AddTrackDownload() as well as a bunch of other helper methods. Moreover, it has multiple collections of types of downloads. So, I have decided to map from Customer to Downloads as a many-to-one in Customer. So, the Customer table has a DownloadsID. The thing is, my Downloads table only has one column, the PK. This seems kind of inefficient to me. Rather, I'd like to do something like add the DownloadsID to the Customer table similar to a component and have the many-to-one's in the child collections map back to this. Is there a recommended way of doing this? For clarity, here's the model
Customer has one Download Download has many AlbumDownload Download has many IndividualTrackDownload --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
