On 27/06/2012 5:32 AM, Benny Malengier
When I look at the diagrams of the Gramps database, as seen here,
it looks very complicated. The main problem that I have is that the
diagram shown is a .gif and does not scale very well. Which makes it
difficult to study and/or comment on.
2012/6/27 j debert <firstname.lastname@example.org>
On 06/26/2012 06:20 PM, john wrote:
SQLite sounds like a good idea. The db isn't centralized like
> Is any work being done to move Gramps to either SQLite
or one of the
> other SQL databases (MySQL, Prostgres).
etc., so the db can be kept in Gramps working directory, which
it portable. And SQLite doesn't have to run as a daemon, it
need to run until needed. Also, there's plenty of external
SQLite which means that everything db doesn't need to be
into Gramps. Gramps could even be made leaner by delegating
db functions to external SQLIte utils and perhaps even call
executables to handle the db and maintenance. That would
system recources, using only what's needed when needed. And it
free Gramps developers from having to maintain all the db
This questions pops up now and then.
The datamodel for gramps in SQL form would be huge. A lot of
queries to just build our view tables. This would not be a
saving as to the current model!
Doug tried a real SQL for gramps-connect, and it was much
slower than our current setup.
He now uses sqllite or another sql via django, but with tables
that are dumps of our bsddb tables. So SQL in name only.
I don't mind SQL, but I also think we need not fix what is not
broken. Also, we could have both, I once did a design for
that. Apart from another database engine, not much benefit
Keep in mind that we now can work highly optimized with a very
low level database layer. This is not something we should
I wonder if it needs to this complicated, maybe it might be a good
idea to do some data modelling with a view to normalizing and
simplifying the data structure.
IDIOT, n. A member of a large and powerful tribe whose influence in human affairs has always been dominant and controlling.