But why? SQL is built well to do mathematical operations and return data. Manipulating data is 'typically' better to be done at a higher layer. This article is a great example of how to use it, but a bad example of when (which I do not believe was her intention).
I'm sorry if you misunderstood me. I was referring to her article being a bad example of when to use it. However, that was not the intent of the article, so I just wanted readers to realize that this would 'probably' not be a good business case.
But why? SQL is built well to do mathematical operations and return data. Manipulating data is 'typically' better to be done at a higher layer. This article is a great example of how to use it, but a bad example of when (which I do not believe was her intention).
I'm tired
I'm sorry if you misunderstood me. I was referring to her article being a bad example of when to use it. However, that was not the intent of the article, so I just wanted readers to realize that this would 'probably' not be a good business case.
I'm tired
I'm not sure what your upset about, I wasn't negative at all and, in fact, complemented the writer on her article.