Louis Kessler’s Behold Blog The Behold User Forum
Blog Comments
302.
Database Design for Genealogy Data - Blog comment by arnold - 24 Jul 2015
Louis,
Having played with both Mysql & Sqlite, I can well understand - specially since I am not the one who has to do the work :-)
303.
Database Design for Genealogy Data - Blog comment by lkessler - 23 Jul 2015
Arnold,
I selected SQLite because its a multi-platform, speedy, single file database with a small footprint that’s embeddable within the program.
However, the FireDAC framework in Delphi theoretically lets switch one database to another without changing code, so it will be possible to switch in the ...
304.
Database Design for Genealogy Data - Blog comment by arnold - 22 Jul 2015
Thank you for the latest version - haven't tried it much as yet, but I'd like to add a comment re you choice of database.
As well for the good analysis if the state of affairs of some of the current apps.
While I can see the attractiveness of Sqlite, it may turn out to be not the best if you ever are going ...
305.
Complete Genealogy Data Transfer - Blog comment by lkessler - 15 Jul 2015
Darren,
Oh I see now. You just want to make sure that the program actually loads the data into its database. The "make an edit" and "undo" is to ensure that.
I don't know if that's necessary. I can't really see how a program can load in an input file without loading it into its internal database. To ...
306.
Complete Genealogy Data Transfer - Blog comment by cleaverkin - 15 Jul 2015
Rather than "make an edit" and "undo", I probably should have said "add one data item" then "delete that item".
It does at least insure that data not understood by the program is retained, and exported with exactly the same structure as was imported.
Darren Price
307.
Complete Genealogy Data Transfer - Blog comment by lkessler - 15 Jul 2015
Darren:
I suppose few programs would have any trouble adding one event and then deleting it, or deleting one event and then re-adding it. Even adding or deleting an individual, and then deleting or re-adding him should be straightforward as long as all the parent/child/spouse links are re-added as well. In ...
308.
Complete Genealogy Data Transfer - Blog comment by cleaverkin - 14 Jul 2015
I propose a conformance requirement possibly more strict than what Louis describes. I think that in order for any software tool that performs both import and export should pass the following test: (1) Import any standard-conformant data file; (2) make one edit to the file; (3) undo the previous edit; (4) ...
309.
Behold Version 1.1 - Blog comment by lkessler - 1 Jul 2015
Klemens,
Events without dates generally show up first, with a few exceptions (e.g. Behold tries to be smart about marriages and births and keep them in order if possible).
When I say "event", I am also including facts and other information that normally don't include dates, e.g. height, eye color, number ...
310.
Redefining Plans - Blog comment by klemens - 1 Jul 2015
> As soon as I have something working enough to show the concepts, I’ll try to make it available.
Yes, I think that is a good way to go. You will get feedback early and often, which will help development. And people will start to see earlier what you're aiming at.
For myself, if you actually get ...
Prev 291-300
Database Design for Genealogy Data - Blog comment by sam888 - 25 Jul 2015