Ah, this was a false alarm. Vladimir, the latest HEAD should fix the
problems you reported.
As mentioned in my last note this was actually a bug I introduced in
fixing some memory problems that crop up when using add-index on a large
primary index with the populate option (it used to exhaust BDB'
If you are working from the latest HEAD and using BDB you'll need to
take the following steps to upgrade your BDB databases to work with
check-ins as of September 3rd)
[This info can be found in UPGRADE-BDB in the elephant root directory]
1) Install BDB 4.4.20 or later just as you installed BDB 4
Recent CVS updates encompass:
- I added Vladimir's BDB 4.3->4.4 patch to the repository
- Fixed the bugs Vladimir reported; current state is bug free on
Allegro/Mac OS/BDB
- Re-organized sleepycat.lisp a bit to accommodate the BDB 4.4
convention changes
- Added a new method to the backend API 'opti
Vladimir,
I applied your changes, cleaned up some other changes for a check in. I
found the same errors as you on Mac OS using Allegro. Digging deeper
into this it appears there are genuine issues cropping up in these two
tests.
It appears that a pcursor-next operation returns nil instead of t
Hello,
I was working against HEAD circa late last week. I guess I should have
realized there might be some broken code in the repository. :) The
same tests passed before and after, so at least it doesn't look like I
broke anything new.
Since only the flag constants changed as far as the interfac
Way to go! Did you test against the current HEAD or the 0.6.0 release
branch? All tests passed on 0.6.0 so if you are working from that
release you should be worried, but it's possible that not all tests pass
the current HEAD. Also, did they pass before and after your fix?
In any event, I presu
