doc
doc copied to clipboard
npgsql
Documentation site for npgsql
From: https://www.npgsql.org/doc/release-notes/8.0.html#json-poco-and-other-dynamic-features-now-require-an-explicit-opt-in --> This doesn't look correct:  I guess, there should be links to the documentation, not `xref`s.
As npgsql/efcore.pg#2818 showed, it is not clear on what RegexOptions are actually supported. I suggest adding a note to the tranlation docs to make it clearer for everyone.
We got hung up on this one for quite a while, it's an easy gotcha to run into if you are setting up `NetTopologySuite` in an existing application that obtains...
Via nested data reader, see https://github.com/npgsql/npgsql/issues/3558
* Some of the answers are no longer relevant in their current form (e.g. stored procedure vs. function) * The layout sucks with the huge titles, make them shorter etc....
We should have a Pooling page under "advanced topics", which details how the pool works and all the various tweaks we support. * Database restart doesn't clear the pool -...
This is documentation for https://github.com/npgsql/npgsql/pull/4430, intended for v7.0
Hi, We have been using the logical replication feature with Npgsql 5.x quite successfully. The release notes for Npgsql 6.x say: > ### [The logical replication API has been redone](https://www.npgsql.org/doc/release-notes/6.0.html#the-logical-replication-api-has-been-redone)...
I am comparing behavior of the `NpgsqlTypes.NpgsqlTsQuery.Parse(_query);` vs just passing in my raw query string using `EF.Functions.ToTsQuery(_query)`. The short of the problem is that `EF.Functions.ToTsQuery(_query)` behaves as expected, while `NpgsqlTypes.NpgsqlTsQuery.Parse(_query)`...
