Preview documentation (v2.2) visible on npgsql.org
See original GitHub issueHello
I noticed the documentation on the wiki points to 2.2
Is it possible to have it in sync with the latest stable version, which is 2.1.x ?
I noticed this when I tried to use .ForNpgsqlHasEnum<Enum>()
, which didn’t work as I was on 2.1.2
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Npgsql Documentation
Npgsql aims to be fully ADO.NET-compatible, its API should feel almost identical to other .NET database drivers. Here's a basic code snippet to...
Read more >Npgsql 8.0.0-preview.2
Npgsql is the open source .NET data provider for PostgreSQL. It allows you to connect and interact with PostgreSQL server using .NET.
Read more >Npgsql - .NET Access to PostgreSQL | Npgsql Documentation
Npgsql is an open source ADO.NET Data Provider for PostgreSQL, it allows programs written in C#, Visual Basic, F# to access the PostgreSQL...
Read more >Documentation: 15: COPY
COPY TO copies the contents of a table to a file, while COPY FROM copies data from a file to a table (appending...
Read more >Amazon RDS for PostgreSQL updates
This is preview documentation for Amazon RDS PostgreSQL version 16 Beta 2. It is subject to change. PostgreSQL version 16 Beta 2 is...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
We can also look at making preview documentation for vNext available on the site, although that frankly seems like very low priority to me…
This is actually turning out to be a bit complicated. It looks like we have current docs in both
master
anddev
that do not appear in the other. (I’m responsible for at least some of this…)I’m going to submit a PR to get everything right in
dev
. Along the way, I’ll try to segregate version-specific changes (e.g. enums) as tabbed content.Once that’s accepted (and we can verify everything is there), I’ll submit a second PR to backport the whole
doc/
directory tomaster
, which will hopefully make it easier going forward to apply the normal pattern of backporting.