Glad I was of some help.
I think it is a bug, but it is for the OrientDB devs to decide.
I am just exploring OrientDB and faced similar issues. That's why suggested
a few things.
On Friday, 5 June 2015 15:37:38 UTC+5:30, MV-dev1 wrote:
>
> Kapil -- YOUR SUGGESTION GOT ME TO THE ANSWER.
>
> With the ETL using the mixed case index name that exactly matched the
> imported field name then everything works.
>
> In ETL, changed...
>
> indexes: [{"class":"Player", "fields":["PlayerID:integer"], "type":
> "UNIQUE" }]
>
> to
>
> indexes: [{"class":"Player", "fields":["PlayerId:integer"], "type":
> "UNIQUE" }]
>
>
>
> and now everything works, with any case.
>
>
>
>
>
> *SELECT FROM Player WHERE PlayerId = 99SELECT FROM player WHERE playerid =
> 99SELECT FROM PLAYER WHERE PLAYERID = 99SELECT FROM PlAyER WHERE pLaYeRiD =
> 99*
> *??>> So, this is a bug, right?*
>
> On Friday, June 5, 2015 at 12:33:35 PM UTC+3, MV-dev1 wrote:
>>
>>
>> I'll make these changes, blow away the database and import again.
>>
>> On Friday, June 5, 2015 at 12:07:30 PM UTC+3, Kapil Ranade wrote:
>>>
>>> Another suggestion, try using PlayerID instead of PlayerId
>>> (Case-sesitive).
>>>
>>>>
>>>>
--
---
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.
