Topic: the cubic Concept.
There is a subject over which I think the last some weeks.
I will try not to be verbose (it is my jamb) and to throw snippets instead of set of letters.
1. creation (I Write in pseudo-language which can be C#/D/Rust/Java).
Cube cube = new MCube (2580,2580,2580).withStaticAllocation ();
2. filling by the facts . In this case the predicate isMutuallySimple is stated that by triple of numbers - mutually simple.
for (i in 0. 2599) for (j in 0. 2599) for (k in 0. 2599) if (isMutuallySimple (i, j, k)) cube.set (i, j, k);
3. Cube check .
cube.check (7,9,16) == true
Gives true since 7 and 9 and 16 mutually simple. It simply example. In a predicate
There can be your business logic. Check of the physical-person. The enterprises. Technical-means.
Zadljanafiga. . The answer - I searched for analog data structures of type HashTable. A possible point - saving.
Digits. For a cube with the storage expenditure in 2Gbyte. (~17 179 869 184 boolean an element)
[CSV =;] Size; Dimensions
Translating into our language. Storage of the fact table with three columns with cardinality
The order 2 and a half thousand demands in the worst case 2 .
Further - think. Estimate.
Where to apply. Hm... Initially I thought about Hibernejt. A bit later the task became more the general. I began to think of favor of cubes.
Digits it is not sad. The reference manual of a line - digits is necessary.
Dimensionality of a cube should be floppy. Well... At least it should not
To fall at access to an element with an index 2581 in our case. I think over
The iterator. Actually it is possible to support. But there will be waybills. Think.
That does not lay down in cubic Real values. Dates. Time. Money.
That abruptly lays down in cubic Listings. Reference manuals.
Write . while is not present.