pp wrote: > > > > > I got simple question I think. > > > > I plan to have 5000-10000 article records. > > > > I wonder what is faster: > > > > store every article within one topic and filter > > > > with one field or store it within many subtopics? > > > > I guess every querry will force check every article > > > > in article table. > > > > > I gor two ways of making this. > > 1. Create two topics tree. > First of them keeps articles wchich will be very often deleted and inserted > but will get always the same name, as articles in second topic tree. > This way I have to make additional querry to get almost "twinnie" article > for the first one in first topic tree. > In some cases this way of doing make some work very flexible for me. > > 2. Create only one topic tree, and for example treat $article->view > as an option to displays it in many pages. > This looks most faster , but I do not know how it will behavioure > in one year when number of articles will grow up.
Actually, I don't clearly understand your question. What is the problem you want to solve? Anyway, there are a few methods you can narrow the articles you retrieve with midgard. One is the 'type' field, it can be used with the article listing functions. Another is that there is an $object->searchparameters() method, which can be used to query not only one object, but every object of one type (i.e. all articles). Althogh, it is marked as experimental in the documentation. Actually, I think the functionality of this function is essential in large sites, if I do not want to access the midgard db directly. > Or maybe is there any PHP functions to get querry time? > This way I could compare many ways. I am sure you can use mysql to log the query times. If I am wrong, then you can get what query did it execute, and you can re-execute it at the mysql prompt. Circum --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
