bug-gnubg
[Top][All Lists]
Advanced

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

Re: [Bug-gnubg] Relational dBs issues


From: Christian Anthon
Subject: Re: [Bug-gnubg] Relational dBs issues
Date: Mon, 25 Feb 2008 16:39:58 +0100

On Mon, Feb 25, 2008 at 10:26 AM, Massimiliano Maini
<address@hidden> wrote:
>
> What about an pop-up that appears any time the analysis of a match/session
> is done,
> asking to add the match to the dB ?
> Nice to have: a global option like "always add analyzed matched to dB".
>

It has been suggested to pop the stats window after finishing an
analysis. Perhaps adding an add-to-db button to the stats dialog would
be a good idea.

The more I think about the more I like the idea of adding a match
automatically to the db after it is analysed. It is also a good idea
when we do batch analysis.


> dbprovider.c:59: warning: 'SQLiteConnect' declared `static' but never
> defined
> dbprovider.c:60: warning: 'SQLiteDisconnect' declared `static' but never
> defined
> dbprovider.c:61: warning: 'SQLiteSelect' declared `static' but never defined
> dbprovider.c:62: warning: 'SQLiteUpdateCommand' declared `static' but never
> defined
> dbprovider.c:63: warning: 'SQLiteCommit' declared `static' but never defined
>
>
>

Partly my fault. But it also means that you don't use the direct
sqlite interface. To avoid confusion it might be a good idea to _not_
use the python interface to the db in our main windows distribution.
It will require a small code-change though.

Christian.



 _______________________________________________
>  Bug-gnubg mailing list
>  address@hidden
>  http://lists.gnu.org/mailman/listinfo/bug-gnubg
>
>




reply via email to

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