Using a different character to "/" in node ids. about arangodb

[jsteemann]

@Kafkalasch : there is no option available to configure the character that is used to separate the collection name part and the key part in ArangoDB document ids. The character is hard-coded to /, and many components in ArangoDB rely on this character. So I think it is safe to assume that it will stay this way for the foreseeable future.

In order to use a document id in URLs, it will need to be URL-encoded, e.g. /orders/mycollection/123 would become /orders/%2f123 or such. This does not only apply to the forward slash, but also to some other punctuation characters which could be used in URLs.
There is also the possibility of doing the replacement of forward slashes with some other character in the client application, and decoding it on the server-side if custom receiving APIs are built on the server side. If the latter is not the case, then it is of course not an option.

[Kafkalasch]

thank you for the fast response. I already expected something like this but thought I'd ask just to be sure =)

[dothebart]

please remember that there may be more characters worth the effort of URL encoding.
Will close this now.