Talk:Query Language Properties

Prompt I think expressiveness is not adequate for real life scenarios. a finite set of results (on a finite data set) is mathematically oriented and not useable for real life use cases. I would love to make the requirement much more stringend and ask for results that fit real world constraints i would love to have fit / constrain or reasonable keyword that denotes that limits are to be expected e.g. for cardinality, data size expected query result volume and so on to make sure it can be determined for a given query wether it fullfills the requirements before the query is executed. This can be done formally by reasoning but also by examining statistics of previous query calls if named parameterized queries are being used with proper information hiding so that the query engine behaves like a proper black box Input Processing Output API and e.g. there is a guaranteed execution time (not mathematically proven but in term of likelihood). How would my thought be formally stated in addition and response to the above?