"Christian Anthon" <address@hidden>
wrote on 25/02/2008 16:39:58:
> 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.
I do agree: auto-pop-up of the stats window after
an analysis (except batch analysis) and auto-add matches to the dB (eventually with a
general option to switch that ON/OFF).
> > 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.
I was under the impression that the two interfaces
have been left in the code intentionally, but it seems to me that the only flag
that controls this is the USE_PYTHON. Hence, to disable the python dB interface I have to
disable python support. Not good.
Let me know how to use the "native" interface
without disabling python.