Skip to content

livequery api does not normelize rid #35

@imdark

Description

@imdark

when a result is retured from a live query api update call it looks like this:
{ content: { '@type': 'd', '@Class': 'players', name: 'Maxwell', score: 120 }, type: 'd', cluster: 12, position: 41, version: 0 } }

then the using application needs to combine cluster and postion to get the rid as described here:
http://orientdb.com/docs/2.0/orientdb.wiki/Tutorial-Record-ID.html

this seems like an uncositstent api issue since objects returned from '*' selects do have @Rid as a field

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions