RE: EDB from a system designer's viewpoint
guest at rapideuphoria.com wrote:
>
>
> posted by: shenpen at freemail.hu
>
> Hi!
>
> I'm new to EUPHORIA. I like it very much, because it seems to achieve
> the
> impossible: to be simple and elegant, but still able to get close to the
> machine if needed. I'm quite enchanted that only one step under the
> elegant EUPHORIA library routines there is usually a machine_proc()
> or machine_func() - this is the way things should be in all languages...
> 
>
> I'm actually more of a system designer (SD) than a programmer, so what
> I'm
> most interested in is the EDB. Well, it seems a bit "untraditional" to
> me.
>
> So let me ask how traditional relational SD issues are
> usually handled in EDB.
>
> 1) Keys.
> 2) Transaction management, commit/rollback features.
> 3) Multi-user features - locking.
Hi Miklos:
The short answer is: use another database engine.
EDB was not designed to do those things, and although you
might be able to implement some of them (such as indexing)
with your own code, there just isn't any support in EDB.
Even Euphoria itself lacks things like structured records
which would make implementing a robust database easier.
EDB is great for simple databases, and it's easy to use.
What you are wanting to do requires something better
(which will also be harder to use). Something like PostgreSQL
or Oracle.
Regards,
Irv
|
Not Categorized, Please Help
|
|
