![]() | |
#21
| |||
| |||
|
|
On Apr 10, 6:58 pm, paul c <toledobythe... (AT) oohay (DOT) ac> wrote: An average of averages is generally not equal to an overall average. No, and this gives rise to one of the most annoying statistical paradoxes out there as well: the Simpson-Yule one. Still, we can always guess as to the intention behind the original question, and go from there. Perhaps that means that we would end up with an entire family of algorithms instead of just one. Let's say, variations on a theme. There's no harm in that -- the number would be few, and probably somebody somewhere would find each one of them useful in time. That doesn't really impact my point about data languages being short in expressive power, though. I doubt any such algorithm or its criteria could be cleanly and succinctly stated in an existing data manipulation language. -- Sampo |
#22
| |||
| |||
|
|
Sampo Syreeni wrote: On Apr 10, 6:58 pm, paul c <toledobythe... (AT) oohay (DOT) ac> wrote: An average of averages is generally not equal to an overall average. No, and this gives rise to one of the most annoying statistical paradoxes out there as well: the Simpson-Yule one. Still, we can always guess as to the intention behind the original question, and go from there. Perhaps that means that we would end up with an entire family of algorithms instead of just one. Let's say, variations on a theme. There's no harm in that -- the number would be few, and probably somebody somewhere would find each one of them useful in time. That doesn't really impact my point about data languages being short in expressive power, though. I doubt any such algorithm or its criteria could be cleanly and succinctly stated in an existing data manipulation language. -- Sampo I think I agree with that but this doesn't mean I'm inclined that way. ... |
#23
| |||
| |||
|
|
... because even such a magnificent effort as Tutorial D goes far beyond what is necessary. In the case of Tutorial D, I'm pretty sure that this is because of the 'procedural' perspective and also because D&D pay homage to physical traditions involving concurrency and device techniques and an implied seamless progression away from sql. I don't say their motivation is wrong for them, but personally I could care less about the SQL legacy nor all the mis-specified db's out there, many of them built on ambiguous requirements. ... |
![]() |
| Thread Tools | |
| Display Modes | |
| |