Cube docs

Author: roji

conceptual/EFCore.PG/release-notes/10.0.md

@@ -136,6 +136,21 @@ For more information, [see the documentation](../modeling/generated-properties.m
 
 By default, EF generates GUID (or UUID) values locally in .NET, rather than relying on the database to generate them. Version 9 of the PG provider already switched to generating UUIDv7 values by default ([see release note](9.0.md#uuidv7-guids-are-generated-by-default)), which are significantly better for database indexes. PostgreSQL 18 also added the [`uuidv7()`](https://www.postgresql.org/docs/18/functions-uuid.html#FUNC_UUID_GEN_TABLE) built-in function, which allows database generation of UUIDv7 values. In EFCore.PG 10, if you configure the provider to target PG 18 (`.UseNpgsql("...", o => o.SetPostgresVersion(18, 0))`), the provider will also translate [`Guid.CreateVersion7()`](https://learn.microsoft.com/dotnet/api/system.guid.createversion7) to that function.
 
+## Support for the cube extension
+
+PostgreSQL bundles the [`cube`](https://www.postgresql.org/docs/current/cube.html) extension, which provides a multi-dimensional cube data type and associated operations. EFCore.PG 10 now fully supports the `cube` type out-of-the-box, simply add an `NpgsqlCube` property to your entity type:
+
+```c#
+public class Blog
+{
+    ...
+
+    public NpgsqlCube Cube { get; set; }
+}
+```
+
+Most translations over the type are supported as well. Thanks to [@kirkbrauer](https://github.com/kirkbrauer) for contributing this feature!
+
 ## Other new features
 
 * NodaTime `LocalDate.At()` and `LocalDate.AtMidnight()` are now translated.

conceptual/Npgsql/release-notes/10.0.md

@@ -15,6 +15,29 @@ GSSAPI session encryption is an alternative to SSL/TLS session encryption, where
 
 `RequireAuth` is used to determine which authentication methods are allowed/required. For example, if you want to make sure that passwords aren't sent as cleartext or MD5, you can specify `RequireAuth=!Password,!MD5`. Or, if you want to make sure to always authenticate either via ScramSHA256 or GSS, then you can specify it as `RequireAuth=ScramSHA256,GSS`. To learn more, see PostgreSQL [docs](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNECT-REQUIRE-AUTH).
 
+## Support for the cube extension
+
+PostgreSQL bundles the [`cube`](https://www.postgresql.org/docs/current/cube.html) extension, which provides a multi-dimensional cube data type and associated operations. Npgsql 10 now fully supports the `cube` type out-of-the-box:
+
+```c#
+command.CommandText = """
+    CREATE EXTENSION IF NOT EXISTS cube;
+    CREATE TABLE data (my_cude CUBE);
+""";
+await command.ExecuteNonQueryAsync();
+
+var cube = new NpgsqlCube([1.0, 2.0, 3.0], [4.0, 5.0, 6.0]);
+command.CommandText = "INSERT INTO data (my_cude) VALUES ($1)";
+command.Parameters.Add(new() { Value = cube });
+await command.ExecuteNonQueryAsync();
+
+command.CommandText = "SELECT my_cude FROM data";
+var readCube = (NpgsqlCube)(await command.ExecuteScalarAsync())!;
+Console.WriteLine($"Read cube: {readCube}");
+```
+
+Thanks to [@kirkbrauer](https://github.com/kirkbrauer) for contributing this feature!
+
 ## Various other changes
 
 * OpenTelemetry tracing now also included by default for whenever a physical connection to database is open.

conceptual/Npgsql/types/basic.md

@@ -51,6 +51,7 @@ polygon                     | NpgsqlPolygon              |
 line                        | NpgsqlLine                 |
 circle                      | NpgsqlCircle               |
 box                         | NpgsqlBox                  |
+cube                        | NpgsqlCube<sup>5</sup>     |
 hstore                      | Dictionary<string, string> |
 oid                         | uint                       |
 xid                         | uint                       |
@@ -74,6 +75,8 @@ array types                 | Array (of element type)    |
 
 <sup>4</sup> Prior to version 8.0, the default mapping for `cidr` was `ValueTuple<IPAddress, int>`.
 
+<sup>5</sup> Introduced in Npgsql 10.0.0. Requires the PostgreSQL [`cube`](https://www.postgresql.org/docs/current/cube.html) extension.
+
 ## Write mappings
 
 There are three rules that determine the PostgreSQL type sent for a parameter:
@@ -122,6 +125,7 @@ polygon                     | NpgsqlPolygon                              |
 line                        | NpgsqlLine                                 |                                          | Line                  |
 circle                      | NpgsqlCircle                               |                                          | Circle                |
 box                         | NpgsqlBox                                  |                                          | Box                   |
+cube                        | NpgsqlCube<sup>4</sup>                     |                                          | Cube                  |
 hstore                      | IDictionary\<string, string\>              |                                          | Hstore                |
 oid                         |                                            | uint                                     | Oid                   |
 xid                         |                                            | uint                                     | Xid                   |
@@ -140,6 +144,8 @@ array types                 | T[], List\<T\>                             |
 
 <sup>3</sup>Types which can be read as `byte[]` can also be written as `ReadOnlyMemory<byte>` and `Stream`.
 
+<sup>4</sup> Introduced in Npgsql 10.0.0. Requires the PostgreSQL [`cube`](https://www.postgresql.org/docs/current/cube.html) extension.
+
 Notes when using Range and Array, bitwise-or NpgsqlDbType.Range or NpgsqlDbType.Array with the child type. For example, to construct the NpgsqlDbType for a `int4range`, write `NpgsqlDbType.Range | NpgsqlDbType.Integer`. To construct the NpgsqlDbType for an `int[]`, write `NpgsqlDbType.Array | NpgsqlDbType.Integer`.
 
 For information about enums, [see the Enums and Composites page](enums_and_composites.md).