Refactor edge type creation to remove UNIDIRECTIONAL specification

- Updated multiple examples and tests to create edge types without the UNIDIRECTIONAL keyword, allowing for default bidirectional edge storage.
- Adjusted related documentation and benchmark results to reflect changes in edge type creation.
- Ensured consistency across various test cases and examples by removing the UNIDIRECTIONAL specification from edge type creation commands.

Author: tae898

bindings/python/docs/api/importer.md

@@ -98,7 +98,7 @@ db.command(
 ### Import Graph Edges
 
 ```python
-db.command("sql", "CREATE EDGE TYPE Follows UNIDIRECTIONAL")
+db.command("sql", "CREATE EDGE TYPE Follows")
 db.command(
     "sql",
     (

bindings/python/docs/api/server.md

@@ -579,7 +579,7 @@ except:
 
 # Initialize schema
 db.command("sql", "CREATE VERTEX TYPE TestNode")
-db.command("sql", "CREATE EDGE TYPE TestEdge UNIDIRECTIONAL")
+db.command("sql", "CREATE EDGE TYPE TestEdge")
 
 db.close()
 

bindings/python/docs/development/testing/test-opencypher.md

@@ -18,7 +18,7 @@ import arcadedb_embedded as arcadedb
 
 with arcadedb.create_database("./opencypher_test_db") as db:
     db.command("sql", "CREATE VERTEX TYPE Person")
-    db.command("sql", "CREATE EDGE TYPE Knows UNIDIRECTIONAL")
+    db.command("sql", "CREATE EDGE TYPE Knows")
 
     with db.transaction():
         alice = db.new_vertex("Person")

bindings/python/docs/examples/02_social_network_graph.md

@@ -79,10 +79,10 @@ with db.transaction():
     )
 ```
 
-!!! note "Directed-edge migration note"
-    Current graph examples explicitly declare `CREATE EDGE TYPE ... UNIDIRECTIONAL`.
-    That means you should not assume reverse edges are automatically materialized in
-    storage. If you need incoming traversal behavior, express it in the query pattern.
+!!! note "Directed-edge storage note"
+    Graph relationships are still directed from source to target, but the examples now
+    rely on ArcadeDB's default bidirectional edge storage. That keeps reverse traversal
+    efficient without changing the semantic direction of the relationship.
 
 ### Schema Definition
 
@@ -104,7 +104,7 @@ with arcadedb.create_database("./social_network_db") as db:
     db.command("sql", "CREATE PROPERTY Person.reputation FLOAT")  # Optional (can be NULL)
 
     # Create edge type with properties
-    db.command("sql", "CREATE EDGE TYPE FRIEND_OF UNIDIRECTIONAL")
+    db.command("sql", "CREATE EDGE TYPE FRIEND_OF")
     db.command("sql", "CREATE PROPERTY FRIEND_OF.since DATE")
     db.command("sql", "CREATE PROPERTY FRIEND_OF.closeness STRING")
 

bindings/python/docs/examples/05_csv_import_graph.md

@@ -314,11 +314,11 @@ db.command("sql", "CREATE PROPERTY Movie.title STRING")
 db.command("sql", "CREATE INDEX ON Movie (movieId) UNIQUE_HASH")
 
 # Create edge types
-db.command("sql", "CREATE EDGE TYPE RATED UNIDIRECTIONAL IF NOT EXISTS")
+db.command("sql", "CREATE EDGE TYPE RATED IF NOT EXISTS")
 db.command("sql", "CREATE PROPERTY RATED.rating FLOAT")
 db.command("sql", "CREATE PROPERTY RATED.timestamp LONG")
 
-db.command("sql", "CREATE EDGE TYPE TAGGED UNIDIRECTIONAL IF NOT EXISTS")
+db.command("sql", "CREATE EDGE TYPE TAGGED IF NOT EXISTS")
 db.command("sql", "CREATE PROPERTY TAGGED.tag STRING")
 db.command("sql", "CREATE PROPERTY TAGGED.timestamp LONG")
 ```

bindings/python/docs/examples/basic.md

@@ -81,7 +81,7 @@ import arcadedb_embedded as arcadedb
 with arcadedb.create_database("./mydb") as db:
     # Create graph schema (schema ops are auto-transactional)
     db.command("sql", "CREATE VERTEX TYPE Person")
-    db.command("sql", "CREATE EDGE TYPE Knows UNIDIRECTIONAL")
+    db.command("sql", "CREATE EDGE TYPE Knows")
     db.command("sql", "CREATE PROPERTY Person.name STRING")
 
     # Create vertices and edges

bindings/python/docs/examples/import.md

@@ -85,7 +85,7 @@ with arcadedb.create_database("./import_demo") as db:
 ```python
 with arcadedb.create_database("./graph_import_demo") as db:
     db.command("sql", "CREATE VERTEX TYPE User")
-    db.command("sql", "CREATE EDGE TYPE Follows UNIDIRECTIONAL")
+    db.command("sql", "CREATE EDGE TYPE Follows")
 
     db.command(
         "sql",

bindings/python/docs/guide/core/database.md

@@ -305,7 +305,7 @@ def init_database(path: str):
             db.command("sql", "CREATE VERTEX TYPE Post")
             db.command("sql", "CREATE PROPERTY Post.title STRING")
 
-            db.command("sql", "CREATE EDGE TYPE Authored UNIDIRECTIONAL")
+            db.command("sql", "CREATE EDGE TYPE Authored")
 
             print(f"Database initialized at {path}")
 
@@ -373,7 +373,7 @@ def migrate_database(old_path: str, new_path: str):
         # Copy schema
         new_db.command("sql", "CREATE VERTEX TYPE User")
         new_db.command("sql", "CREATE VERTEX TYPE Post")
-        new_db.command("sql", "CREATE EDGE TYPE Authored UNIDIRECTIONAL")
+        new_db.command("sql", "CREATE EDGE TYPE Authored")
 
         # Copy data
         batch_size = 1000

bindings/python/docs/guide/core/queries.md

@@ -33,7 +33,7 @@ with db.transaction():
 ```python
 # Create schema
 db.command("sql", "CREATE VERTEX TYPE Person")
-db.command("sql", "CREATE EDGE TYPE Knows UNIDIRECTIONAL")
+db.command("sql", "CREATE EDGE TYPE Knows")
 
 # Insert using SQL (RECOMMENDED)
 with db.transaction():

bindings/python/docs/guide/core/transactions.md

@@ -75,7 +75,7 @@ with arcadedb.create_database(temp_db_path) as db:
 ```python
 with arcadedb.create_database(temp_db_path) as db:
     db.command("sql", "CREATE VERTEX TYPE Person")
-    db.command("sql", "CREATE EDGE TYPE Knows UNIDIRECTIONAL")
+    db.command("sql", "CREATE EDGE TYPE Knows")
 
     with db.transaction():
         db.command("sql", "INSERT INTO Person SET name = 'Alice'")