The WinFS newsgroup seems to have died, so I'll try posting my question here as well.
I notice that some of the entities defined in the custom schema samples have properties obviously carried over from the original database schema, like OrderID or ProductID.
Is this the way to go if I'm designing a custom schema It seems wrong somehow. Shouldn't I be using Links to associate items, rather than relying on ID properties
Which leads on to my second question: How do I do one-to-many relations For example, if I had a Customer item and a bunch of Order items, do I have a property in my Customer of type StorageSearcher<Order>, and a property on my Order of type Customer Or is there a way to declare Links and/or Associations so that they define a one-to-many relationship
Thanks,
Matt
WinFS "Identity" Properties and One-to-Many Links
satishdayal
well that choice to use original field names was only a way to show how it is simple now to work with data that was previosly in SQL Server format.
You can create one-to-many relations through InlineTypes
Peter Beresford
Thanks for the reply, Daniel.
I have seen inline types. Can an inline type be referenced/accessed as if it is a full-blown Entity I mean, I might have a "Publisher" which publishes many "Books". If "Book" is an inline type (since publisher-to-book is a one-to-many relationship) can I still get to my Book objects without needing to know their publisher