DOC-1906-warning-empty-primary-id 3.6

Author: Victor Lee

modules/ddl-and-loading/pages/defining-a-graph-schema.adoc

@@ -87,6 +87,13 @@ If you have a single attribute which serves as your primary key, use the `PRIMAR
 This gives you the flexibility of option 2 with the GraphStudio compatibility of option 1.
 ====
 
+[IMPORTANT]
+====
+When loading or inserting vertices, take care not to accidentally leave the primary ID field empty.
+
+* Prior to version 3.9.2, an empty primary ID field is accepted as valid. From 3.9.2+, it will be rejected.
+====
+
 Regardless of which option is selected, GSQL automatically creates a hash index of the key for fast O(1) searches.
 
 The syntax for the three options are summarized below.

modules/ddl-and-loading/partials/load-statement.adoc

@@ -64,6 +64,13 @@ If the vertex data is loaded later, it will be automatically merged with the aut
 The user can disable this feature and perform regular referential integrity checking by setting the `VERTEX_MUST_EXIST` option to `true`.
 ====
 
+[IMPORTANT]
+====
+When loading or inserting vertices, take care not to accidentally leave the primary ID field empty.
+
+* Prior to version 3.6.3, an empty primary ID field is accepted as valid. From 3.6.3+, it will be rejected.
+====
+
 === Examples
 
 Suppose we have the following vertex and edge types: