on 2014 Oct 01 8:59 PM
Is there a way we can drop the index provided by OOB core-items.xml and replace it with a composite key? We want to drop the index on Customer.uid, mark it as non-unique in our custom item type MyCustomer (that extends Customer) and have a composite key on uid and a custom attribute. Is this possible and advisable?
That wouldn't make much sense because you MyCustomer
item would need to fulfill the 'contract' inherited from Customer
, which claims to have a unique uid
attribute. So all existing code base dealing with customers would expect that for a given uid only a single item would be found.
Can you elaborate a bit about your use case ? May be people around here can provide other ideas then.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
11 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.