[Discussion] Multiple index in the meta model

[lmouline]

Currently we can create a class with multiple index.
However, this is not really managed.

For example, with the following meta model:

class kmf.test.Personne {
    att name : String with index
    att firstName : String with index
    att birthMonth : String
}

If we create a person P1(Name1,FirstName1) and a person P2(Name1,FirstName2) and we use the find method with only a selector on the name, we just get one of the person (whereas I expect 2 persons).

So, as a next feature it could be possible to have an index on a "n-uplet".

Currently, @thomashartmann thinks that we should forbid multiple index in a class.

[dukeboard]

Hello,

Right now, the n-uplet is activated in the current snapshot. Therefore if there is a bug as you say i would more bet on a problem on the hashing function. I will check quickly