It is simply not supported, yet, to define a composite key from a combination of attributes and references (to BasicType or Enum). If you need this you can add a request for improvement in jira. My standard answer for the reason is: "We have focused on the most important cases and will add more when needed."
/Patrik amphoras wrote: > > Hi, > > I am trying to test the equals() and hashCode() functionality in Sculptor > right now. From reading the documentation, I know that the behavior is > governed by setting certain fields in my objects as "key". > > Now, I have an object that contains a BigDecimal and an enum. Both of > these fields would logically make a composite natural key. However, the > DSL validator complains when I set the enum as "key". Can you explain the > reason for this error message? > > Thanks, > Polly > -- View this message in context: http://www.nabble.com/-Sculptor--natural-key-and-enums-tp19321107s17564p19333562.html Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Fornax-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fornax-developer
