Re: GEDOM as a database format
- From: Wes Groleau <groleau+news@xxxxxxxxxxxxx>
- Date: Fri, 28 Sep 2007 00:49:05 GMT
Dennis Lee Bieber wrote:
What happens when you edit a data field and the line length changes?
You now have to move all the data that followed the change down to make
room for the new data. GEDCOM files are not fixed-length lines (there
True, if you are editing it's a different thing from browsing.
My program split the GEDCOM into level zero records, and put
them into a BerkeleyDB with the @xref@ as the key (HEAD and TRLR
used their tags as the key).
So although the stoage medium was not a single GEDCOM file, the
records remained in GEDCOM. And output was merely pulling the
desired records and concatenating them.
> GEDCOM doesn't have any way to have a record say "this field is really
> located down there because it grew too large for this space"
Doesn't need it. That's the job of the lower level routines.
I don't worry myself in vi about what happens under the hood
when I add characters to a line.
The genealogy application should deal with the data (whether GEDCOM
or other format) and let the XML API or text file API or SQL DB
or whatever maintain the storage format for that data.
He that is good for making excuses, is seldom good for anything else.
-- Benjamin Franklin
- Prev by Date: Re: GEDOM as a database format
- Next by Date: Re: GEDOM as a database format
- Previous by thread: Re: GEDOM as a database format
- Next by thread: Re: GEDOM as a database format