Skip to content
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

finish range literal [*] [*2] [*..] [*2..] [*..2] #2027

Merged
merged 1 commit into from
Sep 13, 2023

Conversation

AEsir777
Copy link
Contributor

@AEsir777 AEsir777 commented Sep 12, 2023

  • finish range literal [*], [*2], [2..], [..2], [..]
  • fix all the test cases

@AEsir777 AEsir777 force-pushed the kebing-range-literal branch 2 times, most recently from ede0886 to bb88cd6 Compare September 12, 2023 21:44
@codecov
Copy link

codecov bot commented Sep 12, 2023

Codecov Report

Patch coverage: 100.00% and project coverage change: +0.04% 🎉

Comparison is base (defa82b) 90.04% compared to head (64c425e) 90.08%.
Report is 2 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2027      +/-   ##
==========================================
+ Coverage   90.04%   90.08%   +0.04%     
==========================================
  Files         918      919       +1     
  Lines       33125    33257     +132     
==========================================
+ Hits        29826    29961     +135     
+ Misses       3299     3296       -3     
Files Changed Coverage Δ
src/binder/bind/bind_graph_pattern.cpp 95.62% <100.00%> (+0.04%) ⬆️
src/parser/transform/transform_graph_pattern.cpp 93.61% <100.00%> (+0.43%) ⬆️

... and 22 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@AEsir777 AEsir777 force-pushed the kebing-range-literal branch 3 times, most recently from b7c08db to 1f7012b Compare September 13, 2023 16:44
@AEsir777 AEsir777 changed the title finish range literal [*] [*2] finish range literal [*] [*2] [*..] [*2..] [*..2] Sep 13, 2023
Copy link
Contributor

@andyfengHKU andyfengHKU left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't forget to rebase and squash

@@ -0,0 +1,121 @@
-GROUP TinySnbReadTest
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Move this test file to var_length_extend/

--

-CASE SingleUpperBound
-STATEMENT MATCH(a:person {fName: "Alice"})-[e:knows*..2]->(b:person) RETURN e;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe just do a COUNT(*) here. I feel the ground truth is a bit long. Though this is up to u.

Dan
-STATEMENT MATCH(a:person {fName: "Greg"})-[e:knows*..1]->(b:person) RETURN b.fName;
---- 0
# Different results from standard OpenCypher: 0 should be allowed
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove

if (!recursiveInfo->upperBound.empty()) {
upperBound = TypeUtils::convertToUint32(recursiveInfo->upperBound.c_str());
}

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove empty line.

You are now checking lowerBound <= limit then upperBound <= limit.

I guess you can just check lowerBound <= upperBound and then upperBound <= limit. This just comes to my mind that we didn't validate lowerBound <= upperBound.

@AEsir777 AEsir777 merged commit 417e86d into master Sep 13, 2023
10 checks passed
@AEsir777 AEsir777 deleted the kebing-range-literal branch September 13, 2023 22:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants