You did notice the winky face in my post, yes?
Basically what I'm getting at is that in some circumstances it makes sense to have business logic inside stored procs, and in other circumstances it makes sense to have it in the middle tier.
My last project was using the Spring/Hibernate model because that made more sense. In my current project we are using stored procs, and I believe it makes sense in this context too. Both were/are the correct decisions in the context of the respective projects.
Anyone who says business logic should only ever exist in one place or the other is wrong - be they DBA or developer.
Basically what I'm getting at is that in some circumstances it makes sense to have business logic inside stored procs, and in other circumstances it makes sense to have it in the middle tier.
My last project was using the Spring/Hibernate model because that made more sense. In my current project we are using stored procs, and I believe it makes sense in this context too. Both were/are the correct decisions in the context of the respective projects.
Anyone who says business logic should only ever exist in one place or the other is wrong - be they DBA or developer.
Comment