51

Re: the cubic Concept.

mayton wrote:

Further (****) the Extension of a segment of the data for filter Bluma.
I here will long not describe the theory. Can esteem Vicks. Filter Bluma in essence does not extend.
It it is possible  anew and using an original DB  all amount the facts in a new segment.
Adding of the new facts - probably but leads to selectivity loss.

it is impossible to delete from Bluma, and remaining it is solved.
I so understand speech about it is impossible to add new measurements. Here it is possible to be turned out: if at adding of new measurement by all old given to appropriate 0 for this measurement, and after at calculation  not to include this measurement in calculation if it 0 then values  remain same.

52

Re: the cubic Concept.

mayton wrote:

Well... As a topic-starter I all the same suggest to be restricted to a subject of the first post.

I cannot invent a real life application to such cube in any way. In your examples a cube we do not apply, there the reverse task: compactly to store attributes.
Normally it is necessary to check up that there are facts with the given attributes and further something with them to do, i.e. the answer "such fact precisely does not suffice is", and the cube any . does not give, i.e. receiving "is" it is necessary to climb in a DB further.
Unique advantage over Blumom that it is possible to check up an interval of values on one of measurements
And if in a DB all the same to climb, it is possible to throw out a cube and to simplify the task: to make a field hash, on it an index and so to use

h = my_hash (value1, value2, value3)
select... from Table T where T.hash = h and T.attr1 = value1 and T.attr2 = value2 and T.attr3 = value3

53

Re: the cubic Concept.

If we want so to be turned out that it is to equivalently repeated loading of all volume.
But if we initially added in  tuples in a format json (with field names) then anything it is not necessary to do.

54

Re: the cubic Concept.

Dima T wrote:

I cannot invent a real life application to such cube in any way.

smile))
Not  so it is strong. A subject as a matter of fact the Friday.
[quote =] Normally it is necessary to check up that there are facts with the given attributes and further something with them to do, i.e. the answer "such fact precisely does not suffice is", and the cube any . does not give, i.e. receiving "is" it is necessary to climb in a DB further.

In an example No2 which I resulted above was API which checks availability UI of an element to display.
Was the order 500 entitlements and the order of 2000 elements UI. Communication - many to many. To connect
The intermediate label is entered into a DB these two entities entitlement2ui. Graphically it is possible
To present as a Boolean matrix 500 on 2000 Boolean elements where each element speaks that
It is possible or is impossible to display element UI for given . Further still there was another
The intermediate label of users which was parent in relation to
But it is not so important in sew to the task.
Here whence actually also there was at me an initial setting.