I guess the problem was that I was using the CVS version.
I installed the darcs version and all tests were good. One comment I
would make is that the documentation does not really say or recommend
to use the darcs version. Additionally, the documentation does not say
that fiveam and arnesi
Should you be using the darcs system? The CVS tree is about 6 months
out of date. I think you should either use one of the release tarballs
or use darcs to get the latest version.
On Thu, 2008-02-21 at 11:15 -0500, Ian Eslick wrote:
> >
> > I erased the entire elephant directory and re-downloade
No, I can't test this, because I don't have BDB installed on my x86_64.
On Thu, 2008-02-21 at 11:15 -0500, Ian Eslick wrote:
> Robert,
>
> Can you see if you can reproduce this. I can't get back to it now for
> a couple of days.
>
> Waldo, if you don't hear anything from us in a few days jus
??>> elephant reads/writes slots individually, so this means we cannot
??>> have more
??>> than 1000-1 slots operations per second. that sounds quite
??>> prohibitive.
JD> So with an SQL engine this translates to one SELECT/INSERT/UPDATE per
JD> slot value read or write?
something like
Robert,
Can you see if you can reproduce this. I can't get back to it now for
a couple of days.
Waldo, if you don't hear anything from us in a few days just ping us
again.
Thanks,
Ian
On Feb 21, 2008, at 11:11 AM, [EMAIL PROTECTED] wrote:
Hi Ian,
I erased the entire elephant director
Hi Ian,
I erased the entire elephant directory and re-downloaded the CSV
repository again just now. The contents of the tests/testdb were just
the README file and the CVS directory. I ran the tests and got the
exact same result.
I then erased the tests/testdb and then re-created a new bla
On Feb 21, 2008, at 8:41 AM, Leslie P. Polzer wrote:
I'm not sure I understood your message correctly. But see below.
Ok, this is an architectural issue that wasn't completely thought
out. Currently class indexing effectively limits instances of a
class
to a specific store. The first tim
On Thu, Feb 21, 2008 at 3:35 PM, John DeSoi <[EMAIL PROTECTED]> wrote:
>
> On Feb 21, 2008, at 6:12 AM, Alex Mizrahi wrote:
>
> > elephant reads/writes slots individually, so this means we cannot
> > have more
> > than 1000-1 slots operations per second. that sounds quite
> > prohibitive.
On Feb 21, 2008, at 6:12 AM, Alex Mizrahi wrote:
elephant reads/writes slots individually, so this means we cannot
have more
than 1000-1 slots operations per second. that sounds quite
prohibitive.
So with an SQL engine this translates to one SELECT/INSERT/UPDATE per
slot value read o
I'm not sure I understood your message correctly. But see below.
> Ok, this is an architectural issue that wasn't completely thought
> out. Currently class indexing effectively limits instances of a class
> to a specific store. The first time an instance is saved, the current
> *store-controlle
IE> Is this caching something that we could import into BDB?
it is pretty easy to add caching inside one transaction or accross
transactions assuming there is only one instance (and one thread) working
with database. we can have this part implemented in the core and shared
among backends..
ca
the solution seems to be trivial: implement caching on a client
side. simple
solution is to cache data within single transaction. complex
solution is to
cache data accross transaction, tracking changes and invalidating
stale
cache entries automatically.
we've implemented both options. so no
On Thu, Feb 21, 2008 at 2:44 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I don't mean to start a war here or put any work down. However, I just
> needed some clarification/direction into which way the data stores
> work is going.
> Since Postgres does allow for features such
> So, putting licensing issues aside, what is the real difference/ advantage
> of one data store over the other? In a recent email I read by Alex, he
> mentions he's going to work on improving performance on the postmodern
> data store. So, even after that improves and performance is matched
14 matches
Mail list logo
