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
Is your feature request related to a problem? Please describe.
Using the same column at the insertion point will cause the previous value to be overwritten by the next value。
e.g.
given: insert vertex player (name,name) values "dragonchu":("chuchu",null);
when: fetch prop on player "dragonchu" yield properties(vertex);
then:
we will get NULL as name value but without any warning.
Describe the solution you'd like
Checking for duplicate columns in insert statements. It can prohibit this behavior like other databases or at least give some warning.
Additional context
We spent a day trying to troubleshoot this problem because my statements were automatically generated and the column names were not clear, resulting in two of the duplicate column names causing the inserted values to never meet expectations.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Using the same column at the insertion point will cause the previous value to be overwritten by the next value。
e.g.
given:
insert vertex player (name,name) values "dragonchu":("chuchu",null);
when:
fetch prop on player "dragonchu" yield properties(vertex);
then:
we will get NULL as name value but without any warning.
Describe the solution you'd like
Checking for duplicate columns in insert statements. It can prohibit this behavior like other databases or at least give some warning.
Additional context
We spent a day trying to troubleshoot this problem because my statements were automatically generated and the column names were not clear, resulting in two of the duplicate column names causing the inserted values to never meet expectations.
The text was updated successfully, but these errors were encountered: