Some further information on the problem below:
- The user was created with the value 142253104340300199 assigned to the ID
field
- In OrientDB Studio, it displays the ID as 142253104340300200, yet
fetching the document by this ID fails, it has to be fetched with the ID
originally assigned, namely 142253104340300199. So even though it DISPLAYS
a different id, it seems like it did STORE the original, correct id
- When performing a query from within Studio, the resulting "raw" json also
returns 142253104340300200 as the id of the user
- When performing the same query from the Java API, the id returned for the
user is the correct one. In fact, all seems fine when using the Java API,
and the display/query problem only presents itself in Studio
Hope that helps to isolate the problem
W
On Thursday, January 29, 2015 at 1:45:57 PM UTC+2, wkrause wrote:
>
> Given the following document in my DB ...
>
> {
> "@class": "User",
> "id": 142253104340300200,
> "name": "Name",
> "surname": "Surname",
> ... etc ...
> }
>
> ... the query "select from User where id = 142253104340300200" returns no
> results, to my surprise.
>
> But when I issue the following query "select from User where id =
> 142253104340300199" I get the above document in the result.
> There are no other documents in DB, so I cannot get something by that ID
> accidentally.
>
> This is a serious enough issue for me not to be able to proceed with
> OrientDB. I hope that it is a mistake on my side?
>
> The above document was inserted against a schema that looks as follows:
>
> create class User extends V
> create property User.id long
> create property User.name string
> ... etc ... (the rest is ommitted as it's irrelevant
>
> I am on version 2.0.1 of OrientDB
>
>
>
--
---
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.
