Naming conventions (db 64, coll 256)

arangodb · Dec 19, 2019 · d3c4e3b · d3c4e3b
1 parent 3d5164c
commit d3c4e3b
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/3.6/aql/fundamentals-syntax.md b/3.6/aql/fundamentals-syntax.md
@@ -209,9 +209,9 @@ Names
 In general, names are used to identify objects (collections, attributes,
 variables, and functions) in AQL queries.
 
-<!-- TODO: variable names can apparently be longer than 256 bytes -->
-The maximum supported length of any name is 256 bytes. Names in AQL are always
-case-sensitive.
+Names in AQL are always case-sensitive.
+The maximum supported length for collection/View names is 256 bytes.
+Variable names can be longer, but are discouraged.
 
 Keywords must not be used as names. If a reserved keyword should be used as a
 name, the name must be enclosed in backticks or forward ticks. Enclosing a name in 

diff --git a/3.6/data-modeling-naming-conventions-database-names.md b/3.6/data-modeling-naming-conventions-database-names.md
@@ -16,5 +16,5 @@ names conform to the following constraints:
 * Database names must always start with a letter. Database names starting 
   with an underscore are considered to be system databases, and users should 
   not create or delete those
-* The maximum allowed length of a database name is 255 bytes <!-- TODO: why?! -->
+* The maximum allowed length of a database name is 64 bytes
 * Database names are case-sensitive