{"action":"created","issue":{"url":"https://api.github.com/repos/arangodb/arangodb/issues/1225","labels_url":"https://api.github.com/repos/arangodb/arangodb/issues/1225/labels{/name}","comments_url":"https://api.github.com/repos/arangodb/arangodb/issues/1225/comments","events_url":"https://api.github.com/repos/arangodb/arangodb/issues/1225/events","html_url":"https://github.com/arangodb/arangodb/issues/1225","id":55470857,"number":1225,"title":"Naming Conventions for attribute names in ArangoDB","user":{"login":"kevinprotoss","id":3446906,"avatar_url":"https://avatars.githubusercontent.com/u/3446906?v=3","gravatar_id":"","url":"https://api.github.com/users/kevinprotoss","html_url":"https://github.com/kevinprotoss","followers_url":"https://api.github.com/users/kevinprotoss/followers","following_url":"https://api.github.com/users/kevinprotoss/following{/other_user}","gists_url":"https://api.github.com/users/kevinprotoss/gists{/gist_id}","starred_url":"https://api.github.com/users/kevinprotoss/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kevinprotoss/subscriptions","organizations_url":"https://api.github.com/users/kevinprotoss/orgs","repos_url":"https://api.github.com/users/kevinprotoss/repos","events_url":"https://api.github.com/users/kevinprotoss/events{/privacy}","received_events_url":"https://api.github.com/users/kevinprotoss/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/arangodb/arangodb/labels/documentation","name":"documentation","color":"e102d8"},{"url":"https://api.github.com/repos/arangodb/arangodb/labels/question","name":"question","color":"AA3333"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-01-26T11:12:09Z","updated_at":"2015-01-30T11:08:50Z","closed_at":"2015-01-30T11:08:50Z","body":"Hi,\r\n\r\nI found one limitation in the documentation.\r\n\r\n```\r\nAttribute names should not start with the at-mark (@). The at-mark at the start of attribute names is reserved in ArangoDB for future use cases.\r\n```\r\n\r\nI need to make sure whether could we use `@` in the attribute names. Certainly, it's supported now in the db. However, if it won't in the future version, that would be a problem.\r\n\r\nWhy can not use other character for future use cases? As I know `@` in JSON is much more important than other reserve keywords. e.g., JSON-LD uses always attribute names starting with `@`.\r\n\r\nBg,\r\nKevin\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/arangodb/arangodb/issues/comments/72186045","html_url":"https://github.com/arangodb/arangodb/issues/1225#issuecomment-72186045","issue_url":"https://api.github.com/repos/arangodb/arangodb/issues/1225","id":72186045,"user":{"login":"jsteemann","id":1423118,"avatar_url":"https://avatars.githubusercontent.com/u/1423118?v=3","gravatar_id":"","url":"https://api.github.com/users/jsteemann","html_url":"https://github.com/jsteemann","followers_url":"https://api.github.com/users/jsteemann/followers","following_url":"https://api.github.com/users/jsteemann/following{/other_user}","gists_url":"https://api.github.com/users/jsteemann/gists{/gist_id}","starred_url":"https://api.github.com/users/jsteemann/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jsteemann/subscriptions","organizations_url":"https://api.github.com/users/jsteemann/orgs","repos_url":"https://api.github.com/users/jsteemann/repos","events_url":"https://api.github.com/users/jsteemann/events{/privacy}","received_events_url":"https://api.github.com/users/jsteemann/received_events","type":"User","site_admin":false},"created_at":"2015-01-30T11:08:50Z","updated_at":"2015-01-30T11:08:50Z","body":"To clear the confusion that may have arisen, I just discussed that with @fceller: \r\n- attribute names starting with `@` are supported by ArangoDB and should work, so they can be used by end users if required\r\n- the section about them being reserved for future use cases has been removed from the manual (at least in the source code, the online manual will be updated eventually). \r\n- we still do not encourage the usage of `@`-prefixed attribute names because in AQL, identifiers starting with the at-mark will be interpreted as bind parameters. To use an at-mark-prefixed attribute name in AQL, it will need to be enclosed in backticks. The same is true for other attribute names by the way, e.g. attribute names including spaces.\r\n\r\nLong story short: at-prefixed attributes can be used, though they will need some attention when used in AQL queries.\r\n\r\nI think this should provide everyone with enough information to make a good decision about whether it is worth to use such attribute names in their applications."}}