Some release notes and breaking changes for 8.0 #306
Conversation
|
|
||
| ### System.Text.Json mapping support must now be opted into | ||
| Considerable effort has gone into reducing Npgsql's size footprint; a minimal Npgsql application using NativeAOT and trimming now takes only around 5MB of disk space. To allow users to achieve a minimal size footprint, <xref:Npgsql.NpgsqlSlimDataSourceBuilder> has been introduced; unlike the standard <xref:Npgsql.NpgsqlDataSourceBuilder>, this builder includes only the very minimum of functionality by default, and allows adding additional features via opt-ins. This allows a pay-per-play approach to application size, where developers can choose only the features they actually need for optimal size. For more information on <xref:Npgsql.NpgsqlDataSourceBuilder> |
There was a problem hiding this comment.
| Considerable effort has gone into reducing Npgsql's size footprint; a minimal Npgsql application using NativeAOT and trimming now takes only around 5MB of disk space. To allow users to achieve a minimal size footprint, <xref:Npgsql.NpgsqlSlimDataSourceBuilder> has been introduced; unlike the standard <xref:Npgsql.NpgsqlDataSourceBuilder>, this builder includes only the very minimum of functionality by default, and allows adding additional features via opt-ins. This allows a pay-per-play approach to application size, where developers can choose only the features they actually need for optimal size. For more information on <xref:Npgsql.NpgsqlDataSourceBuilder> | |
| Considerable effort has gone into reducing Npgsql's size footprint; a minimal Npgsql application using NativeAOT and trimming now takes only around 5MB of disk space. To allow users to achieve a minimal size footprint, <xref:Npgsql.NpgsqlSlimDataSourceBuilder> has been introduced; unlike the standard <xref:Npgsql.NpgsqlDataSourceBuilder>, this builder includes only the very minimum of functionality by default, and allows adding additional features via opt-ins. This allows a pay-for-play approach to application size, where developers can choose only the features they actually need for optimal size. For more information on <xref:Npgsql.NpgsqlDataSourceBuilder> |
There was a problem hiding this comment.
No strong feelings here but both terms seem to be used (some search results). I'll leave like that for now but if you feel strongly about it I can change.
| Npgsql version 8.0 is under development, and is available as preview versions. | ||
| **The below release notes and breaking changes list aren't yet complete. Check back soon for more notes.** | ||
|
|
||
| Npgsql version 8.0 is under development, and is available as release candidate versions. | ||
|
|
||
| ## New features |
There was a problem hiding this comment.
We should mention nullable parameter support in copy and parameters
npgsql/npgsql#1965
npgsql/npgsql#3679
There is also some info that needs changes here, as we now do support sending nulls
https://www.npgsql.org/doc/basic-usage.html#strongly-typed-parameters
There was a problem hiding this comment.
We can decide to mention something about the polymorphic json support npgsql/npgsql#4862
There was a problem hiding this comment.
Oh absolutely, this is just a first round - we definitely need a lot more release notes; I'll be working on that (putting your suggestions in my notes).
| In previous versions, transparent JSON serialization and deserialization was supported via System.Text.Json. That support hasn't changed, but you must now explicitly opt into it. If you're using `NpgsqlDataSource`, simply add the following when building your data source: | ||
| Making Npgsql NativeAOT/trimming-compatible was a far-reaching effort, affecting many parts of the driver and involving a rewrite of large parts of Npgsql's internals (leading to many other internal improvements). This huge task was done mainly by [Nino Floris](http://github.com/ninofloris), with considerable contributions also by [Nikita Kazmin](https://github.com/vonzshik). | ||
|
|
||
| ## Breaking changes |
There was a problem hiding this comment.
I'm assuming we're still missing quite a few things here, including cidr/inet changes etc?
There was a problem hiding this comment.
Absolutely, this is just a first round. I'll be submitting more PRs.
Do you think we should address this in the release notes for 8.0? Feels like we should do this for 9.0 no? |
|
Merging as-is for now, we'll be adding more in any case so we can modify as required. |
Original commit: 41cfb70
We definitely should do that for 9.0, but adding a note for 8.0 (that it's going to be the last version supporting netfx) definitely wouldn't hurt. Either people will notice and might raise an issue, or we can always point out that we've made an effort to notify everyone a year ahead. |
No description provided.