UNIX databases - request for info
Beverly Dyer
bev at hlexa.UUCP
Wed Jun 20 23:32:50 AEST 1984
This is a request for information from anyone with INGRES,
or other UNIX database (UNITY, ORACLE, etc) experience.
We've used URSA (POLARIS); we're considering a switch to INGRES.
We'd consider anything else that looked good.
Problems with URSA (POLARIS) are summarized below, and also
a list of the features we want in a database manager.
We, of course, need speed, which may be incompatible with
some of the features we'd also like to have.
Comparisons of our wishlist with other DBMS are especially welcome.
There may have been a database discussion here recently, so
please reply by mail. If you want to know what responses I receive,
send me a request and I'll forward them; I'll also summarize to the net.
Beverly Dyer (harpo, ihnp4, decvax) !hlexa!bev
***********************************************************
Following are some of our negative reactions to URSA (POLARIS):
General problems:
Slow
Lack of support
Inflexibile
No concurrent access during append.
Unauthorized user access causes endless loop. (bug)
Security only implemented for database, not by record or field.
Rigid syntax
Inconsistent command syntax.
No data type or length checks.
Key searches for each append are time consuming and
should be optional.
C interface (RDLC)
Uncontrollable error messages... they go to standard out,
should be trappable.
No nested or recursive database calls.
No data type or length checks.
Messes up preprocessing, #include file expansion must
be done seperately.
Static coding only, dynamic queries would be useful.
Sentry interface:
Cant get to shell.
Inconsistency in commands and arguments.
Inconsistency with RDLC interface.
Poor report output.
Poor error messages.
****************************************
Ideal DBMS
Needs:
relational
supported
fast
Wishlist:
robust .. flexibile .. easy to use
no size limits (except ulimit)
security by database, record and field
virtually concurrent access
(locked for duration of update only)
ability to reformat tables (add new fields)
efficient keyed and indexed access - preferably also a tracking
mechanism to inform the user about space used for indexing
regular expression searching
backup procedure for system failures during appends
data translation (ascii <-> integer <-> floating, etc.)
useful report generation (graphics capability desirable)
(nlp interface desirable)
C interpreter:
ad hoc / dynamic queries (at execution time)
good (trappable) error codes
use of database calls as library functions
nested and recursive database calls
good I/O reading/writing to/from structures
get next function
Interactive interface:
consistent command syntax
good error messages
More information about the Comp.unix
mailing list