I would like to know if this it's possible.
I have an Addresses Database, and both customers and providers have different addresses, but they should map to the same table, since they hold the same data.
If I map the collection with a <set one-to-many>, I think it would probably end duplicating entries, because it would not be able to distinguish the collection items, and their real parents.
I'm trying to avoid adding an id field for each collection mapped to this table.
Is there any neater way to implement this behaviour?
Thanks