-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
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
Not possible to select attribute with name status #187
Comments
do you have an example script? |
For query builder? It's really simple, only:
Schema is also really simple: |
can you post the schema also? and some data thanks |
Can you run this script against the Orientdb 2.2.4? with the default database? const OrientJS = require('orientjs'),
server = OrientJS({ host: 'localhost', port: 2424 }),
db = server.use({ name: 'GratefulDeadConcerts', username: 'admin', password: 'admin' });
db.open().then(function(){
db.select('name').from("OUSer").all().then(function(res){
console.log(res);
server.close();
});
}) Thanks |
Sure, I receive
and I am using Orientdb 2.2.4 :-) |
So the projections seems to work if you can share your dataset i can inspect it further. You can send me some example here e.risa@orientdb.com Thanks |
I just sent you dataset to your email. Thanks |
the problem is that you are using the decimal type that is not yet supported by the new native serializer/deserializer. |
Ok, thank you, i will migrate it. But you should also add this restrictions to the documentation :-) Jan |
What is the best way to convert from Decimal to Double? Seems to be not possible to change it only in schema |
hi @janjilek |
Great! |
When I try to execute query "select status from Gift" via query builder, I receive only following response:
{ '@type': 'd',
'@Rid': { [String: '#-2:99'] cluster: -2, position: 99 },
'@Version': 0 }
As you can see, status is missing. When I try to execute it in console, everything works well. When I try to execute it on OrientDB 2.1.16, everything is fine. The problem is only with driver 2.2 and OrientDB 2.2 (.4)
Regards
Jan
The text was updated successfully, but these errors were encountered: