From 18a309ef8c3d264080d64a54425340feb0f795d6 Mon Sep 17 00:00:00 2001 From: Shay Rojansky Date: Mon, 20 Jan 2025 15:44:34 +0100 Subject: [PATCH] Add Integrated Security connstring param removal to the 8.0 breaking changes list --- conceptual/Npgsql/release-notes/8.0.md | 1 + 1 file changed, 1 insertion(+) diff --git a/conceptual/Npgsql/release-notes/8.0.md b/conceptual/Npgsql/release-notes/8.0.md index 5a9834b5..40fb6dd8 100644 --- a/conceptual/Npgsql/release-notes/8.0.md +++ b/conceptual/Npgsql/release-notes/8.0.md @@ -114,6 +114,7 @@ As part of improving Npgsql's support for the PostgreSQL network mappings (see a ### Obsoletions and obsolete API removals +* The `Integrated Security` connection parameter has been removed. It was never actually necessary - simply stop setting it. * `NpgsqlTsVector.Parse()` and `NpgsqlTsQuery.Parse()` are now obsolete. These methods attempted to mimic the behavior of the PostgreSQL `to_tsvector` and `to_tsquery` functions, but could only do so partially and in problematic ways. Use the PostgreSQL functions instead. * The parsing functions on the built-in geometry types (NpgsqlPoint, NpgsqlBox etc.) have been removed; similarly, they partially replicated PostgreSQL parsing functionality client-side and had issues. * `NpgsqlLargeObjectManager` and `NpsgqlLargeObjectStream` are now obsolete. These types were very rarely-used, provided only a thin wrapper over easily-accessible PostgreSQL large-object functions, and limited usage in various ways (e.g. they didn't allow batching). Call the PostgreSQL large-object functions directly.