Re: subviews and python interface
Thomas Mills Hinkle <[email protected]> Mon, 9 May 2005 18:05:59 -0400
| Newsgroups | gmane.comp.db.metakit |
|---|---|
| Message-ID | <[email protected]> |
On 5/7/05, Brian Kelley <[email protected]> wrote: <snip> > A view cannot contain a storage objects, a storage object contains > views. A view can contain other views though. For example > > vw = st.getas("user[name:S,history[commands:S]]") > > so now each user has a name and a "list" of strings that were the past > commands. The subview can have many different columns of course. So I never noticed you could do this before. Does this provide substantial gains over having two views that get linked by an ID? e.g. in my curren app I store recipes, each of which has a number of ingredients. The ingredients are in a separate view and then looked up by the recipe ID. Is this substantially slower than using a nested view would be? It seems like it wouldn't be worth it since it's not intuitive how I would search all ingredients with this method, but I'm curious to learn what advantages the nested views might have under the hood. Tom _____________________________________________ Metakit mailing list - [email protected] http://www.equi4.com/mailman/listinfo/metakit