1. Euphoria file structure
Hi all
My main interest with Euphoria is DBMS. If i'm going to put my efforts
in that direction, I have to make a decision about a major issue: work
with the native internal Euphoria file format using a single file for
program data etc, when using EDS, or work with external data files. The
more serious DBMS use the design/data separation model. It make sense.
If you modify your design like adding a different input screen, it does
not affect the data in any way. Yet popular DBMS such as FileMakerPro
uses the "all in one file approach" very successfully. However if the
file get corrupted, you don't know what is corrupted: design or data?
Using the internal format of Euphoria is appealing. It's easier and you
readily benefit of the flexible structures of the language. The file is
in binary format I believe.
My main question then is: How can you examin in a human readable format
the data of an EDS in an editor to verify its integrity if something
turns sour. A comma delimitted file is easilly visible in a simple text
editor. Is such facility posslble with an Euphoria file?
TIA
Serge Lavigne
2. Re: Euphoria file structure
On Fri, 18 Jul 2003 15:47:04 +0000, jondolar <lavigne.s at videotron.ca>
wrote:
>My main question then is: How can you examin in a human readable format=20
>the data of an EDS in an editor to verify its integrity if something=20
>turns sour. A comma delimitted file is easilly visible in a simple text=20
>editor. Is such facility posslble with an Euphoria file?
>
Visit http://www.rapideuphoria.com/contrib.htm and type in eds. There
are several. Matthew Lewis has just updated his. You could even just
use db_dump(open("test.txt","w"),0) and view test.txt
The main question you should be asking is: How do I write the software
so that if, at some point in the future, I decide the data would be
better off stored in a different format, it will be relatively easy to
change?
If you use something like Jordah Ferguson's safe edb wrapper, then
hopefully it is simply a matter of re-writing that 400-line source
(and a little ditty that uses JF's code and your new version of it to
transfer the data, if needed).
At the moment, I'm using something similar, which I've shrouded during
development. That way I cannot inadvertently invoke the db_ routines
directly (I cut and paste a bit manically sometimes).
Pete
