Re: [Gramps-devel] External databases

[Douglas S. B. <db...@cs...>]

> 2008/4/11, Lee Myers <Le...@lo...>:
>>
>> Dev's,
>>
>> Is there a chance we might eventually be able to use an external
>> database
>> like MySQL or Postgresql with Gramps it would make it so if someone was
>> making a web page with content for their file they could easily change
>> the
>> information if it was set up right.
>
>
> Some people have started something like that. However, large parts of
> GRAMPS
> should be rewritten to make this possible.
> The database now is BSDDB though, and you can access that from python or
> other languages just fine, so no need to do a different database.
> Moreover,
> using the same database, and using python for the webpage generator, means
> you can reuse the GRAMPS database access methods.
>
> However, GRAMPS is single user, to make what you want , not the database
> is
> of importance. What is important is to rewrite GRAMPS as a client server
> program, allowing multiple users (clients) to work on one DB (via the
> server).
>
> This is not really need it just kind of came to me it might not even have
> to
>> be the main database just a sub data base (though I suspect it would
>> most
>> likely be a plugin then).
>>
>> I would work on this but I am still learning python.
>
>
> If you learn python, you could concentrate on  learning a webpage server,
> you find some resources here: http://py.vaults.ca/apyllo.py?i=127386987
> There are too little developers on GRAMPS to support another database
> (every
> change must be done in every backend, and know we already have XML, BSDDB
> and GEDCOM, which is _a_lot_ of work).

My plan, once I get all of the smaller things on my todo list finished, is
to concentrate on exploring a SQL backend for GRAMPS. I believe that
GRAMPS could be even faster than it is today, and handle much larger
database as fast as it handles smaller databases, for most all functions.

In addition, it could be multiuser, have different front ends, like a
web-based one, and could be used directly in other applications. It would
also be easier to make changes to the database. (I didn't realize how hard
it would be to add a new field to a Date object until I saw that I needed
to go through every object that contained a date, unpack it, add it
manually, repack it, and save. That took me a week of research. It would
have been a 10 second change in a SQL database.)

I'll probably begin some experiments this summer, given that I get
everything else done. The conversations about exactly what would need to
be changed in the GRAMPS DB API, and whether this would be accepted, would
follow.

-Doug

> Benny
>
> Thanks Lee Myers
>>
>> --
>> http://www.whylinuxisbetter.net/
>> Go ahead check it out!
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
>> Don't miss this year's exciting event. There's still time to save $100.
>> Use priority code J8TL2D2.
>>
>> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
>> _______________________________________________
>> Gramps-devel mailing list
>> Gra...@li...
>> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>>
>>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone_______________________________________________
> Gramps-devel mailing list
> Gra...@li...
> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>