relpipe-data/principles.xml
branchv_0
changeset 210 f0a2916368e2
parent 204 58c40f213028
child 231 ea49ee7a73c9
equal deleted inserted replaced
209:74fecc2ba590 210:f0a2916368e2
   133 		</p>
   133 		</p>
   134 		
   134 		
   135 		<p>
   135 		<p>
   136 			However, there are cases where such streaming is not feasible e.g. if we need to compute some statistics or a column widths while printing a table in the terminal.
   136 			However, there are cases where such streaming is not feasible e.g. if we need to compute some statistics or a column widths while printing a table in the terminal.
   137 			In such situation, we must read the whole relation and only then generate the output.
   137 			In such situation, we must read the whole relation and only then generate the output.
   138 			But we should still be able to do streaming on the relations level e.i. if there are more relation, we always hold only one of them in the memory.
   138 			But we should still be able to do streaming on the relations level i.e. if there are more relation, we always hold only one of them in the memory.
   139 		</p>
   139 		</p>
   140 		
   140 		
   141 		<p>
   141 		<p>
   142 			This rule is important not only from the performance point of view but also for user experience.
   142 			This rule is important not only from the performance point of view but also for user experience.
   143 			The user should see the output as soon as possible i.e. the longer running processes will produce result continuously instead of flushing everything at the end.
   143 			The user should see the output as soon as possible i.e. the longer running processes will produce result continuously instead of flushing everything at the end.