On 10/6/06, JP <[EMAIL PROTECTED]> wrote:
>
> I'd bet this is related to some issues I've seen in trying to get the
> multi-db branch tests passing post r3661. The trouble is (or seems to
> me to be) that anything that uses the test client causes the
> request_finished signal to fire, which causes
Mikeal Rogers wrote:
> > Excuse me for being very dense here, but I'm missing what's going on
> > here. You found a problem with in-memory SQLite and then did or didn't
> > solve it? Or you just worked around it?
>
> Sorry for the confusion.
>
> I worked around it. It's still an outstanding issue,
> Excuse me for being very dense here, but I'm missing what's going on
> here. You found a problem with in-memory SQLite and then did or didn't
> solve it? Or you just worked around it?
Sorry for the confusion.
I worked around it. It's still an outstanding issue, I'm not that
familiar with the
Hey Mikael,
On Thu, 2006-10-05 at 20:16 -0700, Mikeal Rogers wrote:
> I'm working on adding some selenium support in to the test framework.
>
>
> The first thing i obviously had to do was get the test server up and
> running at the beginning of the tests. I completed this but ran in to
> one la
I'm working on adding some selenium support in to the test framework.The first thing i obviously had to do was get the test server up and running at the beginning of the tests. I completed this but ran in to one large issue.The test framework defaults to using an in memory database if it sees that
