Mark, I second Jonathon that a surogate key is the way to go for simplifying relations you may have to your product table, you could ensure unicity with an unique constraint (which is supported via UniqueKey property AFAIR).
Also, in the sample you gave, updating product's attributes which compose the key will not be possible: it's not possible to update a primary key, if you have any other attributes that doesn't compose the key, you are free to update them as normal properties/relations. Creation or deletion scenario are supported with the CompositeKey mapping though. Hope this make sense > Gauthier I used the 'CompositeKey' approach and as far as i am seeing, > the schema was created as expected, however i still need to create, update > and delete some records. > Thanks a lot for your help > > *note*: All those that are in the same problem that i was, please feel > free to drop me an email an i will send you the code --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" 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/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
