Must....not....kill....
-
a = cx.ExecuteQuery("select top (1) a from foo where id={0}", id).First();
b = cx.ExecuteQuery("select top (1) b from foo where id={0}", id).First();
c = cx.ExecuteQuery("select top (1) c from foo where id={0}", id).First();... and about 20 more of those, yes, each effectively querying a scalar from foo with the same qualifier. Major redaction in the above, but you get the idea. So many things wrong about this. And people here wonder why the performance of nightly jobs is so bad. :((
Latest Article - A Concise Overview of Threads Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
I think this is the guy you're looking for.
-
Marc/others - be gentle with me ;). This is what, C#? So someone seriously got carried away with cut and paste... Did I understand your rant correctly?
Charlie Gilley <italic>Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
charlieg wrote:
with cut and paste.
Cut & paste would have been OK. This was copy and paste!
Latest Article - A Concise Overview of Threads Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
-
No no no! Do not change that, you'll break it! Don't you see that the other fields in that row of the table might change between queries? There's no transaction around these queries after all! And also the id parameter might change between queries, if a different process has write access to it. Oh, another thing: are you sure that the id column of the table is unique? So many things could go wrong with your refactoring. Better don't do that! You cannot find out what the original developer thought when he wrote that code thanks to a lack of proper documentation. :-D
Oh sanctissimi Wilhelmus, Theodorus, et Fredericus!
Bernhard Hiller wrote:
You cannot find out what the original developer thought
You're making a big assumption there! ;)
Latest Article - A Concise Overview of Threads Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
-
I think this is the guy you're looking for.
Tomaž Štih wrote:
I think this is the guy you're looking for.
Tools don't create bad code, it's the person wielding the tool!
Latest Article - A Concise Overview of Threads Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
-
a = cx.ExecuteQuery("select top (1) a from foo where id={0}", id).First();
b = cx.ExecuteQuery("select top (1) b from foo where id={0}", id).First();
c = cx.ExecuteQuery("select top (1) c from foo where id={0}", id).First();... and about 20 more of those, yes, each effectively querying a scalar from foo with the same qualifier. Major redaction in the above, but you get the idea. So many things wrong about this. And people here wonder why the performance of nightly jobs is so bad. :((
Latest Article - A Concise Overview of Threads Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
-
a = cx.ExecuteQuery("select top (1) a from foo where id={0}", id).First();
b = cx.ExecuteQuery("select top (1) b from foo where id={0}", id).First();
c = cx.ExecuteQuery("select top (1) c from foo where id={0}", id).First();... and about 20 more of those, yes, each effectively querying a scalar from foo with the same qualifier. Major redaction in the above, but you get the idea. So many things wrong about this. And people here wonder why the performance of nightly jobs is so bad. :((
Latest Article - A Concise Overview of Threads Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
-
Tomaž Štih wrote:
I think this is the guy you're looking for.
Tools don't create bad code, it's the person wielding the tool!
Latest Article - A Concise Overview of Threads Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
That's what I always say about guns. :cool:
-
a = cx.ExecuteQuery("select top (1) a from foo where id={0}", id).First();
b = cx.ExecuteQuery("select top (1) b from foo where id={0}", id).First();
c = cx.ExecuteQuery("select top (1) c from foo where id={0}", id).First();... and about 20 more of those, yes, each effectively querying a scalar from foo with the same qualifier. Major redaction in the above, but you get the idea. So many things wrong about this. And people here wonder why the performance of nightly jobs is so bad. :((
Latest Article - A Concise Overview of Threads Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
This is were the Warhammer 40K universe gets it right, I think. They lobotomize and reeducate people like that. Clean, cost effective, ecological. I've pitched a similar idea, but marketing disagrees every time I propose to stab people. The numbers check out though; the reduction in technical debt and project costs is significant, even if you reallocate resource to pay for the funerals.
-
a = cx.ExecuteQuery("select top (1) a from foo where id={0}", id).First();
b = cx.ExecuteQuery("select top (1) b from foo where id={0}", id).First();
c = cx.ExecuteQuery("select top (1) c from foo where id={0}", id).First();... and about 20 more of those, yes, each effectively querying a scalar from foo with the same qualifier. Major redaction in the above, but you get the idea. So many things wrong about this. And people here wonder why the performance of nightly jobs is so bad. :((
Latest Article - A Concise Overview of Threads Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
-
a = cx.ExecuteQuery("select top (1) a from foo where id={0}", id).First();
b = cx.ExecuteQuery("select top (1) b from foo where id={0}", id).First();
c = cx.ExecuteQuery("select top (1) c from foo where id={0}", id).First();... and about 20 more of those, yes, each effectively querying a scalar from foo with the same qualifier. Major redaction in the above, but you get the idea. So many things wrong about this. And people here wonder why the performance of nightly jobs is so bad. :((
Latest Article - A Concise Overview of Threads Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
I don't get it ! ! ! Why must you 'not kill'? It seems justified.