On May 10, 2008, at 2:46 PM, Clinton Ebadi wrote:
Ian Eslick <[EMAIL PROTECTED]> writes:
Also which version of the elephant tree? This may be fixed on
unstable - there was quite a bit of general cleanup as I made the
schema changes. Today, psets are just a wrapper around btrees -
anyone tri
It's interesting to know that this problem appears to show up on both
branches. That narrows down the possibilities a bit.
Ian
On May 10, 2008, at 4:35 PM, Ryszard Szopa wrote:
On Sat, May 10, 2008 at 8:46 PM, Clinton Ebadi <[EMAIL PROTECTED]
> wrote:
Ian Eslick <[EMAIL PROTECTED]> writes:
How long ago were you using unstable? Some of the class indexing
problems should have been fixed by the time I did my last major
update. If it was more recent, than at least for that problem I know
where to look...
Ian
On May 10, 2008, at 2:46 PM, Clinton Ebadi wrote:
Ian Eslick <[EMAI
> My other strong suggestion, besides starting by capturing the major
> use cases, is that we begin by implementing a procedural approach by
> implementing the building blocks for filter, sort, intersect, etc. If
> we take the list of four filtering approaches above, we can start
> writing code t
On Sat, May 10, 2008 at 8:46 PM, Clinton Ebadi <[EMAIL PROTECTED]> wrote:
> Ian Eslick <[EMAIL PROTECTED]> writes:
>> Also which version of the elephant tree? This may be fixed on
>> unstable - there was quite a bit of general cleanup as I made the
>> schema changes. Today, psets are just a wrapp
Ian Eslick <[EMAIL PROTECTED]> writes:
> Also which version of the elephant tree? This may be fixed on
> unstable - there was quite a bit of general cleanup as I made the
> schema changes. Today, psets are just a wrapper around btrees -
> anyone tried to reproduce this using straight btrees in
Also which version of the elephant tree? This may be fixed on
unstable - there was quite a bit of general cleanup as I made the
schema changes. Today, psets are just a wrapper around btrees -
anyone tried to reproduce this using straight btrees instead of psets?
Ian
On May 10, 2008, at
That's fascinating (and disturbing).
What data-stores are you using?
Ian
On May 10, 2008, at 1:49 PM, Clinton Ebadi wrote:
Ian Eslick <[EMAIL PROTECTED]> writes:
This happens in your application, or only in the tests? Can you give
me the exact sequence and state you use to reproduce? Do y
Ian Eslick <[EMAIL PROTECTED]> writes:
> This happens in your application, or only in the tests? Can you give
> me the exact sequence and state you use to reproduce? Do you have a
> fresh lisp & fresh DB? Does it still show up if you close the store,
> open a fresh one, and try again? There is
Ok, I'll look into this when I can. May be a few days or so. Pester
me if you don't hear back from me next week sometime.
Thanks,
Ian
On May 10, 2008, at 1:13 PM, Ryszard Szopa wrote:
On Sat, May 10, 2008 at 4:25 PM, Ian Eslick <[EMAIL PROTECTED]>
wrote:
This happens in your application,
On Sat, May 10, 2008 at 4:25 PM, Ian Eslick <[EMAIL PROTECTED]> wrote:
> This happens in your application, or only in the tests?
Until now I have spotted it only in my unit tests.
> Can you give me the
> exact sequence and state you use to reproduce? Do you have a fresh lisp &
> fresh DB? Does i
This happens in your application, or only in the tests? Can you give
me the exact sequence and state you use to reproduce? Do you have a
fresh lisp & fresh DB? Does it still show up if you close the store,
open a fresh one, and try again? There is likely to be some state
somewhere and i
On May 10, 2008, at 12:26 AM, [EMAIL PROTECTED] wrote:
Hi Ian,
Thanks for your comments. They do make some points a bit clearer and
bring others to the table. I'd like to see others comment as well
before we continue moving forward.
In summary, I agree to follow your suggestion. However,
Hello,
I have run into a very strange bug related to psets. I create some
persistent objects with psets as slot-values, and at some point one of
those psets that should be empty contains 5 integers, usually in
descending order with a step equal 5. For example
(values pset (pset-list pset)) => # (
14 matches
Mail list logo
