There is no good general solution to this is you are going to change
encodings from something open-ended to something of fixed radix (e.g.
a pair of integers => fixed length string field).
We might be able to provide some support for specific kinds of items
defined by a simple specification
I'd like to add a mechanism for sorting on small tuples, but it would
be different for each backend. I think I know how to do it for BDB,
but it will take some work. CLSQL could do it pretty easily (however
see my response to Leslie's recent mail).
Alex, what would the issues be for the pos
I don't believe the Postmodern backend, at least, allows search by conses.
If you want sensible (ordered) results with a and b if a and/or b are
integers, by the way, you should zero-pad them; otherwise, say, '1 2'
comes after '1 12', which is probably not what you want
Rob
2009/1/14 Yarek Kowali
When serializing tuples, is the string representation best: You suggest
using (format t "~A ~A" a b) - is that efficient enough? what about doing
(cons a b) = is there a way to index and search for conses? Any other ideas?
Yarek
On Tue, Jan 6, 2009 at 5:17 AM, Alex Mizrahi wrote:
> YK> Is thi
Thanks for your comments. Let me try to provide you with a little more
information.
On Thu, Jan 8, 2009 at 4:38 AM, Ian Eslick wrote:
>
> On Jan 8, 2009, at 3:22 AM, Elliott Slaughter wrote:
>
> > Another issue is that the cache-style declaration in persistent
> > classes doesn't get inherited by
> Is anyone still using the CL-SQL store? Robert and I have discussed
> deprecating it in this or a future release, although SQLite support is
> the only way to use Elephant with a cheap, free, easy to install/
> distribute backend.
I would prefer to ditch CLSQL and SQLite altogether and put
tha
