Nested projection using wildcard problem

Open
#9,263 2 comments 0 reactions 1 assignee View on GitHub

@luigidellaquila is already working on this.

Since Jun 1, 2020.

Assessment

This issue has not been assessed yet.

Description

OrientDB Version: 3.0.31
Java Version: 1.8
OS: linux

Expected behavior

If there is a name attribute then I would expect na* in a nested projection to include something like "name":"some name"

Actual behavior

In my case it returns "na":null

Steps to reproduce

create class Test_1 extends V
create class Test_2 extends V
INSERT INTO Test_1 CONTENT {"name": "Joe", "surname": "Miner"}
INSERT INTO Test_2 CONTENT {"name": "Jay", "surname": "Miner"}
CREATE CLASS test_edge1 EXTENDS E
create edge test_edge1 from (select from Test_1 where name ="Joe") to (select from Test_2 where name ="Jay")

select out(test_edge1):{*} from Test_1  --> Works
select out(test_edge1):{*,!in_*} from Test_1  --> Works
select out(test_edge1):{!in_*} from Test_1  --> Works
select out(test_edge1):{name} from Test_1  --> Works
select out(test_edge1):{surname} from Test_1  --> Works
select out(test_edge1):{!na*} from Test_1  --> Works
select out(test_edge1):{*,!na*} from Test_1  --> Works

select out(test_edge1):{na*} from Test_1  --> Doesn't Work
select out(test_edge1):{sur*} from Test_1  --> Doesn't Work
Dominant language
Java
Stars
5k
Forks
868
Avg merge
15h 6m
Merged PRs (30d)
18

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from orientechnologies/orientdb

All issues in orientechnologies/orientdb

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.