src/Appwrite/Platform/Modules/Databases/Http/Databases/Collections/Documents/Bulk/Update.php (1)

153-155: Chain original QueryException; verify message exposure

Pass the caught exception as previous for better logs/observability, and double‑check that returning the raw DB error message is acceptable to expose. If not, drop the message to use the standardized one for GENERAL_QUERY_INVALID. Optionally apply the same previous chaining to the earlier parseQueries catch for consistency.

-        } catch (QueryException $e) {
-            throw new Exception(Exception::GENERAL_QUERY_INVALID, $e->getMessage());
+        } catch (QueryException $e) {
+            throw new Exception(
+                Exception::GENERAL_QUERY_INVALID,
+                $e->getMessage(),
+                previous: $e
+            );
         }

src/Appwrite/Platform/Modules/Databases/Http/Databases/Collections/Documents/Bulk/Delete.php (1)

127-129: Preserve exception chain; confirm client‑facing message policy

Same suggestion here: include the original exception as previous for diagnostics, and verify whether the raw QueryException message should be surfaced to clients or replaced by the default mapped message.

-        } catch (QueryException $e) {
-            throw new Exception(Exception::GENERAL_QUERY_INVALID, $e->getMessage());
+        } catch (QueryException $e) {
+            throw new Exception(
+                Exception::GENERAL_QUERY_INVALID,
+                $e->getMessage(),
+                previous: $e
+            );
         }

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro