On Fri, Nov 21, 2008 at 02:14:22PM -0500, Ian Eslick wrote:
> I think my prior e-mail on this topic failed to make it to the list...
>
> I checked in some patches this week to elephant-unstable:
> - Fixed (get-universal-time) issue reported earlier caused by error in
> bignum comparisons under B
On Tue, Oct 28, 2008 at 12:40:36PM +0100, Leslie P. Polzer wrote:
>
> > Background: Our application that makes heavy use of elephant/bdb and the
> > association feature in the unstable branch is too slow by at least one order
> > of magnitude. We obviously need to profile it first before we start
Hi,
I'd like to know if people on the list have experience with the performance
characteristics of the available backends for elephant. I am not asking for
detailed measurements and performance differences of few percent but typical
usage patterns where you can predict that one backend will likely
Hi,
the attached patch solves the problem with the "forgotten" associations. The
main reason for the problem was that the slot index was incorrectly named in
the controller-index-table of the store controller.
Is this patch format ok? We are admittedly all but darcs experts.
Regards
Lukas, Marc
Hi,
we came across a (to us) surprising behavior of the association code in
elephant-unstable: If we generate associations between instances of the same
class, then elephant forces these associations to be symmetric. That means we
cannot use association slots to implement directed graphs.
For exa
