Re: EDS and SQL
Matthew Lewis wrote:
<snip>
> Has anyone worked on writing a SQL engine for use with EDS?
</snip>
Its not even to pre-alpha yet, but I am working on an Object Euphoria
Database Engine. This is an ambitious project and it is an open question
when I can be ready to release anything.
Planned features are:
1. Fields with arbitrarily complex subfields accessible by dot notation.
2. Data typing of fields--field may be required to contain data of any
Euphoria type or user-defined type.
3. Indexes for fast search/sort on any field or fields.
4. Links between tables with referential integrity.
5. A SQL-like query language.
6. Other data manipulation methds.
I suspect #5 will be implemented as a script interpreter which translates
EuSQL into direct data manipulation methods (#6)--which would also be
available to the user for those who prefer them.
The advantage of using Object Euphoria is that all the structural data can
be read in when the database is opened and maintained and manipulated by OOP
objects. The OOP approach will automate the handling of indexes and all the
complex bookkeeping that goes into a database being accessed in this
fashion--much more is required than in simple EDS where key searches are
highly optimized but searches on non-key fields requires a sequential
search.
The disadvantage is the OOP overhead--my hope is the fast search and sort on
non-key fields will make up for this and speed will be nearly as good as
EDS.
I would be glad to correspond with you or anyone about this--it is likely
that many ideas about the structure of the EDS database will be applicable
to both OOP and non-OOP implementations these design concepts.
-- Mike Nelson
MichaelANelson at worldnet.att.net
|
Not Categorized, Please Help
|
|
