HP3000-L Archives

March 2006, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Charles Finley <[log in to unmask]>
Reply To:
Charles Finley <[log in to unmask]>
Date:
Thu, 2 Mar 2006 10:06:15 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (23 lines)
Tracy Pierce wrote:

"2) Showing my Eloquence ignorance, I've understood all this time that
it's the best of both worlds, and while not as uh robust as Oracle, it
qualifies as an RDBMS.  Not so?"

My understanding is that the Eloquence database engine is written in the
same style as a modern RDBMS.  That is, the same code base could have been
used to implement an RDBMS.  However, what the programmer sees is the API
(Intrinsics, System Calls) not the internals.  RDBMS's are accessed with
some API that involves sending SQL statements to access data.  Eloquence is
not built to use a SQL API. Eloquence is NOT an RDBMS.

I usually associate robustness with reliability and I belive Eloquence to be
very reliable.  If you mean it to be feature rich, Eloquence is not a
feature rich as Oracle.

Charles Finley
619-795-0720

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2