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

Advertisements

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

Note on coercion

In the last post we saw several means of organizing data, namely templates, subsumption, and examplification. However, those means could be made more effective if there was more direction on how they operate. For instance, examplify() should be able to feed a record without having to repeat type names explicitly, but we didn’t choose the … Continue reading Note on coercion

How to use subdatabases

Subdatabases (subdbs in short) do not differ deeply from formats, but provide a type-record and thus allow subrecords to be created according to a defined structure. When subdbs are there, functions such as examplify(), subsume(), templatize() and get_subject() become available. ? select * from subdbs i sdb n a t u: -47 ~ #Data Structure … Continue reading How to use subdatabases

How to modify information

No surprise that with various recording levels, Unidatab provides also various means of modifying information.  Let' start by looking at how we can change some input data and we'll admit that we should better act on properties and types. Changing data Since pure data is only entered once and not duplicated, we understand that changing … Continue reading How to modify information