-
Notifications
You must be signed in to change notification settings - Fork 872
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
new bugs with traverse after fix #10281 #10292
Comments
mikhalov
changed the title
new bugs with traverse after fix https://github.com/orientechnologies/orientdb/issues/10281
new bugs with traverse after fix #10281
Aug 29, 2024
Hi, Thanks to report this, will check it. |
tglman
added a commit
that referenced
this issue
Sep 10, 2024
tglman
added a commit
that referenced
this issue
Sep 10, 2024
@tglman Checked the fix in the new release, but one case is still failing: @Test
void newApiVariable() {
String query = """
select $path.out('Owns')[0].name as name from (
select $current as person
from (select from Person where name = 'John Doe')
)
let
$person = person,
$path = (traverse out('Owns') from $current.$person)""";
try (OResultSet resultSet = db.query(query)) {
assertTrue(resultSet.hasNext());
while (resultSet.hasNext()) {
System.out.println(resultSet.next().toJSON());
}
}
}
|
Hi, Did you try to just use Regards |
@tglman, hi |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
OrientDB Version: 3.2.32
Java Version: 17
OS: Windows
After the fix #10281, several new bugs were discovered:
First Bug: It is still impossible to access a variable or result in the context using $current as was possible in the old API.
Second Bug: There is a bug when trying to access the result of a traversal using $path.out('Owns'). Specifically, the issue occurs when you attempt to reference the out('Owns') on the result of the traverse operation stored in the $path variable. This causes an error and does not work as expected.
Also, I am including tests for both bugs using the old and new APIs:
The text was updated successfully, but these errors were encountered: