2012/6/27 Ron Johnson <ron.l.johnson@cox.net>
On 06/27/2012 04:32 AM, Benny Malengier wrote:
> 2012/6/27 j debert <jdebert@garlic.com>
>
>> On 06/26/2012 06:20 PM, john wrote:
>>> Is any work being done to move Gramps to either SQLite or one of the
>>> other SQL databases (MySQL, Prostgres).
>>
>> SQLite sounds like a good idea. The db isn't centralized like mysql,
>> etc., so the db can be kept in Gramps working directory, which makes
>> it portable. And SQLite doesn't have to run as a daemon, it doesn't
>> need to run until needed. Also, there's plenty of external tools for
>> SQLite which means that everything db doesn't need to be incorporated
>> into Gramps. Gramps could even be made leaner by delegating internal
>> db functions to external SQLIte utils and perhaps even call SQLite
>> executables to handle the db and maintenance. That would conserve
>> system recources, using only what's needed when needed. And it would
>> free Gramps developers from having to maintain all the db functions.
>>
>
> 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.

Treating SQLite just as portable record storage is OK.

>
> 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 however.

http://sourceforge.net/mailarchive/message.php?msg_id=29369113

Platform portability and database sharing is *manifestly* broken.

Directly converting bsddb operations to SQL INSERT, UPDATE, DELETE &
SELECT statements (no need to alter the existing schema) would open up
possibilities that are now impossible.

>
> Keep in mind that we now can work highly optimized with a very low level
> database layer. This is not something we should throw away.
>

Only if SQLite is significantly slower.

It is a discussion that should be held on the devel mailing list.
As gramps-connects works like this, if all works good, we could incorporate it  back into the main core, as long as django is not an install requirement. Using django allows sqlite or progress or mysql, without changing the code.

Benny

--
"There is usually only a limited amount of damage that can be
done by dull or stupid people. For creating a truly monumental
disaster, you need people with high IQs."
Thomas Sowell



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Gramps-users mailing list
Gramps-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gramps-users