On 25/07/13 08:14, Vincenzo Romano wrote:
2013/7/25 Luca Ferrari :
On Thu, Jul 25, 2013 at 2:57 AM, Some Developer
wrote:
The added advantage of removing load from the app servers so they can
actually deal with serving the app is a bonus.
Uhm...I don't know what application yo
On 25/07/13 07:57, Luca Ferrari wrote:
On Thu, Jul 25, 2013 at 2:57 AM, Some Developer
wrote:
The added advantage of removing load from the app servers so they can
actually deal with serving the app is a bonus.
Uhm...I don't know what application you are developing, but I don'
On 24/07/13 20:33, Jeff Janes wrote:
On Tue, Jul 23, 2013 at 5:29 PM, Some Developer
wrote:
I've done quite a bit of reading on stored procedures recently and the
consensus seems to be that you shouldn't use them unless you really must.
I think that mostly speaks to the method yo
On 24/07/2013 14:58, Merlin Moncure wrote:
On Wed, Jul 24, 2013 at 8:31 AM, Some Developer
wrote:
On 24/07/13 14:21, Gauthier, Dave wrote:
I find stored procedures to be a God-send. The alternative, external
code, is the risky, difficult and often poorer performing approach to the
problems
On 24/07/13 02:56, Andrew Sullivan wrote:
On Tue, Jul 23, 2013 at 06:55:56PM -0600, John Meyer wrote:
are accessing your database at one time? And most importantly, what
are you best at?
That is one of the most important questions, for sure, but there's a
close second that I'd suggest: what a
On 24/07/13 01:55, John Meyer wrote:
Taking an absolutist position either way is pretty blind. What is the
purpose of the procedure? Is it enforcing business rules? Are these
rules that must be enforced against already existing data or are they
more akin to validation of a credit card. How m
I've done quite a bit of reading on stored procedures recently and the
consensus seems to be that you shouldn't use them unless you really must.
I don't understand this argument. If you implement all of your logic in
the application then you need to make a network request to the database
serve
