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
"NOTE 130 — Unlike most regular expression languages, is not equivalent to the quantifier {0,1}: the quantifier {0,1} exposes variables as group, whereas does not change the singleton variables that it exposes to group. However, does expose any singleton variables as conditional singletons."
The way to translate this would be with a LEFT OUTER JOIN
select*from student s
join know k ons.id=k.srcjoin student s2 ons2.id=k.dstleft join studyat sa onsa.studentid=s.idjoin university u onsa.universityid=u.id;
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Many SNB queries such as IC1, IC4, IC5 (see https://github.com/cwida/duckpgq-experiments/issues/26 for all) require optional matches. The PGQ syntax would be
()-[]->?()
.Snippet from the SQL/PGQ specification section 10.6:
"NOTE 130 — Unlike most regular expression languages, is not equivalent to the quantifier {0,1}: the quantifier {0,1} exposes variables as group, whereas does not change the singleton variables that it exposes to group. However, does expose any singleton variables as conditional singletons."
The way to translate this would be with a
LEFT OUTER JOIN
The text was updated successfully, but these errors were encountered: