Re: [Seaside] Re: Best data structure for...

["S.J.Chun"]

Hi,

don't know whether magma or omnibase does have solution for this.
It seems that I/devloper does have to provide properly designed data
structure...

----- 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...

  Hi,
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?
Regards
Ernst
 
> chunsj at embian.com chunsj at embian.com
>  Mon Nov 26 01:22:30 UTC 2007
>
> Hi,
>
> my data class has following attributes;
>
> title
> content
> creation date
> modified date
> type
>
> 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
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside