[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: RE: RE: RE: [Bug-gnubg] Database tools for the player record
From: |
Massimiliano . Maini |
Subject: |
RE: RE: RE: RE: [Bug-gnubg] Database tools for the player record |
Date: |
Wed, 16 Aug 2006 09:57:17 +0200 |
>I followed your instructions, modified the database.py file as per your
>instructions, and it gives the same error as I showed below:
>
>"Database table check failed!"
>"The table gnubg.match is missing."
>
>I then renamed the database file to database.old, which was 1.47kb and not
>0kb, just to test, and this time it gave a different error:
>
>Database preference file not found
>Traceback <most recent call last>
>File "C:\program files\gnubg/scripts\database.py", Line 630, in connect
>import pgdb
>ImportError: no module named pgdb
>
>BTW, the inverted '/' above is not a typo. That is exactly what it reads.
>
>
Albert
Hmmm, if it's trying to import the pgdb module it means that your
database is set-up as postgresql instead of sqlite. Is this intentional ?
Can you please send me the file named "database" from your gnubg directory
?
it specifies the database format (sqlite, postresql or mysql) and if
game table is created or not (BTW, I find the name of this file just silly
and confusing).
Hereafter there's the "database" file I normally use on Windows (of course
it
may not work with your existing db, but should be ok if you create a new db
from scratch). Notice that :
- it's sqlite
- it include games table
- the db file (the real database, not the config file) is named gnubg.db
Let me know,
MaX.
#############################################################################
# all specifications for the match/game database begin with the text gnubg*
# type = postgres or sqlite, maybe mysql somedoay
gnubg*type sqlite
# parameters used during connect for storing/retreiving matches/games
# for sqlite, this is only dbname
# for postgresql:
# dsn Data source name host:database:user:password:options:tty
# trailing fields and their ':' can be omitted
# localhost:gnubg:mylogin:mypass defaults options and tty
# :gnubg defaults host, user, password, options and tty
# user User name as string (optional)
# password Password as string (optional)
# host Hostname (optional)
# database Database name (optional)
# host, user, password and database will override those
# parts of the dsn. If you need a non-default port no
# you have to supply the host line
# parameters can contain embedded white space if they are surrounded
# by single or double quotes (so single or double quotes can also be
# included, but not both in the same parameter:
# gnubg password 'this is my password'
# gnubg password "it's a secret"
#gnubg*user jes
#gnubg*host localhost:5432
gnubg*database gnubg.db
#gnubg*password "abcdef ghig"
# this line, tells gnubg to include details of individual
# games
gnubg*games yes
# parameters used during connect for storing/retreiving errors
# see above notes (still in development)
#error*user jes
#error*host localhost:5432
#error*database blunders
- RE: RE: RE: RE: [Bug-gnubg] Database tools for the player record,
Massimiliano . Maini <=