From: John R. <jr...@ce...> - 2011-11-26 18:32:41
|
On Nov 26, 2011, at 8:45 AM, Doug Blank wrote: > For example, we have a web-based, server version of Gramps under > development (http://gramps-connect.org/) that promises to be a good > solution for large databases, and collaborations. We just recently > learned that the current Gramps Gtk-based structure can't be beat in > terms of efficiency of access. We now replicate that structure in SQL > on the webserver, so that one can run all of the same code. One option > that this suggests (at least to me) is that we could keep the current > hierarchical Gramps data structures, but use something like sqlite (or > a No-SQL product) as the backend. Sqlite has a good record of > remaining backwards compatible [1]. There are many other viable > options that did not exist 6 years ago when the decision to switch to > BSDDB was made. Doug, If you're really thinking about changing the backend architecture, I suggest that you have a look at XQuery-based XML solutions like Oracle's DBXML [1]. Although most commercial Genealogy applications do use some sort of relational database for a backend, the fixed-format table structure is less than ideal for genealogical data. Semi-structured solutions are more appropriate, and XQuery provides a ready-made and very rich query framework for accessing the data. Regards, John Ralls [1] http://www.oracle.com/technetwork/database/berkeleydb/overview/index-083851.html |