Computers: Universe: A Note on SQL

With a few tweaks and reservations, UniVerse supports the Structured Query Language or SQL, which might be seen as an alternative to RetrieVe, particularly to those familiar with SQL after experience with database such as Oracle and Ingres.

From a technical point of view, this support is both impressive and worthwhile. Impressive, because SQL was not designed to deal with typeless, 'post-relational' (which means basically 'non-relational') databases like PICK. Worthwhile, because anything that smooths the conversion of a computer system from an existing base and preserves code is worthwhile.

However, I do not recommend the use of SQL for the development of new enquiries and reports, much less its use as the primary reporting engine in an entire system. If it's SQL you want, you really are better off using a product like Oracle, which was designed to work with it, and which extends it (via languages like 'PL/SQL' or 'Procedural SQL') into the primary development lanuage too: giving you a far more consistent development platform.

Successfull systems were being developed using PICK systems, and the forerunners of RetrieVe, well before SQL was supported. The SQL support does not fill any functional gap, but rather adds a handy piece of support when porting systems.

The issue is similar to that between vi and ED. Whatever objective comparisons might be made between the tools, they assume a level playing field which does not exist. ED and RetrieVe start with the enormouse advantage of having been specifically designed for the environment within which they work.

For these reasons, this course does not cover SQL, even though it is supported. If you already know it, you don't need my help with it. If you don't, don't learn it to use with UniVerse, spend the time learning RetrieVe.