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

Update 2.2: 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 Update 2.2: purifying Unidatab

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

Unidatab-CGI reloaded

check it out! (on https://github.com/emilbarton/Unidatab-CGI) This old graphical interface to Unidatab has been rewritten entirely to conform to the new version Unidatab. Experimenting with the software is now fairly easier. The output is always readable while Unidatab function calls are made automatically after filling out the proper fields on a web page and clicking the … Continue reading Unidatab-CGI reloaded

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

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