You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this recovers a 'list' of @rids which, intuitively at least, should match:
select @rid from (select @rid from CLASS)
Actual behavior
The first result, as stated above, is a list of @rids whereas the second is NULL.
Steps to reproduce
Run the queries above.
Perhaps I've missed it, but could not find an account of this behavior in the docs.
If such an account exists, it would be nice to be pointed to it. (I am aware of this).
I personally find this behaviour to be quite counterintuitive. Moreover, it is quite problematic
for the Python driver which relies somewhat heavily @rids to construct its representation
of vertices and edges.
Thanks!
The text was updated successfully, but these errors were encountered:
OrientDB Version: 3.0.7
Java Version: java 10.0.2
OS: macOS 10.13.6
Expected behavior
Take the following for example:
this recovers a 'list' of
@rid
s which, intuitively at least, should match:Actual behavior
The first result, as stated above, is a list of
@rid
s whereas the second is NULL.Steps to reproduce
Run the queries above.
Perhaps I've missed it, but could not find an account of this behavior in the docs.
If such an account exists, it would be nice to be pointed to it. (I am aware of this).
I personally find this behaviour to be quite counterintuitive. Moreover, it is quite problematic
for the Python driver which relies somewhat heavily
@rid
s to construct its representationof vertices and edges.
Thanks!
The text was updated successfully, but these errors were encountered: