Update 2.2: released

Maintainability is the intention of this Revision 2.2 which achieves several goals, among which, bringing a clear schema of the execution modes, introduce formatting help (libfmt) and output classes (UnidCells, GraphicSet), review coding practice and algorithms. This last objective led to the suppression of several redundancies and the introduction of more or less successful stylistic … Continue reading Update 2.2: released

Advertisements

Update 2.2: development within the limits of an hybrid system

Announcement of next Unidatab’s release (continued). Based on a static, single-threaded process, Unidatab is a hybrid system in which principles of programmation don't apply well. For example, having classes corresponding to the main objects we are dealing with isn't essential here and could even be disturbing when these objects already exist preformatted in the underlying … Continue reading Update 2.2: development within the limits of an hybrid system

Version 2.0: the splitting of the node table

[ UPGRADE WARNING for Unidatab 2.0: The new version brings structural changes, in consequence older databases have to be migrated to the new standard (see this link). Besides, some functions have been improved in syntax and output. Therefore old documentation will reveal inappropriate in some cases and will be corrected gradually in the near future. … Continue reading Version 2.0: the splitting of the node table

Search functions

Introduction In this post we'll explore ways of selecting records by comparison of properties. Designing even the simplest scientific examples implied too many decisions on the theoretical level for us to risk here. Instead, we're going to fancy we need holidays. Let's see how we can retrieve properties of some hotels we have in memory. … Continue reading Search functions

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

How to retrieve information

Defining good and better ways of extracting information from an SQL base is a field of investigation in itself, however there are some peculiarities in the structure of Unidatab, that make it unexpected to people used to classical SQL databases. What kinds of output can we then expect from Unidatab? In this post we are … Continue reading How to retrieve information