From 74cf95650609d62609cbc45f8fef67cd671d1385 Mon Sep 17 00:00:00 2001 From: Shay Rojansky Date: Thu, 24 Nov 2022 17:13:20 +0100 Subject: [PATCH] Add some more info to the stored procedure breaking note Closes #264 --- conceptual/Npgsql/release-notes/7.0.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/conceptual/Npgsql/release-notes/7.0.md b/conceptual/Npgsql/release-notes/7.0.md index 9a0729272..d1090daa7 100644 --- a/conceptual/Npgsql/release-notes/7.0.md +++ b/conceptual/Npgsql/release-notes/7.0.md @@ -70,16 +70,20 @@ Note that with Npgsql, there is no advantage in using [`CommandType.StoredProced // Invoke a procedure using var command1 = new NpgsqlCommand("CALL some_procedure($1, $2)", connection) { - // Add parameters + new() { Value = "some_value" }, + new() { Value = "some_other_value" } }; // Invoke a function using var command2 = new NpgsqlCommand("SELECT * FROM some_function($1, $2)", connection) { - // Add parameters + new() { Value = "some_value" }, + new() { Value = "some_other_value" } }; ``` +For more information on calling procedures and functions, see [this doc section](../basic-usage.html#stored-functions-and-procedures). + ### Managing type mappings at the connection level is no longer supported Previous versions of Npgsql allowed mapping custom types (enums/composites) and configuring plugins (NetTopologySuite, NodaTime) at the connection level; the type mapping change would persist only for the lifetime of the connection, and would be reverted when the connection closed. This mechanism was inefficient - connections get opened and closed a lot - and added significant maintenance burden internally.