Section 1 of 4 - Prev - Next All sections - 1 - 2 - 3 - 4
Archive-name: databases/free-databases
Last-modified: 1997/08/06
Version: 2.0
Catalog of Free Database Systems
This document attemts to catalog databases that are
available without payment and with source.
The latest version of the document can be ftp'ed: get
pub/free-databases from ftp.idiom.com. The latest version is
always posted; the ftp version is never ahead.
There is a WWW version provided by Karl Guggisberg of the Software
Composition Group: http://cuiwww.unige.ch/~scg/FreeDB/
I will post this document about once a year to comp.databases,
comp.databases.object, comp.answers, and news.answers. I will also
post it to other groups somewhat randomly.
Please send additions, corrections, and donations to
David Muir Sharnoff
I would like user testimonials. I want to know which databases
are usable and which are trustable! Is there any database on this
list that I could store payroll records on? I have not used any
of these database nor have I used many commercial databases. I am
not qualified to answer your database questions or able to reccomend
a database for your use. Please try not to ask.
Thanks,
-Dave
Idiom Consulting, Berkeley, CA
Copyright (C) 1993-1997 David Muir Sharnoff, All rights reserved.
---------------------------------------------------------------------------
Prototype entry:
name: The name of the package
version: The current version number of the package
direct inquiries to "contact."
interface from: (interface packages only) front end protocol/program/language
interface to: (interface packages only) back end protocol/program/server/etc.
interfaces: The external interfaces that are supported by
the package. Common interfaces are: SQL, ESQL,
dbm, X, etc.
access methods: A list of the database access methods that are supported
multiuser: Can more than one person access the package at
the same time.
transactions: Does the package support transactions? (Consitency, rollback,
and rollforward?)
distributed: Does the package support distributed databases?
query language: What query languages does the package support
if any? SQL, QUEL, etc.
index size: (full text packages only) the size of the index as a percentage
of the size of the text to be indexed.
limits: Any known, annoying limits
robustness: Can this package be used on mission-critical data? Is the
package bug free? Does it crash? If it supports multi-user
transactions, does it make guarentees and keep them?
description: A description of the package.
references: Pointers to other documentation (not including that which
is included in the package)
status: current developement status (supported, actively developed, etc)
announcements: Where to get announcements
discussion: Where to send, or how to join discussions about the package
bugs: Where to send bug reports
requires: Special requirements for installing or running
ports: What does the package run on?
restrictions: Special copyright or other restrictions on the software
author: The primary author, if known. If not known,
contact: The current contact point. If not specified,
use "author."
how to get: Instructions for obtaining the package
updated: When the package was last updated (yyyy/mm/dd)
---------------------------------------------------------------------------
--------------------------- relational databases --------------------------
---------------------------------------------------------------------------
name: Beagle SQL
version: 1997/04/03
interfaces: SQL, C API
access methods: Btree
multiuser: ?
transactions: ?
distributed: no
query language: SQL
limits: ?
robustness: Quote from disclaimer: "This code WILL contain bugs"
description: A client-server database system under development. Beagle
SQL supports variable length records.
status: under development
discussion: send "SUBSCRIBE beagle your name" to istproc@brttech.com
ports: unix, OS/2
author: Robert Klein
how to get: http://tiny.iapnet.com/rob/beagle.html
updated: 1997/04/03
name: Datascope
version: 3.1
interfaces: C, Fortran, Perl, Tcl, command-line, X11
multiuser: no
transactions: no
distributed: no
query language: ?
description: A major component of the Datascope Seismic Application
Package is a relational database system, Datascope. Although
it is used primarily for seismic applications at the JSPC,
it is a general purpose database system which can also be
useful outside the seismic community. Datascope is a
relational database system in which tables are represented
by fixed-format files. The system provides the standard
operations on relational database tables: subsets, joins,
and sorts. And, since the data is typically plain ascii,
it's also possible to just use standard UNIX tools like
sed, awk, and vi. Some features:
+ It is possible to store ranges as keys and index them
+ Attributes can have units
+ Support for foreign keys
Datascope provides a cheap, easy, fairly intuitive way of
moving from the traditional plethora of formats to a better
approach which organizes the data, documents it, and
provides powerful tools for manipulating it.
status: ?
ports: SunOS, Solaris, Irix
author: Daniel Quinlan
how to get: http://jspc-www.colorado.edu/software/software.html#datascope
updated: 1996/01/01
name: DiamondBase
version: 0.31
interfaces: C++ library
access methods: b+ tree
multiuser: very limited
transactions: no
distributed: no
query language: C++ methods
limits: limits are set at compile time. The default max records
is 21474836.
robustness: The database engine is quite stable. The multi user
component is a more recent addition, and is still considered
beta. The single user version is separate however and
unaffected.
description: DiamondBase is written entirely in C++, and uses a schema
compiler to generate C++ class defintions for the objects,
as well as some comparison code which is also linked in to
the final executable. Facilities are now available to access
generic relations without providing comparison code. It
was written originally as a replacement for MetalBase which
was too slow. DiamondBase is very fast.
announcements: send mail to Darren Platt to be put on their list
questions: send mail to Darren Platt
bugs: send mail to Darren Platt
requires: C++
ports: many Unix platforms and OS/2 under cfront or gcc or
Borland's compiler. Recent ports to Dos/windows.
restrictions: Free usage for non-commerical applications -- negotiate
anything else.
author: Kevin Lentin, Andrew Davison, Darren Platt
contact: Darren Platt
how to get: http://www.cs.monash.edu.au/~darrenp/diamondbase.html
updated: 1994/12/22
name: GNU SQL
version: 0.7b5.3
interfaces: SQL
access methods: B-tree
multiuser: yes
transactions: yes
distributed: no
query language: SQL
limits: ?
robustness: ?
description: SQL Server is a free portable multiuser relatational database
management system. It supports the full SQL89 dialect and
has some extensions from SQL92. It provides multiuser access
and transaction isolation based on predicative locks. The
working OS: UNIX. The working language: C . It also uses
RPC, shared memory and message queues.
references: http://www.ispras.ru/~gsql
status: actively under development
bugs: bug-gnu-sql@prep.ai.mit.edu
restrictions: GNU General Public License
author: Sergev Kuznezov, Michael Kimelman, Vera Ponomarenko,
Kostya Dyshlevoi, Andrew Yahin
contact: gss@ispras.ru
how to get: ftp://alpha.gnu.ai.mit.edu/gnu/gnusql-*
updated: 1997/06/12
name: LEAP
version: 1.0
interfaces: command line
access methods: ?
multiuser: no
transactions: no
distributed: no
query language: relational algebra
limits: ?
robustness: fine for educational purposes
description: LEAP is a an educational tool. It is a full relational
database system. It uses relational algebra as a query
language. LEAP allows practically all the algebraic examples
in many popular DBMS books to be entered with little or
no modification. Leap is written in C and fairly simple.
status: actively developed
ports: DOS, Windows, unix
restrictions: GNU General Public License
author: Richard Leyton
how to get: http://www.dogbert.demon.co.uk/leap.html
updated: 1997/05/24
name: MetalBase
version: 5.0
interfaces: custome C library
access methods: AVL-trees
multiuser: yes, but in theory race conditions still exist
transactions: yes
distributed: no
query language: "Report", and "View Relation" a curses based viewer
limits: ?
robustness: data corruption is possible when MetalBase is not shut
down correctly
description: MetalBase is a small relational database. It has all the
pieces that a relational database should C interface, curses
interface, report writer, etc. It does not have design which
takes advantage of shared memory or the better access methods.
None of the interfaces are standard, but all of them are easy
to use.
discussion: mbase-request@internode.com.au
requires: curses
ports: Linux, MS-DOS, Amiga, NeXT, Coherent, Macintosh MPW, SGI, Xenix
restrictions: donations are suggested
author: Richid Jernigan / PO Box 827 / Norris TN 37828
how to get: ftp systems/unix/linux/sources/usr.bin/mbase.tar.z
from ftp.uu.net
updated: 1992/10/01
name: mSQL (Mini SQL)
version: 1.0.9
interfaces: C, ESL, Tcl, Perl, Python, NextSTEP, X11
access methods: Flat data with external primary key mapped into virtual
address space of server process.
multiuser: yes (25 simultaneous connections)
transactions: no
distributed: no
query language: SQL
limits: none
robustness: Pretty good - getting better all the time. One positive
user testimonial so far.
description: Mini SQL or mSQL is a light weight database engine that
supports a significant subset of the ANSI SQL specification
(including joins, ORDERing, DISTINCT, NULL handling, etc).
It is a single proces engine and doesn't use vast amounts of
system resources as other engines can. It supports
client server operations over TCP/IP networks and provides
quite reasonable performance. As an example, on a clunky old
25mhz 386 running Linux (one of the supported platforms) a
sustained rate of 67 inserts per second was achieved
during the insertion of 100,000 table entries.
discussion: msql-list-request@bunyip.com
ports: SunOS, Solaris, HP-UX, AIX, Linux, FreeBSD-2, SCO, SVR4,
NeXT, Cray Unicos, OSF/1, Ultrix.
restrictions: free for NON-COMMERCIAL USE ONLY
author: David Hughes
how to get: ftp pub/Minerva/msql/ from Bond.edu.au
updated: 1995/10/29
name: MySQL
version: 3.20.24a, 3.21.4-alpha
interfaces: SQL, ODBC, C, Perl, JAVA, C++, Python, command line
access methods: B-tree on disk, hash tables in memory
multiuser: yes
transactions: no, but tables can be locked in 3.21
distributed: no, mirroring is possible
query language: SQL
limits: 16 keys / table, max key length: 500 bytes
robustness: B-tree code is extreamly stable; 24 hour operation is possible
description: MySQL is a fully functional relation database. It supports
a subset of ANSI SQL and includes many extensions. It
has a C API that is very similar to mSQL's. Some features:
+ multi-threading;
+ all password traffic is encrypted.
+ all columns have default values
+ table check and repair utility included
+ table and column aliases as per SQL92 standard.
+ no memory leaks (purified)
+ all joins made in one pass
+ fixed and variable length records
status: actively developed and commercially supported
ports: BSDOS, SunOS, Solaris, Linux, IRIX, AIX, OSF1, BSD/OS, FreeBSD
restrictions: Commercial redistribution requires a license
author: Michael Widenius
contact: mysql@tcx.se
how to get: http://www.tcx.se
updated: 1997/08/05
name: PostgreSQL
version: 6.1.1
interfaces: SQL, C API, C++ API, Tcl API, Perl5 API, Python API,
WWW Gateway, JDBC driver, X11
access methods: Heap plus secondary indexes: B-tree, R-tree, Hash.
multiuser: yes
transactions: yes
distributed: no
query language: SQL
limits: ?
robustness: ?
description: PostgreSQL is derived from the Postgres research database.
It is a full-featured object-relational database system. It
supports declarative queries in SQL, query optimization,
concurrency control, transactions, multi-user support and
a number of security features. Extensibility features
include user defined operators, types, functions and access
methods. Application programmer interfaces (APIs) exist
for C, C++, Java, Perl4, Perl5, Python, SQL and Tcl. ODBC
and JDBC drivers are available from commercial sources and
free versions are under development.
status: actively developed
bugs: mailing list: pgsql-bugs@postgresql.org
ports: Linux, Solaris, Digital Unix, *BSD and more
contact: mailing list: pgsql-questions@postgresql.org
how to get: http://www.postgresql.org
updated: 1997/07/31
name: Postgres
version: 4.2 beta
interfaces: libpq (C interface), pgbrowse (tk-based browser)
access methods: Heap plus secondary indexes: B-tree, R-tree, Hash.
multiuser: yes
transactions: yes
distributed: no
query language: Postquel (incompatable, extended variant of QUEL)
limits: ?
robustness: The authors say: "It is not up to commercial levels of
reliability. I would not want _my_ payroll records in it :-)"
description: Postgres is a database research project under Prof. Michael
Stonebraker at U. C. Berkeley. To facilitate research
efforts, a software test-bed was created; this is the
"Postgres" DBMS software. The Postgres DBMS is extended
relational or object oriented, depending on the buzzword du
jour. Postgres is relational. It is highly extensible. It
has object oriented features like inheritance. it has query
language procedures, rules, updatable views, and more.
references: There are may papers available, both through ftp and as
hard-copy technical reports. Cruse the ftp site for papers
or mail Michelle Mattera
status: orphaned
discussion: send "Subject: ADD" to postgres-request@postgres.berkeley.edu
linux: send "X-Mn-Admin: join postgres"
to linux-activists-request@niksula.hut.fi
bugs:
ports: full support: Alpha OSF/1 1.3+, Mips Ultrix .2+,
Sparc SunOS 4.1.1+, Power AIX 3.2.3+, HP-PA HP-UX 9.0+
comming soon: Sparc Solaris 2.3, i386 Linux
previous versions: i386 SVR4, i386 386BSD, i386 Linux,
i386 NextStep 3.1, NeXT NextStep 3.0,
Sparc Solaris 2.1+, HP-PA HP-UX 8.07
contact: developers:
admin: Michelle Mattera
how to get: ftp pub/postgres/postgres-v4r2* from s2k-ftp.CS.Berkeley.EDU.
pgbrowse: ftp pub/pgbrowse/* from crseo.ucsb.edu.
updated: 1994/04/02
name: PQL
version: 0.95
interfaces: interactive, stdin and shell mode
access methods: hash
multiuser: no
transactions: yes
distributed: no
query language: SQL subset
limits: ?
robustness: Early phase of release, still many bgs
description: PQL stands for "plain query language" and is a kind of SQL
(rather a subset) Nearly all features of SQL are supported,
like joins, subqueries and grouping. The join operation
has been optimized using a iterative "select and join"
algorithm which runs over all joined base tables.
In addition to the PQL-Interpreter, a relational and
transaction oriented database engine interface is shipped
with the package. The engine is based on the lower level
GDBM interface, a freely available database library.
requires: gdbm, GNU readline
ports: unix
author: Bjoern Lemke
how to get: ftp://ftp.uni-stuttgart.de/pub/unix/database/pql-0.95.tgz
updated: 1995/11/30
name: Qddb
version: 1.43
interfaces: query language, Tcl/Tk
access methods: ?
multiuser: yes
transactions: ?
distributed: no
query language: supports regular expressions; words, numbers, and dates;
and ranges of words, numbers, and dates.
limits: ?
robustness: The authors indicate that they believe it to be stable.
description: QDDB stands for 'Quick and Dirty DataBase'.
Qddb is a database suite that allows you to create relations,
add tuples, modify tuples, delete tuples, and search for tuples
in a fast and very flexible way. Qddb 1.40 can use Tcl as its
configuration language, so you can build custom interfaces to
your Qddb databases with it. We provide a reasonably nice
generic interface so you can be up and running quickly.
Qddb allows seaching on regular expressions and numeric and
date ranges.
A set of applications built on top of Qddb can be obtained
from the same ftp site as Qddb itself.
status: actively developed
discussion: send "Subject: subscribe" with your address in the body to
qddb-users-request@ms.uky.edu
bugs: qddb-bugs@ms.uky.edu and qddb-users@ms.uky.edu
requires: Tcl 7.3, Tk 3.6p1
ports: Ultrix, OSF/1, BSD/386, Linux, SunOS, Solaris.
restrictions: There are two versions of Qddb. One is covered by the
GNU General Public License. The other version is commercial.
author: Eric H. Herrin II ,
Raphael Finkel
how to get: http://www.hsdi.com/qddb & ftp://ftp.hsdi.com/pub/qddb/sources
updated: 1997/06/10
name: REQUIEM
version: ?
interfaces: RQL, ERQL (extension)
access methods: B-tree indexes can be created on attributes of base relations.
multiuser: yes (multiuser extension)
transactions: yes (multiuser extension)
distributed: no
query language: RQL
robustness: [seems to maintained by zero to few people --ed]
description: REQUIEM (RElational Query and Update Interactive systEM) is
an extensible, relational DBMS developed in C with a query
language based on the relational algebra called RQL (Relational
Query Language).
There appears to be three versions of REQUIEM: the base
version and two extensions. One extension adds multiuser
capability. The other adds an embeddable version of the
query langauge.
references: "An Extensible DBMS for Small-Medium Scale Systems",
Papazoglou, M.P., IEEE Micro, April 1989.
Relational Database Management - A Systems Programming
Approach, Papazoglou, M.P. and Valder, W., Prentice Hall
International, UK, 1989.
"The Development of a Program Interface for the RDBMS Requiem"
Power, R.A., 1991 Honours Thesis (dvi file available with
source code for the embedded version).
ports: Sparc/SunOS; base version only: MS-DOS, Macintosh
contact: (embedded version only)
Robert Power
how to get: ftp pub/requiem/REQUIEM.tar.Z (multiuser version) or
pub/requiem/Requiem.tar.Z (embeddable version)
from dcssoft.anu.edu.au
The base version can be constructed from the multiuser version.
updated: 1992/10/06
name: shql
version: 1.3 Beta
interfaces: SQL, shell
multiuser: no
transactions: no ?
distributed: no
limits: no NULLs in the data, spaces and backslashes may be added when
the data contains punctuation, GROUP BY is not implemented.
robustness: it is a shell script.
description: Shql is a program that reads SQL commands interactively and
executes those commands by creating and manipulating Unix
files. The program is patterned after Ingres' interactive sql
terminal monitor program.
requires: bourne shell with functions, awk, grep, cut, sort, uniq, join,
wc, and sed
author: Bruce Momjian
how to get: comp.sources.misc volumes 34, 41 and 42.
Also ftp pub/net-sources/shql-patch-1.3-beta from ftp.idiom.com
updated: 1994/08/06
name: Typhoon
version: 1.06
interfaces: C API
access methods: B-trees
multiuser: Yes, but no locking mechanism at this point (will come soon)
transactions: no
distributed: no
query language: none
limits: A single file cannot exceed 4GB.
robustness: The package is quite stable as it is shut down properly. It
is currently used in a system that handles billing
information (and some other applications).
description: Typhoon is a relational database management system. It was
originally inspired by Raima's db_VISTA (today Raima Data
Manager) but is relational rather than network based. Typhoon
lacks some of db_VISTA's features, but also contains a number
of nice features not found in db_VISTA.
All relations are defined in a so called Data Definition
Language (ddl) file. You define the database relations like
you would write a C structure with chars, ints, strings,
multidimensional arrays, nested union and structures, etc. Then
you define primary, alternate and foreign keys for each
relation. The Data Definition Language Processor (ddlp)
compiles the database defintion into a binary file which
constitutes the database description. The database relations
are accessed via C subroutines which manipulate individual
records within a table.
- Multiple open database
- Multi-field keys
- Nested structures in records
- Controlled unions
- Referential integrity
- Variable length fields
- Null keys (optional keys in db_VISTA, but easier to use)
- Dynamic opening and closing of database files
status: actively developed
ports: SCO UNIX, Solaris, Tandem NonStop UNIX, AIX, Linux and OS/2.
author: Thomas B. Pedersen
how to get: comp.sources.misc volume 44;
ftp pub/Linux/devel/db/typhoon-1.06.tar.gz from sunsite.unc.edu
updated: 1994/10/03
name: University INGRES
version: 8.9
interfaces: QUEL, EQUEL
access methods: heap, hash, isam, ordered
multiuser: yes
transactions: yes, but no multistatement transactions. Each statement
is ACID
distributed: no
query language: QUEL
limits: ?
robustness: Very mature technology
description: This is the database program that was the basis for INGRES
Corporation. Obviously, it does not have all the bells
and whistles of the current commercial product. However,
it is small and fast and it works.
So called ordered relations are slow and not locked.
references: "The INGRES Papers" Stonebraker ed. Addison Wesley
status: orphaned
ports: SunOS, Linux
author: The Ingres project at UC Berkeley.
contact:
how to get: ftp://s2k-ftp.CS.Berkeley.EDU/pub/ingres
updated: 1993/05/20
---------------------------------------------------------------------------
--------------------------- object oriented -------------------------------
---------------------------------------------------------------------------
name: EXODUS Project software
version: GNU E 2.3.3, Storage Manager (SM) 3.1
interfaces: GNU E, (C++ for direct access to the Storage Manager)
access methods: B+tree and linear-hashing based indexes
multiuser: yes, client-server
transactions: yes, but not nested.
distributed: yes, applications can access multiple servers in a single
transaction. Distributed commits are performed across servers
and clients have access to an interface allowing participation
in distributed commits managed by an external agent.
query language: GNU E -- a persistent programming language based on C++
robustness: High (at least for academic software).
The SM release includes a facility for regression
testing most features, including crash recovery.
description: The EXODUS Storage Manager (SM) is a client-server object
storage system which provides "storage objects" for storing
data, versions of objects, "files" for grouping related storage
objects, and indexes for supporting efficient object access. A
storage object is an uninterpreted container of bytes which can
range in size from a few bytes to hundreds of megabytes. The
Storage Manager provides routines to read, overwrite, and
efficiently grow and shrink objects. In addition, the Storage
Manager provides transactions, lock-based concurrency control,
and log-based recovery.
GNU E is a persistent, object oriented programming language
developed as part of the Exodus project. GNU E extends C++
with the notion of persistent data, program level data objects
that can be transparently used across multiple executions of a
program, or multiple programs, without explicit input and
output operations.
references: A bibliography of EXODUS related papers can be obtained from
the ftp site described below. Some of the papers are available
from the ftp server as technical reports, and are marked as
such in the bibliography.
status: No longer being developed. However, the authors are working
on a new system, SHORE, and will support current Exodus
users well enough to keep them going until SHORE is useable.
GNU E 2.5.8 is in beta and can be ftped.
discussion: Send "information exodus_all" to listproc@cs.wisc.edu to
find out how to join the exodus_all mailing list.
bugs: exodusbugs@cs.wisc.edu
requires: g++ 2.3.3 (exactly 2.3.3. GNU E 2.5.8 is in beta)
ports: MIPS/Ultrix, SPARC/SunOS, HP 7xx/HP-UX, Linux
restrictions: none, but see copyright notice located in all source files
author: The EXODUS Database Toolkit project at the
University of Wisconsin
contact: exodus@cs.wisc.edu
how to get: ftp exodus/* from ftp.cs.wisc.edu
updated: 1993/03/29
name: LINCKS (Linkoping Intelligent Communication of Knowledge System)
version: 2.5
interfaces: C library, emacs-like editor/X11
access methods: ?
multiuser: yes
transactions: no, but creates different versions on the fly
distributed: no, but maybe later
query language: hypertext-ish X user interface
robustness: The underlaying store handler (NODE) has been used since '89
and is quite stable. The system have betweem 20 to 500 users.
description: LINCKS is an object-centred multi-user database system
developed for complex information system applications where
editing and browsing of information in the database is of
paramount importance. The focus is on sharing of small
information chunks which combine to make up complex information
objects used by different users for different purposes. The
information chunks are semi-structured in that they contain one
part which is well-structured to facilitate addition of A.I.
processing within the system, and one part which is
unstructured and suitable for management by the user.
Features: shared composite objects, database history,
atlernative views, change collision notification (when more
than one person makes changes to the same composite object)
references: ftp://ftp.ida.liu.se/pub/lincks/articles/cscw.ps.gz
announcements: lincks@ida.liu.se
discussion: lincks-users-request@ida.liu.se
bugs: lincks-bugs@ida.liu.se
requires: Unix, X11R5
ports: Sun4/SunOS 4.1.[123], Sun4/SunOS 5.2, Sun3, Decstation, Alpha,
RS/6000, Sequent Symmetry, Linux, HP-UX, SGI, SCO, SVR4.2, Sony
restrictions: GNU General Public License
author: Lin Padgham, Ralph Ronnquist; University of Linkoping, Sweden
contact: lincks@ida.liu.se
how to get: ftp://ftp.ida.liu.se/pub/lincks/lincks-2.5pre5.tar.gz
updated: 1997/04/24
name: MONET
version: 3.05
interfaces: MIL (Monet Interpreter Language), ODMG (ODMG interface
to Monet), MOA (meta-model mapping system)
access methods: ?
multiuser: yes
transactions: yes
distributed: yes
robustness: Used commercially for data mining
description: The Goblin Database Kernel is a C/C++ library that provides
ACID properties on a DSM model, using main-memory database
algorithms, built on virtual-memory OS primitives and
multi-threaded parallellism.
The Monet Server runs multiple interpreter threads, which parse
MIL commands. It manages client acces through the internet, and
can runtime be extended with new modules.
The Monet kernel is designed as a microkernel DBMS. This design
keeps the code mean and lean. Different users can plug in
different extra functionality using extension modules. A set
of standard extension modules is delevered with the system
(like math, tcpip, temporal, cross tables, concurrency
control, performance profiling)
references: http://www.cwi.nl/~monet/
status: ?
ports: Solaris, ?
restrictions: ?
author: Research project at CWI (Centrum voor Wiskunde en Informatica)
and the University of Amsterdam
contact: ?
how to get: Unknown. The source code can be browed, but it's not clear
how to actually download it.
updated: ?
name: OBST
version: 3-4.3
interfaces: C++, Tcl, schema compiler, graphical object browser
access methods: extendable hashtable
multiuser: yes, but writing locks entire tables
transactions: yes
distributed: not yet
query language: C++, Tcl, graphical object browser
limits: 4 GB per container, 2^32 containers
robustness: OBST is quite stable since the start of '93. Releases were
made to enhance the coding quality rather than to add new
features. There are somewhere between 50 and 500 users.
description: The persistent object management system OBST was developed by
Forschungszentrum Informatik (FZI) as a contribution to the
STONE project (supported by grant no. ITS8902A7 from the BMFT,
i.e. the German Ministry for Research).
OBST was originally designed to serve as the common persistent
object store for the tools of an software engineering
environment.
An essential feature of STONE is that the object oriented
paradigm is pursued consequently as a key concept. OBST is the
common persistent object store for all tools within the STONE
environment.
OBST provides a rich OO model including multiple inheritance,
generics, overloading, and privacy. The schema definition
language is syntactically similar to C++. It comes with a
library of pre-defined classes like Set, and
List. New methods can be incrementally loaded at
runtime.
announcements: send 'add obst-announce' to obst-listserv@fzi.de
discussion: send 'add obst-forum' to obst-listserv@fzi.de
bugs: send OBST version, configuration options, C++ version, machine,
OS, and a description of your problem to .
requires: A C++ compiler (G++ 2.3.3-2.6.3 or AT&T 2.1/3.01)
ports: UNIX: SPARC/SunOS 4.1, Solaris 2, Linux, HP-UX, Ultrix, ...
restrictions: STONE is over; OBST is now a commercial product.
contact: obst@fzi.de
how to get: ftp pub/OBST/OBST3-4.3 from ftp.fzi.de
usa: ftp pub/database/obst/? from ftp.uu.net
uk: ftp computing/databases/OBST/? from src.doc.ic.ac.uk
updated: 1995/01/19
name: pfl
version: 0.2
interfaces: Built-in persistent functional programming language
access methods: no
multiuser: no
transactions: no
distributed: no
query language: functional programming
limits: Index size is limited by the amount of main memory available.
Selectors are a bit flaky when they contain more than about
10,000 tuples. Since the current implementation of the
language is interpreted it is very slow.
robustness: alpha release
description: pfl is a persistent programming language and database
environment. The language is functional.
references: "An Overview of PFL", 3rd International Workshop on Database
Programming Languages, 1991.
"A functional programming approach to deductive databases",
17th International Conference on Very Large Databases, 1991
Section 1 of 4 - Prev - Next All sections - 1 - 2 - 3 - 4
