>From the release notes: •Removed SetAttribute - SetAttribute was a stop-gap measure to allow people to use Fluent NHibernate when we didn't support the attributes they needed. We've now gone to a great length to support all of the main attributes in the fluent interface, so you shouldn't need this anymore. If there are any attributes you need that we've missed, let us know (or even better, send us a pull request/patch)
OK - there still seem to be several scenarios - such as the component composite ID - where the proper attributes aren't supported. Given that the SetAttribute was the only way to get around this limitation, why would you guys make a breaking change like that? I mean, what was the upside that balanced the downside of making it so that a bunch of implementations broke with no workaround? Just trying to understand, Andrew p.s. - How can I use a component/composite ID? Doesn't seem to be any way now. And in my situation, I'm writing a SaaS application where the ID has a partitionKey in it, so it's perfectly appropriate to be using a composite/component key... Thanks, Andrew -- You received this message because you are subscribed to the Google Groups "Fluent NHibernate" 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/fluent-nhibernate?hl=en.
