We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#1: SELECT username FROM User WHERE username = "Bob"
"result": [ { "@type": "d", "@rid": "#11:1", "@version": 0, "username": "Bob", "@fieldTypes": "rid=x" } ]
#2: SELECT @Rid, username FROM User WHERE username = "Bob" "result": [ { "@type": "d", "@Rid": "#11:1", "@Version": 0, "rid": "#11:1", "username":"Bob" "@fieldTypes": "rid=x" } ]
## Actual behavior **#1**: SELECT username FROM User WHERE username = "Bob"
"result": [ { "@type": "d", "@Rid": "#-2:0", "@Version": 0, "rid": "#11:1", "username": "Bob", "@fieldTypes": "rid=x" } ]
**#2**: SELECT @rid, username FROM User WHERE username = "Bob" "result": [ { "@type": "d", "@rid": "#-2:0", "@version": 0, "rid": "#120:3750", "rid": "#11:1", "@fieldTypes": "rid=x" } ]
See queries above.
The text was updated successfully, but these errors were encountered:
Hi @RubenVermeulen
This is a legacy behavior that unfortunately cannot be changed in v 2.2.
If you want to include/exclude fields from JSON you can use fetch plans: http://orientdb.com/docs/2.2.x/Fetching-Strategies.html
In v 3.0 it's already fixed.
Thanks
Luigi
Sorry, something went wrong.
luigidellaquila
No branches or pull requests
OrientDB Version: 2.2.22
Java Version: 1.8.0_131
OS: Zorin OS 12.1, Ubuntu 16.04 LTS
Expected behavior
#1: SELECT username FROM User WHERE username = "Bob"
#2: SELECT @Rid, username FROM User WHERE username = "Bob"
"result": [
{
"@type": "d",
"@Rid": "#11:1",
"@Version": 0,
"rid": "#11:1",
"username":"Bob"
"@fieldTypes": "rid=x"
}
]
"result": [
{
"@type": "d",
"@Rid": "#-2:0",
"@Version": 0,
"rid": "#11:1",
"username": "Bob",
"@fieldTypes": "rid=x"
}
]
Steps to reproduce
See queries above.
The text was updated successfully, but these errors were encountered: