In the early days of DB2, queries that were know to be slow were
called ad-hoc and strictly verboten in production code. I can see
where people my want to keep these, even knowing they are slow.
Perhaps _ad_hoc_view would bring provide this caution, without
calling them "slow". As was mentioned, they are all slow the first time.
Bob
On Jan 5, 2009, at 6:31 AM, Antony Blakey wrote:
How about relying on documentation?
This view may be slow (or not, for a small db). I might use it for
testing or ad-hoc maintenance. Who knows? The one thing you can say
for certain is that it is temporary, unlike every other view. That
is the defining characteristic of this facility, and hence
_temp_view is the appropriate name.
On 05/01/2009, at 9:03 PM, Geir Magnusson Jr. wrote:
How about _test_view? Kinda gets the point across that it's for
testing.
Antony Blakey
-------------
CTO, Linkuistics Pty Ltd
Ph: 0438 840 787
All that is required for evil to triumph is that good men do nothing.
