[elephant-ticket] Re: #38: Map over types

[elephant]

#38: Map over types
--------------------------+-------------------------------------------------
  Reporter:  ieslick      |       Owner:  ieslick      
      Type:  enhancement  |      Status:  new          
  Priority:  minor        |   Milestone:  Release 0.9.1
 Component:  db-bdb       |     Version:               
Resolution:               |    Keywords:               
--------------------------+-------------------------------------------------
Changes (by ieslick):

  * milestone:  Release 0.9.2 => Release 0.9.1

Old description:

> Right now there is no good way to map over types is a btree or index.
> There are two notions of types to think about: primitive serializer types
> (select by type tag) or lisp types (which requires deserializing all
> values).  The trick to lisp types is either to do a full scan with lisp
> subtypes, or to do a set/pset to the primitive supertype, then filter out
> the subtypes according to the type specifier.
>
> This might be put off until someone requests it as typically indexes are
> looking at ranges of
>
> Ideal implementation?  Only deserialize values if primitive types match.
> This is a subset of the lazy deserialization feature discussed in ticket
> #39.

New description:

 Right now there is no good way to map over types in a btree or index.
 There are two notions of types to think about: primitive serializer types
 (select by type tag) or lisp types (which requires deserializing all
 values).  The trick to lisp types is either to do a full scan with lisp
 subtypes, or to do a set/pset to the primitive supertype, then filter out
 the subtypes according to the type specifier.

 This might be put off until someone requests it as typically indexes are
 looking at ranges of

 Ideal implementation?  Only deserialize values if primitive types match.
 This is a subset of the lazy deserialization feature discussed in ticket
 #39.

Comment:

 We need to evaluate whether this is important for dealing with indexing in
 class hierarchies so I'm putting it into 0.9.1

-- 
Ticket URL: <http://trac.common-lisp.net/elephant/ticket/38>
elephant <http://common-lisp.net/project/elephant>
elephant