From efa04cebcd2caa5a4750217e5a95219f2bbfa582 Mon Sep 17 00:00:00 2001 From: Gil Mizrahi Date: Thu, 20 Jun 2024 15:30:11 +0300 Subject: [PATCH] adding some whys --- .../translation/src/translation/mutation/experimental/mod.rs | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/crates/query-engine/translation/src/translation/mutation/experimental/mod.rs b/crates/query-engine/translation/src/translation/mutation/experimental/mod.rs index d14591cfe..1b1a3da47 100644 --- a/crates/query-engine/translation/src/translation/mutation/experimental/mod.rs +++ b/crates/query-engine/translation/src/translation/mutation/experimental/mod.rs @@ -33,9 +33,12 @@ //! It allows us to update a single row using the uniqueness constraint by updating the relevant columns, //! and contains a pre check and post check for permissions. //! -//! * Mutations using uniqueness constraints use the naming schema `by_column_and_column_and_column` instead of the db constraint name. +//! * Mutations using uniqueness constraints use the naming schema `by_column_and_column_and_column` instead of the db constraint name, +//! because the former is far more helpful. //! * If generating a mutation encounters an internal error, we skip that particular mutation and trace a warning instead of throwing //! an error so the connector can start at any situation. +//! * Naming collisions between the unique constraints and the update_columns / pre_check / post_check is avoided by prefixing argument +//! names of the columns of a unique constraint with `key_`. pub mod common; pub mod delete;