I did few more tests and it appear that property collate is tightly
connected with index collate:
1. After creating ci index, property becomes ci too
2. Creating index on ci property automatically makes index ci
3. Changing property collate affect already created indexes (e.g. making
property ci will make all existing indexes on this property ci too)
Maybe it would be helpful to someone
пятница, 12 июня 2015 г., 21:38:20 UTC+6 пользователь xvik написал:
>
> Yes, this is the behaviour I see.
> But, if I look in scheme:
>
> db.getMetadata().getSchema().getClass('Test').getProperty('foo').getCollate()
>
>
> There will be default collate. For me, it seems as an inconsistent state.
> That's why I'm asking what is expected behaviour (by design). Is it a bug
> or not.
>
> пятница, 12 июня 2015 г., 18:59:48 UTC+6 пользователь
> [email protected] написал:
>>
>> Hi,
>> I think that the property and the index are dependent.
>> If you create a property foo not ci and you create an index ci
>> when you run the query "select from Test where foo='test' you
>> get both records with 'test' and 'Test'
>>
>> Regards,
>> Alessandro
>>
>
--
---
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.
