On Fri, Mar 7, 2008 at 10:08 PM, Leslie P. Polzer <[EMAIL PROTECTED]> wrote:
>
> Yes, this works as it should.
> The problem is that the concurrency tests shouldn't be included
> in the standard backend test suite which gets run by
> DO-BACKEND-TESTS.
I think it just is a matter of putting this
Dear Henrik,
> 2008/3/7 Leslie P. Polzer <[EMAIL PROTECTED]>:
>>
>> Amendments:
>>
>> * handle pg error 23505 (duplicate primary key race condition)
>> * some notes on handled errors
>> * removed dbpm-error condition
>
> Does these fix the problems you reported earlier?
I believe this fixes
On Wed, Mar 5, 2008 at 4:38 AM, Ian Eslick <[EMAIL PROTECTED]> wrote:
> Hello again everyone,
>
> As some may have guessed from recent e-mails, I got motivated to
> design/add a fairly large set of inter-related features that should
> address many of the problems and questions we've seen lately.
2008/3/7 Leslie P. Polzer <[EMAIL PROTECTED]>:
>
> Amendments:
>
> * handle pg error 23505 (duplicate primary key race condition)
> * some notes on handled errors
> * removed dbpm-error condition
Does these fix the problems you reported earlier?
Since Alex Mizrai is updating the postmodern cod
Amendments:
* handle pg error 23505 (duplicate primary key race condition)
* some notes on handled errors
* removed dbpm-error condition
I also noticed that the concurrency tests are run automatically
as part of the backend tests. This is not my intention, but I'm
not sure how to fix it right no
Ian Eslick writes:
> You shouldn't be using any of the controllers in contrib/eslick, those
> are in-progress experiments. Which version of the source tree are you
> using? This code shouldn't be loaded unless you are doing it
> explicitly. You should just be loading elephant.asd.
As a matter
