Re: [Bug-gnubg] Player records are wrong

[Jim Segrave]

On Sun 09 Mar 2003 (09:46 +0000), Joern Thyssen wrote:
> On Sat, Mar 08, 2003 at 04:11:03PM -0600, Chris Wilson wrote
> > Hello Joern,
> > 
> > Saturday, March 8, 2003, 3:32:30 PM, you wrote:
> > 
> > JT> I have a crazy idea about using an relational database for storing
> > JT> player records. Most databases have a C API, so it should be
> > JT> straightforward. 
> > 
> > JT> Each game would be stored in such a database, so it's possible to make
> > JT> statistics for certain match scores or whatever.
> > 
> > JT> Jørn
> > 
> > That's an excellent idea.  There is a lot of valuable information
> > being discarded at the moment.  The question becomes which database
> > format to use.  I can think of two formats on the Windows side of
> > things but I don't know much about databases for use on the *NIX
> > platforms.  If this idea is implemented, I'd be more than happy to
> > write an application on the Windows side to manipulate and report on
> > that data.
> 
> My plan is to use a standard relational database, for example, access,
> mssql on windows and mysql, postgresql etc on unix. On windows I think we
> could use ODBC as interface, so it really doesn't matter what database
> we're using -- most if not all databases on windows support ODBC
> (access, mssql, mysql, DB2, oracle etc). I don't think there is a
> similar interface on unix, but I think it easy to use any database since
> most of them have a C API.
> 
> For example,
> 
> static int
> DBConnect( ... ) {
> #ifdef ODBC
>    do whatever we need to do to establish a connection with ODBC
> #endif
> #ifdef MYSQL
>    do whatever we need to do to establish a connection with mysql
> #endif
> etc etc
> 
> }
> 
> The largest part of the work is creating the logical database model for
> the player records. 

Both mysql and postgresql have ODBC interfaces available. Databases
are not something I work with directly, but some of my staff do. There
were some problems encountered connecting a Microsoft application with
ODBC to a postgresql database, but that's probably not an issue here.

-- 
Jim Segrave           address@hidden