edgedb error: -> gel error:

docs/datamodel/constraints.rst

@@ -458,14 +458,14 @@ apply globally across all the types that inherited the constraint.
     db> insert Moderator {
     ...   name := 'Jan'
     ... };
-    edgedb error: ConstraintViolationError: name violates exclusivity
+    gel error: ConstraintViolationError: name violates exclusivity
     constraint
       Detail: value of property 'name' of object type 'default::Moderator'
       violates exclusivity constraint
     db> insert User {
     ...   name := 'Jan'
     ... };
-    edgedb error: ConstraintViolationError: name violates exclusivity
+    gel error: ConstraintViolationError: name violates exclusivity
     constraint
       Detail: value of property 'name' of object type 'default::User'
       violates exclusivity constraint
@@ -518,7 +518,7 @@ on each of the inheriting types.
     db> insert Moderator {
     ...   name := 'Jan'
     ... };
-    edgedb error: ConstraintViolationError: name violates exclusivity
+    gel error: ConstraintViolationError: name violates exclusivity
     constraint
       Detail: value of property 'name' of object type 'default::Moderator'
       violates exclusivity constraint

docs/datamodel/functions.rst

@@ -109,10 +109,10 @@ Unlike other functions, the arguments of modifying functions **must** have a
 .. code-block:: edgeql-repl
 
     db> select add_user({'Feb','Mar'});
-    edgedb error: QueryError: possibly more than one element passed into
+    gel error: QueryError: possibly more than one element passed into
     modifying function
     db> select add_user(<str>{});
-    edgedb error: QueryError: possibly an empty set passed as non-optional
+    gel error: QueryError: possibly an empty set passed as non-optional
     argument into modifying function
 
 Optional arguments can still accept empty sets. For example, if ``add_user``

docs/datamodel/triggers.rst

@@ -347,7 +347,7 @@ both a friend and an enemy of any other person.
     ...     select detached Person filter .name = 'Dracula'
     ...   )
     ... };
-    edgedb error: GelError: Invalid frenemies
+    gel error: GelError: Invalid frenemies
 
 
 .. list-table::

docs/edgeql/literals.rst

@@ -539,7 +539,7 @@ ranges cannot be unpacked.
     db> select range_unpack(range(1, 1));
     {}
     db> select range_unpack(range(0, <int64>{}));
-    edgedb error: InvalidValueError: cannot unpack an unbounded range
+    gel error: InvalidValueError: cannot unpack an unbounded range
 
 .. _ref_eql_literal_bytes:
 

docs/edgeql/types.rst

@@ -108,7 +108,7 @@ typed; you can't simply convert an object to an object of a different type.
     .. code-block:: edgeql-repl
 
         db> select <Hero><uuid>'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa';
-        edgedb error: CardinalityViolationError: 'default::Hero' with id 'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa' does not exist
+        gel error: CardinalityViolationError: 'default::Hero' with id 'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa' does not exist
 
 .. lint-on
 

docs/guides/migrations/tips.rst

@@ -337,7 +337,7 @@ Now we proceed with the migration:
     Created ./dbschema/migrations/00003.edgeql, id:
     m1dxs3xbk4f3vhmqh6mjzetojafddtwlphp5a3kfbfuyvupjafevya
     $ edgedb migrate
-    edgedb error: ConstraintViolationError: name violates exclusivity
+    gel error: ConstraintViolationError: name violates exclusivity
     constraint
 
 Some objects must have the same ``name``, so the migration can't be
@@ -385,7 +385,7 @@ And then we apply the migration:
 .. code-block:: bash
 
     $ edgedb migrate
-    edgedb error: could not read migrations in ./dbschema/migrations: could not
+    gel error: could not read migrations in ./dbschema/migrations: could not
     read migration file ./dbschema/migrations/00003.edgeql: migration name
     should be `m1t6slgcfne35vir2lcgnqkmaxsxylzvn2hanr6mijbj5esefsp7za` but `
     m1dxs3xbk4f3vhmqh6mjzetojafddtwlphp5a3kfbfuyvupjafevya` is used instead.
@@ -581,7 +581,7 @@ reminder:
 .. code-block:: bash
 
     $ edgedb migrate
-    edgedb error: could not read migrations in ./dbschema/migrations:
+    gel error: could not read migrations in ./dbschema/migrations:
     could not read migration file ./dbschema/migrations/00003.edgeql:
     migration name should be
     `m1e3d3eg3j2pr7acie4n5rrhaddyhkiy5kgckd5l7h5ysrpmgwxl5a` but
@@ -886,7 +886,7 @@ We're ready to apply the migration:
 .. code-block:: bash
 
     $ edgedb migrate
-    edgedb error: could not read migrations in ./dbschema/migrations:
+    gel error: could not read migrations in ./dbschema/migrations:
     could not read migration file ./dbschema/migrations/00003.edgeql:
     migration name should be
     `m1ryafvp24g5eqjeu65zr4bqf6m3qath3lckfdhoecfncmr7zshehq`
@@ -1025,7 +1025,7 @@ reminder:
 .. code-block:: bash
 
     $ edgedb migrate
-    edgedb error: could not read migrations in ./dbschema/migrations:
+    gel error: could not read migrations in ./dbschema/migrations:
     could not read migration file ./dbschema/migrations/00002.edgeql:
     migration name should be
     `m1juin65wriqmb4vwg23fiyajjxlzj2jyjv5qp36uxenit5y63g2iq` but
@@ -1320,7 +1320,7 @@ Our attempt at migrating fails as we expected:
 .. code-block:: bash
 
     $ edgedb migrate
-    edgedb error: MissingRequiredError: missing value for required link
+    gel error: MissingRequiredError: missing value for required link
     'class' of object type 'default::Character'
       Detail: Failing object id is 'ee604992-c1b1-11ec-ad59-4f878963769f'.
 

docs/intro/projects.rst

@@ -121,7 +121,7 @@ with the ``-I`` flag.
 
   $ cd ~
   $ edgedb
-  edgedb error: no `edgedb.toml` found and no connection options are specified
+  gel error: no `edgedb.toml` found and no connection options are specified
     Hint: Run `edgedb project init` or use any of `-H`, `-P`, `-I` arguments to
     specify connection parameters. See `--help` for details
   $ edgedb -I my_instance

docs/reference/edgeql/casts.rst

@@ -49,7 +49,7 @@ information on type casting rules.
     .. code-block:: edgeql-repl
 
         db> select <Hero><uuid>'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa';
-        edgedb error: CardinalityViolationError: 'default::Hero' with id 'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa' does not exist
+        gel error: CardinalityViolationError: 'default::Hero' with id 'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa' does not exist
 
 .. lint-on
 

docs/stdlib/bool.rst

@@ -340,10 +340,10 @@ operator.
         {true}
 
         db> select assert(false);
-        edgedb error: QueryAssertionError: assertion failed
+        gel error: QueryAssertionError: assertion failed
 
         db> select assert(false, message := 'value is not true');
-        edgedb error: QueryAssertionError: value is not true
+        gel error: QueryAssertionError: value is not true
 
     ``assert`` can be used in triggers to create more powerful constraints. In
     this schema, the ``Person`` type has both ``friends`` and ``enemies``
@@ -390,7 +390,7 @@ operator.
         ...     select detached Person filter .name = 'Dracula'
         ...   )
         ... };
-        edgedb error: GelError: Invalid frenemies
+        gel error: GelError: Invalid frenemies
 
     In the following examples, the ``size`` properties of the ``File`` objects
     are ``1024``, ``1024``, and ``131,072``.
@@ -403,7 +403,7 @@ operator.
 
         db> for obj in (select File)
         ... union (assert(obj.size <= 64*1024, message := 'file too big'));
-        edgedb error: QueryAssertionError: file too big
+        gel error: QueryAssertionError: file too big
 
     You may call ``assert`` in the ``order by`` clause of your ``select``
     statement. This will ensure it is called only on objects that pass your
@@ -421,7 +421,7 @@ operator.
 
         db> select File { name, size }
         ... order by assert(.size <= 64*1024, message := "file too big");
-        edgedb error: QueryAssertionError: file too big
+        gel error: QueryAssertionError: file too big
 
         db> select File { name, size }
         ... filter .size <= 64*1024

docs/stdlib/bytes.rst

@@ -286,4 +286,4 @@ Bytes
         db> select enc::base64_decode('aGVsbG8=');
         {b'hello'}
         db> select enc::base64_decode('aGVsbG8');
-        edgedb error: InvalidValueError: invalid base64 end sequence
+        gel error: InvalidValueError: invalid base64 end sequence

docs/stdlib/datetime.rst

@@ -310,7 +310,7 @@ functionality.
         db> select <duration>'48 hours 45 minutes';
         {<duration>'48:45:00'}
         db> select <duration>'11 months';
-        edgedb error: InvalidValueError: invalid input syntax for type
+        gel error: InvalidValueError: invalid input syntax for type
         std::duration: '11 months'
           Hint: Units bigger than hours cannot be used for std::duration.
 

docs/stdlib/numbers.rst

@@ -716,7 +716,7 @@ Definitions
     .. code-block:: edgeql-repl
 
         db> select bit_lshift(123, -2);
-        edgedb error: InvalidValueError: bit_lshift(): cannot shift by
+        gel error: InvalidValueError: bit_lshift(): cannot shift by
         negative amount
 
 
@@ -765,7 +765,7 @@ Definitions
     .. code-block:: edgeql-repl
 
         db> select bit_rshift(123, -2);
-        edgedb error: InvalidValueError: bit_rshift(): cannot shift by
+        gel error: InvalidValueError: bit_rshift(): cannot shift by
         negative amount
 
 

docs/stdlib/range.rst

@@ -160,7 +160,7 @@ omitted, but if they are present, they must be consistent with an empty range:
     ...   "inc_upper": false,
     ...   "empty": true
     ... }');
-    edgedb error: InvalidValueError: conflicting arguments in range
+    gel error: InvalidValueError: conflicting arguments in range
     constructor: "empty" is ``true`` while the specified bounds suggest
     otherwise
 

docs/stdlib/string.rst

@@ -785,7 +785,7 @@ Strings
         db> select to_str(b'\xe3\x83\x86');
         {'テ'}
         db> select to_str(b'\xe3\x83');
-        edgedb error: InvalidValueError: invalid byte sequence for
+        gel error: InvalidValueError: invalid byte sequence for
         encoding "UTF8": 0xe3 0x83