Scribit Daniel Salama dies 13/11/2006 hora 21:00:
> So, if I make my class persistent, it's persistent... period! I don't
> need to add it to a collection or to the root.
Well, I did not know that before that discussion. I think it's not
clearly indicated in the docs...
And then I wonder: if I us
Persistent classes in the current model aren't easy to fully delete -
you can only make the unreachable by having no reference to them
reachable from the controller or class roots. You can drop an object
from the index and there is a way to delete the object from the main
system BTree - but until
Ian et al,
Based on my comment to Robert and that of Pierre, could you, or
anyone, please clarify this for me (and maybe others):
If making a class persistent means that there is no need to add it to
root or to any persistent collection, when I look at Robert's sample
code, I see (excerpt
On Tue, 2006-11-14 at 14:50 -0500, Daniel Salama wrote:
Ian et al,
Based on my comment to Robert and that of Pierre, could you, or
anyone, please clarify this for me (and maybe others):
If making a class persistent means that there is no need to add it to
root or to any persistent colle
Robert,Thanks for the clarification. I think I got it and agree.BTW, after running your code using persistent objects and adding 5000 users, the total on-disk storage is now 5MB (as compared to 9MB by using non-persistent objects), which concurs with what Ian mentioned yesterday. Anyway, just wante
