[mythtv] Scheduler needs table keys?

[Chris Pinkham]

* On Mon Jan 29, 2007 at 11:55:40AM -0600, David Engel wrote:
> On Sun, Jan 28, 2007 at 11:55:36PM -0500, Chris Pinkham wrote:
> > Well, I was looking into this a little and it's not as easy as I thought
> > to do it this way.  Because MSqlQuery inits QSqlQuery, we can't just pass
> > in a null MSqlQueryInfo and init the db connection when the thread gets
> > around to processing the query.  I wanted to keep from having to rewrite
> > queries the way the current async thread does, so I'm going to keep
> > looking at this trying to figure out a solution.
> 
> Could you pass the DB connection and query objects together for later
> execution?

I thought about that, but we could potentially eat up a lot of connections
if a bug occurred.  It might be possible to have a dedicated connection like
the scheduler does and just use that connection with multiple MSqlQuery
instances so that we can have multiple prepared statements queued up.
If the backgrounded processes are sequential then we wouldn't be writing
over ourselves with the single DB connection.  Something I'll have to test.

--
Chris