"Henrik Hjelte" <[EMAIL PROTECTED]> writes:
> We have recently discovered some performance (and possibly other)
> problems, you might even call them bugs, with both map-index and the
> current implementation of cursors in the postmodern backend. Alex
> Mizrahi will reimplement things in a new way
On Wed, 2007-11-28 at 18:37 -0500, Ian Eslick wrote:
> I'm surprised you are seeing this difference on Postmodern, unless
> your input name is matching a large number of objects (i.e. s is
> large). I had thought that the native PostgreSQL backend,
> postmodern,
> fixed the linear cost probl
I used CLSQL recording in the past when I have been debugging. I think
that is the best way to do it; I wouldn't want to put such a think in
Elephant, since it would be very backend-specific.
On Wed, 2007-11-28 at 18:37 -0500, Ian Eslick wrote:
> There is not SQL recording built into Elephant tha
We have recently discovered some performance (and possibly other) problems,
you
might even call them bugs, with both map-index and the current
implementation
of cursors in the postmodern backend. Alex Mizrahi will reimplement things
in a new way
with the eye for performance, this work will probably
Originally I wrote it get-instance-by-value as a convenience function
when I knew that there was only one object being returned by an
index. If there are multiple objects that match the input term, then
get-instance-by-value is effectively returning a random one.
There is going to be a hug
Dear Elephant developers,
I've been considering using Elephant for a project of mine,
and have been doing some basic performance tests, using the
new postmodern back end (which seems way cool, btw).
The scenario I'm testing is something like this; you
have a base class:
(defclass person-mixin (
