Re: [Seaside] Re: Best data structure for...
chunsj at embian.com
Mon Nov 26 10:41:06 UTC 2007
don't know whether magma or omnibase does have solution for this.
It seems that I/devloper does have to provide properly designed data
----- Original Message -----
From: Ernst <ernst at hisplace.net>
To: seaside at lists.squeakfoundation.org
Sent: 07-11-26 18:00:11
Subject: Re: [Seaside] Re: Best data structure for...
One option would be to use a dictionary per key. Then use the observer design
pattern for keeping them consistent.
But maybe your OODB offers already a solution?
> chunsj at embian.com chunsj at embian.com
> Mon Nov 26 01:22:30 UTC 2007
> my data class has following attributes;
> creation date
> modified date
> and except content, the collection of
> elements of this data shlould be indexed; that is,
> title, creation/modified date and type be key.
> If single key is required, then dictionary will be my choice(or
> should I use tree?). What is the best data structure for multiple
> keyed data? This question has been one of my hurddle to the
> OODB; if like now, sql db will be used, I know how to handle this.
> Thanks in advance.
seaside mailing list
seaside at lists.squeakfoundation.org
More information about the seaside