Hiperspace.Rocks 2.5.35

Prefix Reserved
.NET 8.0 This package targets .NET 8.0. The package is compatible with this framework or higher. 
dotnet add package Hiperspace.Rocks --version 2.5.35
                    


                    

                
NuGet\Install-Package Hiperspace.Rocks -Version 2.5.35
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="Hiperspace.Rocks" Version="2.5.35" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="Hiperspace.Rocks" Version="2.5.35" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="Hiperspace.Rocks" />
                    


                            Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package. 
paket add Hiperspace.Rocks --version 2.5.35
                    


                    

                
#r "nuget: Hiperspace.Rocks, 2.5.35"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
#:package Hiperspace.Rocks@2.5.35
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=Hiperspace.Rocks&version=2.5.35
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=Hiperspace.Rocks&version=2.5.35
                    


                            Install as a Cake Tool

Hiperspace.Rocks

RocksDB is a remarkable technology, originally developed by Google (LevelDB) and optimized by Facebook for absolutely lowest possible latency writing to SSD devices. RocksDB used Log-structured-Merge (LSM) to stream updates while maintaining fast key access.
It is used both as a key/value database, and also as a driver for relational-databases, message-stores, blockchain and various analytical services. The use of LSM optimizes performance and life of SSD devices.

Hiperspace.Rocks uses RockDB to store elements in durable SSD memory

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 is compatible.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
2.5.35 42 2/27/2026
2.5.33 94 2/14/2026
2.5.32 96 1/30/2026
2.5.29 97 1/17/2026
2.5.28 102 12/31/2025
2.5.26 182 12/21/2025
2.5.21 435 12/10/2025
2.5.18 669 12/3/2025
2.5.13 205 11/24/2025
2.5.8 188 11/15/2025
2.5.2 223 11/6/2025
2.5.0 206 10/20/2025
2.4.6 211 9/23/2025
2.4.4 293 8/7/2025
2.4.2 181 7/28/2025
2.4.0 211 7/10/2025
2.3.8 210 7/1/2025
2.3.7 208 6/18/2025
2.3.3 211 6/5/2025
2.2.2 233 5/5/2025
Loading failed

https://www.cepheis.com/hiperspace/20260227
# Overview
## Cube Enhancements
A minor enhancement has been made to fully qualify references to **Hiperspace.Functions**. This prevents naming conflicts when a domain also uses **Functions**.

When one of a Cube’s **Dimensions** is `Node`, the `Node` view is added to the Cube along with `Edge` definitions that represent navigation between the **Dimension** and the Cube. In this release, the naming of these edges has been updated to ensure consistent navigation through a HiperGraph, using a common TypeName convention:

* TypeName `Cube:Drilldown` for navigation from a  *Dimension* to the *Cube*.
* TypeName `Cube:Dimension` for navigation from the *Cube* to a *Dimension*.

### Example
In the [Cube Example](https://github.com/channell/Hiperspace/blob/master/examples/Cube/Cube.hilang) ***Customer Sector*** and ***Product*** are *Dimensions* that can also be viewed as `Nodes`. The ***Contract Cube*** therefore has `Node` and `Edges` added as a views because.

[image]blogs/Blogs/Butterfly/product-model.png[/image]

* ***Contact*** (*Cube*) has one ***Account*** and ***Account*** has one ***Customer*** and ***Customer*** has one ***Sector*** (*Dimension*), it is inferred that  ***Sector*** is a *Dimension* of *Cube* ***Contact***.
*  ***Contact*** (*Cube*) has one ***Instrument*** and ***Instrument*** has one ***Product***, it is inferred that ***Product*** is a *Dimension* of *Cube* ***Contract***.

When viewed through a **HiperGraph** the *Cube* becomes a `Node` that links ***Sector*** *node* to ***Product*** *Node*

If you *drilldown* from ***Product*** to ***Contact_Cube*** and *drilldown* to ***Sector***, the shortest *HiperEdge* from ***Product*** to ***Sector*** is through the ***Contract_Cube*** slice that summarizes the connection between the two `Nodes`.  We call this combination of *HiperGraph* and *Cube* "*HiperCube*", and is useful for **AI** prompts like *"which sector uses most widgets?"*

[image]blogs/Blogs/Butterfly/product-graph.png[/image]