You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/ast/trigger.rs
+17-9Lines changed: 17 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -161,24 +161,32 @@ impl fmt::Display for TriggerExecBodyType {
161
161
}
162
162
}
163
163
}
164
-
/// This keyword immediately precedes the declaration of one or two relation names that provide access to the transition relations of the triggering statement
164
+
/// The EXECUTE clause of a CREATE TRIGGER statement.
165
+
///
166
+
/// Holds call-site information: the function/procedure name and optional
167
+
/// positional argument expressions (e.g. string literals passed to
168
+
/// `tsvector_update_trigger`). This is deliberately distinct from
169
+
/// `FunctionDesc`, which carries CREATE-FUNCTION-style parameter
// Verify that EXECUTE FUNCTION accepts call-site expression arguments
6581
+
// (e.g. string literals), not just bare identifiers. This matches the
6582
+
// PostgreSQL tsvector_update_trigger calling convention used in pagila.
6583
+
let sql = "CREATE TRIGGER film_fulltext_trigger BEFORE INSERT OR UPDATE ON public.film FOR EACH ROW EXECUTE FUNCTION tsvector_update_trigger('fulltext', 'pg_catalog.english', 'title', 'description')";
6584
+
let expected = Statement::CreateTrigger(CreateTrigger{
0 commit comments