Skip to content

fix: broken code embedding #395

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
roji merged 2 commits into from
Mar 4, 2025
Merged

fix: broken code embedding #395

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2d1438a
fix: broken code embedding
zFlxw Mar 4, 2025
1e120d9
fix: typos and wrong class reference
zFlxw Mar 4, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion conceptual/Npgsql/types/basic.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,7 @@ multirange types (PG14) | NpgsqlRange\<TElement>[] |
enum types | TEnum |
array types | Array (of element type) |

<sup>1</sup>Types which can be read as `byte[]` can also be written as `ReadOnlyMemory<byte>` and `Stream`., and if they could be big, consider using `Stream`CommandBehavior.SequentialAccess` and `NpgsqlDataReader.GetStream()` to stream the row and column instead of buffering them. Note that if you're reading string data (e.g. `jsonb`) as binary, it's you're responsibility to perform UTF8 decoding (or whatever encoding is configured for your database).
<sup>1</sup>Types which can be read as `byte[]` can also be written as `ReadOnlyMemory<byte>` and `Stream`, and if they could be big, consider using `CommandBehavior.SequentialAccess` and `NpgsqlDataReader.GetStream()` to stream the row and column instead of buffering them. Note that if you're reading string data (e.g. `jsonb`) as binary, it's your responsibility to perform UTF8 decoding (or whatever encoding is configured for your database).

<sup>2</sup> In versions prior to 6.0 (or when `Npgsql.EnableLegacyTimestampBehavior` is enabled), reading a `timestamp with time zone` returns a Local DateTime instead of Utc, and reading it as a DateTimeOffset returns a local offset based on the timezone of the server where Npgsql is running. [See the breaking change note for more info](../release-notes/6.0.md#major-changes-to-timestamp-mapping).

Expand Down