Re: Re: [Bug-gnubg] python/db issues + minor comment

[Massimiliano . Maini]

>On Wed, Mar 29, 2006 at 09:15:23AM +0200,
address@hidden wrote:
>> I tried my python-enabled distribs with respect to sql db interface and
>> almost everything works fine. I installed SQLite and its python module
>> (as explained by Jon). Just a few details :
>>
>>
>> 1) I had to edit the file "database" in order to set "gnubg*type sqlite"
>> (and comment out postgres-only stuff). Also, set "gnubg*database
gnubg.db"
>> (.db extension is recognized by SQLiteAnalyzer and make it clear what
the
>> file contains).
>>
>
>Could you post the output of
>
>cvs.exe diff python/database.py

Not really, since I have no access to the cvs repository. Well, I could do
a diff
between two local files (original and modified), but the changes in
database
(NOT database.py) are trivial :

The line :
      gnubg*type postgres
becomes :
      gnubg*type sqlite


The line :
      gnubg*database gnubg
becomes :
      gnubg*database gnubg.db

I also have comented out (#) the last 3 lines of the file (all starting
with
"errors*").

>> 2) I added a couple of analyzed .sgf file to the database using
>> command-line gnubg and everything went ok : I can run queries
>> like "select * from nick;" and I see the expected result (I
>> also tried to run queries via an external tool, SQLiteAnalyzer,
>> and it works fine). I can also run queries via gnubg gui, but the
>> thing I cannot do is to add a match to the db via gnubg gui :
>> it does nothing (no confirmation message in the "status bar" in the
>> bottom of the window) ... something must be failing ...
>>
>>
>> 3) If I set "gnubg*games yes", then :
>
>The game database works on postgres/linux. You should probably remove the
>entire db before creating the match+game db.

I'm pretty sure I did it, but I'll try again.

>Could you please update to
>latest cvs before doing so, as there is a bug in the .sql files.

Tonight :))

>If you can make the windows version work with games, I think it makes
>sense to remove the non-games version and update database.py
>accordingly.

Don't know but if ok for everybody, it's just a matter of copying
gnubg.game.sql as gnubg.sql and removing gnubg.game.sql from the
repository.

BTW, why there's a gnubg.game.mysql in the repository ?!


MaX.