Protocol refinements (#208)

## Release notes: usage and product changes

1. Simplify connection open to pre-send database information (reduces 1
round trip on connection open)
2. Standardise `AnswerRow` to `ConceptRow` terminology
3. Type concepts only contain labels and possibly value types, and no
annotations (right now)

Author: flyingsilverfin

proto/answer.proto

@@ -8,13 +8,13 @@ import "proto/concept.proto";
 
 package typedb.protocol;
 
-message AnswerRow {
-    repeated Answer row = 1;
+message ConceptRow {
+    repeated RowEntry row = 1;
 //    Explainables explainables = 2;
 }
 
-message Answer {
-    oneof answer {
+message RowEntry {
+    oneof entry {
         Empty empty = 1;
         Concept concept = 2;
         Value value = 3;

proto/concept.proto

@@ -95,7 +95,7 @@ message Value {
     }
 
     message Struct {
-
+        string struct_type_name = 1;
     }
 }
 
@@ -109,25 +109,20 @@ message Type {
 }
 
 message RoleType {
-    string name = 1;
-    string scope = 2;
-    repeated Annotation annotations = 3;
+    string label = 1;
 }
 
 message EntityType {
     string label = 1;
-    repeated Annotation annotations = 2;
 }
 
 message RelationType {
     string label = 1;
-    repeated Annotation annotations = 2;
 }
 
 message AttributeType {
     string label = 1;
     optional ValueType value_type = 2;
-    repeated Annotation annotations = 3;
 }
 
 message ValueType {

proto/connection.proto

@@ -5,6 +5,7 @@
 syntax = "proto3";
 
 import "proto/version.proto";
+import "proto/database.proto";
 
 package typedb.protocol;
 
@@ -18,9 +19,13 @@ message Connection {
     }
 
     message Res {
-      uint64 server_duration_millis = 2;
-      ConnectionID connection_id = 1;
-      // also: initial Token
+      uint64 server_duration_millis = 1;
+      ConnectionID connection_id = 2;
+
+      // TODO: initial Token
+
+      // pre-send all databases and replica info
+      DatabaseManager.All.Res databases_all = 3;
     }
   }
 }

proto/database.proto

@@ -37,7 +37,9 @@ message DatabaseManager {
         message Req {
             string name = 1;
         }
-        message Res {}
+        message Res {
+            DatabaseReplicas database = 1;
+        }
     }
 }
 

proto/logic.proto

@@ -94,8 +94,8 @@ message Rule {
 message Explanation {
     Rule rule = 1;
     map<string, VarList> var_mapping = 2;
-    AnswerRow condition = 3;
-    AnswerRow conclusion = 4;
+    ConceptRow condition = 3;
+    ConceptRow conclusion = 4;
 
     message VarList {
         repeated string vars = 1;

proto/query.proto

@@ -27,7 +27,7 @@ message Query {
             oneof ok {
                 Empty empty = 1;
                 ReadableConceptTreeStream readable_concept_tree_stream = 3;
-                AnswerRowStream concept_row_stream = 4;
+                ConceptRowStream concept_row_stream = 4;
             }
 
             message Empty {
@@ -38,7 +38,7 @@ message Query {
                 // note: we could use this first response to record debug info, type annotations, warnings, etc
             }
 
-            message AnswerRowStream {
+            message ConceptRowStream {
                 repeated string column_variable_names = 1;
             }
         }
@@ -47,15 +47,15 @@ message Query {
     message ResPart {
         oneof res {
             ReadableConceptTreesRes trees_res = 1;
-            AnswerRowsRes rows_res = 2;
+            ConceptRowsRes rows_res = 2;
         }
 
         message ReadableConceptTreesRes {
             repeated ReadableConceptTree trees = 1;
         }
 
-        message AnswerRowsRes {
-            repeated AnswerRow rows = 1;
+        message ConceptRowsRes {
+            repeated ConceptRow rows = 1;
         }
     }
 }

proto/transaction.proto

@@ -40,7 +40,7 @@ message Transaction {
         bytes req_id = 1;
         oneof res {
             Open.Res open_res = 2;
-            Query.InitialRes query_res = 3;
+            Query.InitialRes query_initial_res = 3;
             Commit.Res commit_res = 5;
             Rollback.Res rollback_res = 6;
         }