On 3/2/06, Charles Finley <[log in to unmask]> wrote:
> 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.

Adam Dorritie wrote in response:
"I have no understanding of Eloquence's capabilities or internals, but
implying that SQL (although most contenders for the RDBMS title have
implemented it) is the defining characteristic of a relational
database management system is, well, wrong.
http://en.wikipedia.org/wiki/Dataphor"

Here's another way I could have written what I was trying to communicate.
It has been my observation, that popular tools that are either free or in
wide use are less likely to work well with Eloquence than they are with
Oracle, DB2 or Microsoft SQL Server.

Connie was concerned about how to respond to a growing interest at her
organization for tools that will allow the users to have access to company
data using web-based tools and frameworks.  In my opinion, she will be
better able to do this with one of the RDBMS's named above or even with
Mysql, Postgresql or Apache Derby.

So, if it is more appealing and less controversial allow me to offer that
you replace "Eloquence is NOT an RDBMS" with "Eloquence is not popular
enough for people who build the popular tools to target".  This would then
imply that with Eloquence in the future, at least in terms of development
tool availability is concerned, you may not be any better off than you are
with TurboIMAGE today.

I have little or no knowledge of what is pure SQL and what is not, so I
don't what to give the impression that I have anything at all to say in that
arena.


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 *