On Thu, Apr 28, 2011 at 7:31 PM, Alex Mizrahi wrote:
> > Why? I am by no means an expert and never looked thoroughly the code,
> > but ,abstractly speaking, doesnt it boil down to just creating
> > more indexes automatically at class definition time?
>
> Code assumes that there is only one index
On Thu, Apr 28, 2011 at 8:34 PM, Ian Eslick wrote:
> I agree the semantics of inherited indexing is off. I implemented what
> worked for me at the time and was an easy extension to what was already
> there. However, the issues around class redefinition, database connection
> state, schema synch
Clearly a bug if the instances aren't getting indexed when you add an index!
Should be a simple one to fix.
The older you get, sadly, the easier it is to do long-term forecasting. :)
Ian
On Apr 28, 2011, at 1:51 PM, Vassilis Radis wrote:
> As Ian correctly assumed, I just added the :index t
As Ian correctly assumed, I just added the :index t . I didnt change the
slot name.
So, candidates are:
rebuild-slot-index
recreate-index-using-class
I am going to look at them. Thanks.
P.S. As Alex asked, is this a bug or is the normal functionality?
___
Oh come on...
What happened?
Anyway, for you to be able to foresee for a whole year it means it is
serious. I wish best luck.
On Thu, Apr 28, 2011 at 6:39 PM, Ian Eslick wrote:
> Hi everyone,
>
> I'm not going to be in a position to do regular development or support for
> Elephant for at least t
I agree the semantics of inherited indexing is off. I implemented what worked
for me at the time and was an easy extension to what was already there.
However, the issues around class redefinition, database connection state,
schema synchronization, data loss protection, etc make code changes ar
> Why? I am by no means an expert and never looked thoroughly the code,
> but ,abstractly speaking, doesnt it boil down to just creating
> more indexes automatically at class definition time?
Code assumes that there is only one index it needs to update at time, so it
needs to be revised to handl
Hi everyone,
I'm not going to be in a position to do regular development or support for
Elephant for at least the next year. I may be able to make small, critical bug
fixes or apply patches if no one else steps up.
Leslie and Alex are both capable of making changes and improvements and I'm
> After creating a lot of objects of a specific class I decided to change a
> slot to be indexed.
> It did change, no old items were included in the index.
Isn't this a bug?
> How can I populate the index with old values?
(defmethod rebuild-slot-index ((sc store-controller) class-name index-nam
I assume you added :index and didn't change the slot name? I think the
function you want is recreate-index-using-class
On Apr 28, 2011, at 5:48 AM, Vassilis Radis wrote:
> After creating a lot of objects of a specific class I decided to change a
> slot to be indexed. It did change, no old it
After creating a lot of objects of a specific class I decided to change a
slot to be indexed. It did change, no old items were included in the index.
How can I populate the index with old values?
___
elephant-devel site list
elephant-devel@common-lisp.net
I think ideally this would be resolved with a new type of 'hierarchical'
> slot indices where instances will be indexed in many indices at once --
> when
> you make super-frob instance it will be indexed by frob-style both in
> super-frob and frob index (and, generally, in all super-classes). In th
On Wed, Apr 27, 2011 at 10:34 PM, Alex Mizrahi wrote:
> > Currently, I do something along the lines of the following on the results
> > on get-instance[s]-by-XXX functions:
> > (remove-if #'(lambda (x) (not (member ',class-name (mapcar #'class-name
> > (sb-mop:class-precedence-list x) lst :key
13 matches
Mail list logo
