steve wrote:
To be charitable I suppose some will make use of it. I don' see that
it can do any harm except psychologically. It seems to me that I can
only pass the Orders table in the Northwind db if it's something else
(I assume their using the temp db). Then obviously I can't pass Orders
itself:)
I agree that SQL 2008 doesn't cover all of your suggestions - I was
just pointing out that it seems to cover at least some of them.
Most users probably can't appreciate where I coming from
because they do not know what it 'really' means to pass a table as a
parameter (as I've shown in many articles).
That's probably true in many cases, but here is (I suspect) why they
aren't learning from you in particular:
1) Dataphor is a niche product. Existing projects, of which there are
many, would suffer major switchover costs. Even new projects would
require the developer to spend some time learning Dataphor's
interface for app development. There are cases where these costs
would be worth it, but by failing to address these limits, you come
off sounding like an impractical ivory-tower theorist and/or fringe
religious cultist.
This would be greatly mitigated if you translated your ideas into
hypothetical extensions of SQL, and lobbied to have such extensions
added to the industry standard. I've even given examples of this
in the past, but you didn't seem to see any significant value in
it; even SQL 2008's actual (albeit incomplete) progress on this
front was met with no more excitement than "meh, might help a bit".
2) Grammar can't just be swept under the rug with "my style is more
important". First, technical subjects require clear communication,
full stop. Second, your style is far from unique; even in artistic
fields, only a few of us can be a cummings or Silverstein.
