2.2 update : purifying Unidatab

Announcement of next Unidatab's release. The clarity reached by asking the right question, has consequences on the technical side, for we can now see what wasn't necessary in the previous architecture of Unidatab. In spite of the support I could get from the writings of respected scientists, it has become clear for me that properties … Continue reading 2.2 update : purifying Unidatab

Advertisements

Back to subdatabases, with tools

Our last query ? select find_record(i) from unid_node where a = -145 limit 2 was fast enough in reaching records containing a certain type of property, provided we added a generic partial symbol (-145) targeting this type. Now we must notice that it's exactly what does a subdatabase. No need to describe our properties for … Continue reading Back to subdatabases, with tools

A golden ratio of data management

Until now we learned that Unidatab is a complicated engine that makes the act of looking for information slower and clumsier. Our last query for instance involved isolating a set of values sharing the same type from a much larger set (symbols). This kind of query is slow when the sets are numerous. No comparison with a classical db. … Continue reading A golden ratio of data management

More about properties and types

As we can grasp it now the node table is mess: nodes don't appear in the order of their chain but according to the moment in which they were created. Though located in another table, symbols look like nodes but constitute another type of entry. But of what types are we talking about in this … Continue reading More about properties and types