Whole document tree

Whole document tree

MySQL Reference Manual for version 3.23.51. - J What is Unireg? Go to the first, previous, next, last section, table of contents.

J What is Unireg?

Unireg is our tty interface builder, but it uses a low-level connection to our ISAM (which is used by MySQL) and because of this it is very quick. It has existed since 1979 (on Unix in C since ~1986).

Unireg has the following components:

  • One table viewer with updates/browsing.
  • Multi table viewer (with one scrolling region).
  • Table creator. (With lots of column tags you can't create with MySQL) This is WYSIWYG (for a tty). You design a screen and Unireg prompts for the column specification.
  • Report generator.
  • A lot of utilities (quick import/export of tables to/from text files, analysis of table contents...).
  • Powerful multi-table updates (which we use a lot) with a BASIC-like language with LOTS of functions.
  • Dynamic languages (at present in Swedish and Finnish). If somebody wants an English version there are a few files that would have to be translated.
  • The ability to run updates interactively or in a batch.
  • Emacs-like key definitions with keyboard macros.
  • All this in a binary of 800K.
  • The convform utility. Converts `.frm' and text files between different character sets.
  • The myisampack utility. Packs an ISAM table (makes it 50-80% smaller). The table can be read by MySQL like an ordinary table. Only one record has to be decompressed per access. Cannot handle BLOB or TEXT columns or updates (yet).

We update most of our production databases with the Unireg interface and serve web pages through MySQL (and in some extreme cases the Unireg report generator).

Unireg takes about 3M of disk space and works on at least the following platforms: SunOS 4.x, Solaris, Linux, HP-UX, ICL Unix, DNIX, SCO and MS-DOS.

Unireg is currently only available in Swedish and Finnish.

The price tag for Unireg is 10,000 Swedish kr (about $1500 US), but this includes support. Unireg is distributed as a binary. (But all the ISAM sources can be found in MySQL). Usually we compile the binary for the customer at their site.

All new development is concentrated to MySQL.

Go to the first, previous, next, last section, table of contents.