You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Stephen Mallette (Jira)" <ji...@apache.org> on 2021/11/19 12:25:00 UTC

[jira] [Closed] (TINKERPOP-2611) Prevent property(id,null) and addV(null)

     [ https://issues.apache.org/jira/browse/TINKERPOP-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephen Mallette closed TINKERPOP-2611.
---------------------------------------
    Fix Version/s: 3.6.0
         Assignee: Stephen Mallette
       Resolution: Done

> Prevent property(id,null) and addV(null)
> ----------------------------------------
>
>                 Key: TINKERPOP-2611
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2611
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.5.1
>            Reporter: Stephen Mallette
>            Assignee: Stephen Mallette
>            Priority: Minor
>              Labels: breaking
>             Fix For: 3.6.0
>
>
> for {{g.addV().property(id,null)}} isn't quite the same as the {{String}} key version because the {{id}} can't be {{null}} and it can't behave like a removal for graphs that don't support null values. allow this might also create hard to figure out bugs where a variable for the {{id}} gets set to {{null}} accidentally and random data gets created rather than getting an error. There is a similar argument to be made for {{addV(null)}}.
> at this time, there is a test that enforces this behavior so to remove that changes behavior which means we probably need to save this for a breaking change.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)