Re: looping
- From: "Tony Rogerson" <tonyrogerson@xxxxxxxxxx>
- Date: Sat, 14 Nov 2009 07:32:17 -0000
Tony, your off-topic personal insults and outbursts without any
Kettle - pot - black.
Whilst I have a one to one relationship in terms of --ROGGIE-- to {poster} where {poster} = '--CELKO', you on the other hand insult the majority of posters - granted you have been better in the last WEEK - but 7 days compared to 10 years is a drop in the ocean in terms of YOUR OWN attitude.
Now - stop insulting people on this forum.
Keep your posts relevant and accurate so the advice you give is actually relevant and actually works on the product this forum has a context for ie MICROSOFT SQL SERVER.
supporting material are just not the important to me. I am doing this
while two weeks of laundry is running, so let me try to stay on topic,
I always stay on topic; you know that, people on here know that - and believe me it will continue until you get a grasp of the real world or stap strap lining your posts with something like "this post is only relevant to the ANSI SQL standard, it may not work on this product".
Now, on the other hand it is you that drifts off topic, especially when challenged on something (usually real world) that you have no defense for, for instance but not limited to - consistency of date formats within SQL SERVER, ie you must use YYYYMMDD, the use of surrogate keys within the product and our necessity in using the IDENTITY property, your rants about temporary tables being some sort of scratch tape - enough typing, but I could go on.
Anyway, out of interest - why have you parked yourself on this forum, why do we have to put up with your canned crap and out of date answers? I never see you on the Oracle nor DB2 forums, the products you are so familiar with!??!
1) Microsoft SQL people want to move to more and more standard SQL.
This is why the DATE data type defaults to "yyyy-mm-dd" and not
"yyyymmdd" among other things. Look for more of this later. Oh,
this has been one of your rants against me, why have you not commented
that decision?
It's a good move forward and I look forward to when EVERYBODY is on SQL Server 2008.
Now, what about the majority of customers who aren't on SQL Server 2008? What about the "legacy code museum" as you put it? What about the "real world"??
Now, lets throw this around the other way - why aren't you using infix notation when the great majority, including ALL examples in books online, system stored procedures and KB articles are all infix whereas you insist on using the old style join in the WHERE - a very dangerous concept.
2) The [ROWS | RANGE] sub-clause in OVER () is considered important.
That means your cursor to do running totals might become less
desirable in a few releases.
How exactly does that help the developer TODAY in writing a solution that actually scales? Answer: it doesn't.
Frankly, I have avoided database side running totals because I
consider them reporting and not data retrieval. Front end report
tools do a better job than cursors. The few times I did them was with
a scalar subquery in the SELECT clause; small data sets and a quick
solution that would not have to port or to scale.
No doubt because you realise its a real world and common requirement that a set based solution just cannot deliver.
I still wait for some examples in comparison to cursors.
And yet again you rely on yet another product, yet another developer to do what can already be done in the engine - one skill set, on set of code to develop, support and maintain.
3) There are other easy, but less requested, standards that could be
added. While it is good to listen to the customers, they do not know
that they want something until they see it -- Post-It notes comes to
mind.
I'm in a perfect position to answer this question - I'm out there in the field actually listening to customers and understanding the challenges myself.
The question is - are you? I think you are just relying on and listening to hearsay when you come up with these conclusions - a perfect example of that is your opinions (though wrong) about CLR.
This is where you could do us all a favour - if you want to be taken seriously - get out in the real world back into industry and see what is actually going on, what business needs - stop guessing! You cannot draw an industrial opinion on what is posted in this forum which seems to be what you are doing now you have stagnated for the past decade.
I am going to propose that TRANSLATE() be considered. Then usual
nested REPLACE() is pretty effective, but hard to non-LISP programmers
to read :)
While it is easy to maintain with a recursive text editor, it is bitch
to read.
1000 parameters, 52 nested REPLACE's, code anything that is not set achievable in C or COBOL.
Hardly practical in the real world.
Anyway - I'm here for good --celko--; given your attitude on here for the past decade its time you are brought to task and people shown just how out of touch you really are.
--ROGGIE--
.
- Follow-Ups:
- Re: looping
- From: --CELKO--
- Re: looping
- References:
- looping
- From: Brian S.
- Re: looping
- From: sloan
- Re: looping
- From: Brian S.
- Re: looping
- From: --CELKO--
- Re: looping
- From: Tony Rogerson
- Re: looping
- From: Uri Dimant
- Re: looping
- From: Tony Rogerson
- Re: looping
- From: --CELKO--
- looping
- Prev by Date: Re: Reference temporary table twice
- Next by Date: Re: T-SQL is not quite there yet
- Previous by thread: Re: looping
- Next by thread: Re: looping
- Index(es):
Relevant Pages
|