{"action":"created","issue":{"url":"https://api.github.com/repos/tinkerpop/tinkerpop3/issues/518","labels_url":"https://api.github.com/repos/tinkerpop/tinkerpop3/issues/518/labels{/name}","comments_url":"https://api.github.com/repos/tinkerpop/tinkerpop3/issues/518/comments","events_url":"https://api.github.com/repos/tinkerpop/tinkerpop3/issues/518/events","html_url":"https://github.com/tinkerpop/tinkerpop3/issues/518","id":55592911,"number":518,"title":"Consider making edges immutable","user":{"login":"BrynCooke","id":747836,"avatar_url":"https://avatars.githubusercontent.com/u/747836?v=3","gravatar_id":"","url":"https://api.github.com/users/BrynCooke","html_url":"https://github.com/BrynCooke","followers_url":"https://api.github.com/users/BrynCooke/followers","following_url":"https://api.github.com/users/BrynCooke/following{/other_user}","gists_url":"https://api.github.com/users/BrynCooke/gists{/gist_id}","starred_url":"https://api.github.com/users/BrynCooke/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/BrynCooke/subscriptions","organizations_url":"https://api.github.com/users/BrynCooke/orgs","repos_url":"https://api.github.com/users/BrynCooke/repos","events_url":"https://api.github.com/users/BrynCooke/events{/privacy}","received_events_url":"https://api.github.com/users/BrynCooke/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/tinkerpop/tinkerpop3/labels/enhancement","name":"enhancement","color":"009800"},{"url":"https://api.github.com/repos/tinkerpop/tinkerpop3/labels/structure","name":"structure","color":"bfdadc"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-01-27T09:14:14Z","updated_at":"2015-01-27T18:23:00Z","closed_at":null,"body":"Currently TP has mutable edges.\r\n\r\nDiscussions in https://github.com/tinkerpop/tinkerpop3/issues/489 indicate that this may not be a good idea.\r\n\r\nMost SQL developers coming to TP will think that edges are equivalent to junction tables and therefore choose a bad design for their graph.\r\n\r\nAlso a history strategy becomes difficult to implement if edges are mutable.\r\n\r\nThoughts?\r\n\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/tinkerpop/tinkerpop3/issues/comments/71699429","html_url":"https://github.com/tinkerpop/tinkerpop3/issues/518#issuecomment-71699429","issue_url":"https://api.github.com/repos/tinkerpop/tinkerpop3/issues/518","id":71699429,"user":{"login":"mbroecheler","id":758061,"avatar_url":"https://avatars.githubusercontent.com/u/758061?v=3","gravatar_id":"","url":"https://api.github.com/users/mbroecheler","html_url":"https://github.com/mbroecheler","followers_url":"https://api.github.com/users/mbroecheler/followers","following_url":"https://api.github.com/users/mbroecheler/following{/other_user}","gists_url":"https://api.github.com/users/mbroecheler/gists{/gist_id}","starred_url":"https://api.github.com/users/mbroecheler/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mbroecheler/subscriptions","organizations_url":"https://api.github.com/users/mbroecheler/orgs","repos_url":"https://api.github.com/users/mbroecheler/repos","events_url":"https://api.github.com/users/mbroecheler/events{/privacy}","received_events_url":"https://api.github.com/users/mbroecheler/received_events","type":"User","site_admin":false},"created_at":"2015-01-27T18:22:59Z","updated_at":"2015-01-27T18:22:59Z","body":"@BrynCooke I understand where you are coming from, but I don't think we necessarily need to take the conclusion of #489 that far. I think it is important to consider edges as atomic data elements but that does not necessarily mean we need them to be immutable. It's like a row in an RDBMS table - you can update the columns but you think of it as one row with one access level, one provenance record, etc."}}