VERY INTERESTING... (results below)
*SELECT FROM Player WHERE PlayerId >= 99 AND PlayerId <= 99*
Basically the results are the same.
x SELECT FROM Player WHERE Player.PlayerId >= 99 AND Player.PlayerId <= 99
x SELECT FROM Player WHERE PlayerID >= 99 AND PlayerID <= 99
x SELECT FROM Player WHERE PlayerId = 99
x SELECT FROM Player WHERE PlayerID = 99
I also tried using the index but must not be doing that correctly....
*SELECT FROM INDEX:Player.PlayerID where key = 99*
2015-06-05 12:16:43:572 SEVERE Internal server error:
com.orientechnologies.orient.core.sql.OCommandSQLParsingException: Error on
parsing command at position #0: Encountered " ":" ": "" at line 1, column
18.
It is strange that this doesn't work when that's how the label is displayed
in the schema.
SELECT * FROM Player WHERE PlayerID >= 99 AND PlayerID <= 99
But you may be onto something because this is what the raw results look
like...
{
"result": [
{
"@type": "d",
"@rid": "#11:100",
"@version": 1,
"@class": "Player",
*"PlayerId": 99,*
My MSSQL database has PlayerId (lower case 'd') and my OETL has an upper
case 'D'.
indexes: [{"class":"Player", "fields":["PlayerID:integer"],
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.
