| Auteur | Message |
|---|---|
|
le: 04. 06. 2004 [16:04]
|
|
|
ncesar@lunix.com.ar
Nicolas D. Cesar
Auteur du fil
Inscrit depuis: 31.12.1969
Interventions: 0
|
=46rom documentation (yes, I've beeing reading!): =2D---------------------------- * limits Several limits apply to query and especially search evaluation. (..) =2D the number of open queries is limited by session option q (defaul= t=20 20). =2D----------------------------- from php, how can I change this option q? or should I do it when I start up= =20 the server... Also, I run a query with more than 20 results, is there any way to go to an=20 arbitrary offset? (I notice when I re-run that query I get next elements). and something strange... I got 38 results.... first shows 18 and after shows 20, is this the defau= lt=20 behaviour? Thanks in advance, =2D-=20 Nicol=E1s D. C=E9sar <ncesar@lunix.com.ar> Lunix [ Soluciones en GNU/Linux ] http://www.lunix.com.ar BOFH excuse #170: popper unable to process jumbo kernel ------------------------------------------ Posted to Phorum via PhorumMail |
|
le: 06. 06. 2004 [08:32]
|
|
|
paul@malete.org
Klaus Ripke
Inscrit depuis: 31.12.1969
Interventions: 0
|
Hola On Friday 04 June 2004 23:04, Nicolas D. Cesar wrote: > - the number of open queries is limited by session option q (defa= ult > 20). > ------------------------------ > > from php, how can I change this option q? or should I do it when I star= t up > the server... Setting the options is not yet implemented. However, why would you want to do that? It's the number of open queries, not the number of results per query. After reaching that limit, old queries will be recycled. Remembered queries serve two purposes: 1) To reuse their results by reference to e.g. #3 in a new refined query. A user usually only does that for the last handfull of queries. It is slightly more efficient than to copy the old queries original query text into the new query since, under certain circumstances, the prefetched list of mfns can be reused internally. This advantage would go away if the servers memory where hogged with too many remembered results. 2) To fetch the results of multiple queries in "parallel", which is also rarely done for more than two or three. For real parallel queries you need to use multiple sessions against the multi-process server anyway (the limit is per session). > I run a query with more than 20 results, is there any way to go to an > arbitrary offset? (I notice when I re-run that query I get next element= s). no we are considering making the cursor settable just like the other numeric options one day, however, the reason for not making this a fully public option is, that with filtering this is a very expensive operation to do it correctly. In other words, there is not much advantage of doing this in the server, so implementing such operations is left to the client. In most applications the client will buffer the information anyway in order to display some nice scroll lists to the user. > I got 38 results.... first shows 18 and after shows 20, is this the > default behaviour? absolutely not! Is this behaviour repeatable? What does the debugg output from the connection say? saludos ------------------------------------------ Posted to Phorum via PhorumMail |