1. Re: Db - Final Question
Your advice needs a bit of rethinking. In it's present state, EDS is
only reasonable for single user prototyping. There is no current way to
make an EDS database thread-safe or easily recoverable. We don't
have control of the IO in a way that allows us to easily flush buffers
when necessary. EDS doesn't have things like "commit" and "rollback",
or even logging, though that wouldn't be too hard to add. Since the
data involved is normally the source of value in an application,
neglecting that aspect of the project is more than a bit shortsighted.
The
only time that EDS would be even slightly commercially practicable
in a multi-user, multi-tasking environment would be in a read-only style
database. Of course I have entirely neglected whole areas of
functionality
such as embedded triggers, replication, and most important of all,
security.
Advice based on dreams, supposition and non-existant vaporware for a
project that, according to the requestor, will begin today should be a
little more grounded.
Everett L.(Rett) Williams
rett at gvtc.com
