Harish, I believe your contemplations are sort of why we are calling any names of properties "API names" and not the actual field names. If any "API name" of a property is changed (in our GUI, once it is finished), there will be a big fat red warning about that action changing API signatures/ definitions and basically breaking them. The person making a property name change must absolutely know what they are doing and have taken all possible consequences into consideration. In fact, in our system, only someone with a developer role will be able change the API name.
As for your question about changing the property name and what happens to the original index, that is a good one, which I'd also like to know the answer. I would guess a new index would need to be built, which would also be part of the warning we could give the developer, when the API name is changed. We are also looking at automatically building indexes too. So being sure what happens to the original index on a property name change is important. @Luigi - Thanks for the info and the metadata feature is still a great one, but I realized later, that my question was superfluous. That is because class and attribute metadata, in the sense of translated field names, shouldn't be stored in the records themselves or returned with them in the result sets. That would simply bloat the results unnecessarily. We'll need a layer of logic in our application to fit the field names to the result set accordingly. Thanks again though, for your great support! Scott -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
