[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnubg] gnubg database interface

From: Joern Thyssen
Subject: Re: [Bug-gnubg] gnubg database interface
Date: Sun, 4 Apr 2004 20:02:46 +0000
User-agent: Mutt/

On Sun, Apr 04, 2004 at 08:37:28PM +0200, Jim Segrave wrote
> On Sun 04 Apr 2004 (15:26 +0000), Joern Thyssen wrote:
> > Hi,
> > 
> > I've had a first go at the gnubg database interface.
> > 
> > I've commited a file gnubg.sql, which contains the DDLs for the database
> > and tables.
> This is good news. I have been completely snowed under with
> work/children for a long time and I really have regretted that this
> development was stalled (even though databases are not my strongest
> point).

I've more or less followed the schema you posted back then, although I'm
only storing matches. 

I have collection of 3000+ matches played on various online servers, and
I've plans to import those; that should hopefully reveal all the stupid
bugs in my python code.

> From talking to our more database knowledgeable people, there is a lot
> to be said for postgresql over mysql, particularly in enforcing
> relationships by using foreign keys. So starting with postgres is
> probably a very good thing.

The choice was more or less random; I just happened to have postgreql
installed, and I quickly found a postgreql-python RPM :-) From work I've
some experience with ad hoc programs using python + odbc (connecting to
IBM DB2 for OS/390). Anyway, hopefully we only have to change the two
lines importing the db module and connecting to the dbms; the rest of
the code should be independent of the dbms chosen. The DDLs in gnubg.sql
may have to be adapted for various dbms' (although it should be
"standard" sql).


Attachment: pgpDtzIDtI97V.pgp
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]