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
In the PR, I implement the basic property existence check based on the property name, but it doesn't check property expression.
To Reproduce
The expected SQL result:
statement ok
create table person (name varchar, lastname varchar); insert into person values ('Alice', 'Foo');
statement ok
-create property graph pg vertex tables (person properties (name));
query I
-from graph_table (pg match (p:person) columns (p.name || p.name as name));
----
AliceAlice
statement error
-from graph_table (pg match (p:person) columns(p.name, p.name || p.lastname));
----
BinderException: p.notregistered is not a registered property for label person in property graph pg
OS:
ubuntu 22.04
DuckDB Version:
c380346433
DuckDB Client:
build from scratch
Full Name:
Hao
Affiliation:
N/A
How did you load the extension?
Built from source
Did you include all relevant data sets for reproducing the issue?
Yes
Did you include all code required to reproduce the issue?
Yes, I have
Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?
Yes, I have
The text was updated successfully, but these errors were encountered:
What happens?
A followup issue for #190
In the PR, I implement the basic property existence check based on the property name, but it doesn't check property expression.
To Reproduce
The expected SQL result:
OS:
ubuntu 22.04
DuckDB Version:
c380346433
DuckDB Client:
build from scratch
Full Name:
Hao
Affiliation:
N/A
How did you load the extension?
Built from source
Did you include all relevant data sets for reproducing the issue?
Yes
Did you include all code required to reproduce the issue?
Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?
The text was updated successfully, but these errors were encountered: