Pros and Cons of holding all the business logic in stored procedures in web application [duplicate]
This question already has an answer here: Database Application Design Best Practices [duplicate] (1 answer) Closed 11 years ago. In some organization I worked for web applications are developed basing all the business logic in Database stored procedures. For example, use html for view and servlet as controllers to divert the client request to appropriate […]
Why put a simple query into a stored procedure in a web service?
I’m working as a junior programmer, and the senior programmer above me has instructed me to follow a certain unofficial policy for constructing new queries on our web development projects. Generally, we are developing an intranet site for some client, and they always have databases. He wants me to have a class containing a method for each query that the website will perform. This class calls web methods in a web service, hosted on the same machine. Those web methods use ADO to run stored procedures that perform simple queries. Sometimes the queries need parameters and sometimes they don’t. When I say simple queries, I mean simple…select * from table where column=@parameter
Calling MSSQL stored procedure from Zend Controller ? Any other approaches?
MSSQL and DB, Zend as PHP Framework,
Forced to write Stored Procedures
Can you think of some reasons that the management force the developers to write and call Stored Procedures instead of inline SQL statements directly?
Do stored procedures violate three-tier separation?
Some colleagues of mine have told me that having business logic in stored procedures in the database violates the three-tier separation architecture, since the database belongs to the data layer whereas stored procedures are business logic.
Established coding standards for pl/pgsql code
I need to standardize coding practices for project that compromises, among others, of pl/pgsql database, that has some amount of nontrivial code.
Modern practices for stored procedure-based applications
I work in a fairly large and old solution that has many entry points for different kinds of clients, with web sites for public access, web sites for internal access, some web sites and web services for partner companies access, etc.
Modern practices for stored procedure-based applications
I work in a fairly large and old solution that has many entry points for different kinds of clients, with web sites for public access, web sites for internal access, some web sites and web services for partner companies access, etc.
Modern practices for stored procedure-based applications
I work in a fairly large and old solution that has many entry points for different kinds of clients, with web sites for public access, web sites for internal access, some web sites and web services for partner companies access, etc.
Modern practices for stored procedure-based applications
I work in a fairly large and old solution that has many entry points for different kinds of clients, with web sites for public access, web sites for internal access, some web sites and web services for partner companies access, etc.