File: README

package info (click to toggle)
nosql 0.9-0
  • links: PTS
  • area: main
  • in suites: hamm
  • size: 1,364 kB
  • ctags: 225
  • sloc: perl: 3,766; sh: 476; makefile: 41
file content (43 lines) | stat: -rw-r--r-- 1,701 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43

                    NoSQL RDBMS

NoSQL is a fast, portable, relational database management
system without arbitrary limits, (other than memory and
processor speed) that runs under, and interacts with, the
UNIX Operating System.

It uses the Operator/Stream DBMS paradigm described in "Unix
Review", March, 1991, page 24, entitled "A 4GL Language".
There are a number of "operators" that each perform a unique
function on the data. The "stream" is suplied by the UNIX
Input/Output redirection mechanism. Therefore each operator
processes some data and then passes it along to the next
operator via the UNIX pipe function. This is very efficient as
UNIX pipes are implemented in memory. NoSQL is compliant with
the "Relational Model". Read the document "4gl.ps", included
with the distribution, for further details.

See file "Install" for installation instructions.


Performance issues :

The relation operators provided with NoSQL are either
Perl or Shell scripts. In normal operation, commands 
need to be piped one into the other to produce the
final output (Operator-Stream Paradigm).
This is fine for using the operators interactively,
where the overhead involved by spawning the relevant
interpreters several times may not matter much.
However, if NoSQL's data structures (tables) are 
used as a database back-end for other programs (like
www CGI scripts), then you should consider taking a more
efficient approach. I personally use the normal utilities
that come with Linux, like "awk", "grep", "cut", "join",
and so on. Of course then you need to handle the table
headers inside your code before calling those utilities
on table bodies. 


Please report bugs to C.Strozzi, <carlos@linux.it>