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
It appears that as the TypeDB Java client is updated, and the TypeQL version has changed, the string representation of a query changed. There are places where the generators look for a substring in the query (e.g. RelationGenerator.java:104) that can no longer appear. The loader ends up just ignoring the data with a generated query like
insert
$null isa null,
has null "null";
The text was updated successfully, but these errors were encountered:
flyingsilverfin
changed the title
Generators can't validate query with latest TypeDB Java client
Generators can't validate query with updated TypeQL
May 10, 2022
## What is the goal of this PR?
As outlined in #54, a change in TypeQL meant that some of the `toString()` representations have changed. This PR reduces reliance on `toString()` for correctness, though more work needs to be done to eliminate the dependency.
## What are the changes implemented in this PR?
* Fix one `toString()` check that included a comma that no longer exists
* Replace to usages of `toString()` contains checks with operations over the TypeQL query object.
flyingsilverfin
changed the title
Generators can't validate query with updated TypeQL
Generators can't validate query with updated TypeQL version
May 10, 2022
It appears that as the TypeDB Java client is updated, and the TypeQL version has changed, the string representation of a query changed. There are places where the generators look for a substring in the query (e.g. RelationGenerator.java:104) that can no longer appear. The loader ends up just ignoring the data with a generated query like
The text was updated successfully, but these errors were encountered: