I definitely don't want to release until we're comfortable the tests
are covered. We'll look for a reasonable consensus that it is ready.
FYI - The backend updates will require:
- Initialization of new base class slots with fixed-oid btrees
(schema-table :reader controller-schema-table
That is really great !
We'll follow with postmodern backend soon. I don't think we should haste
with releases though, it is better if we have the time to check for bugs and
update the test suite. I want to encourage anyone that sees some areas that
are not tested enough to just feed back this. No
Do you count fast in 10's of ms or 100's? :) -Ian
On Mar 23, 2008, at 5:27 PM, Alex Mizrahi wrote:
IE> unnecessary. If you have messages indexed by time than you can
simply
IE> walk the index and filter by user until you have a web page
worth of
IE> messages.
worst case behaviour is very
IE> unnecessary. If you have messages indexed by time than you can simply
IE> walk the index and filter by user until you have a web page worth of
IE> messages.
worst case behaviour is very bad -- to prove that there are no messages, it
will have to scan all of them..
what's even worse, this
Congratulations Ian!
Thanks for all the hard work.
I will help by working on this task:
On Sun, 2008-03-23 at 10:52 -0400, Ian Eslick wrote:
> - Upgrade Postmodern and CLSQL data stores - Support btrees with
> duplicate keys - Some minor API additions for upgrade &
> bootstrapping
That i
Another thought on this topic is that with a sufficiently efficient
query system, some of the indices you describe should become
unnecessary. If you have messages indexed by time than you can simply
walk the index and filter by user until you have a web page worth of
messages. A scan, eve
Hi Alex,
I've changed the interface but maintained essentially the existing
functionality, except that subclasses can share a derived index with a
common base class. Allowing heirarchy means that at the low-level
indexes are no longer tied to a specific class in the way they were
before,
IE> :index t is not necessary - in fact it is ignored. :slot-deps
are
also not required, but the derived index is updated on any slot write
if that slot is not transient, set-valued or an association. We can
add those last three slot types into the mix if necessary, but
My fellow Elephants,
Unstable isn't unstable anymore! All BDB tests, including migration,
for BDB/Mac/Allegro and BDB/Mac/SBCL are green as of today's checkin.
All major new features are implemented, including:
- Instance map, class schema evolution and MOP compliance
- New slot types
- Ca
