Can't resolve for a while. Link button in a datalist
-
Mark Nischalke wrote:
A better solution to in-line SQL? Ever heard of stored procedures?
It's a myth. IMO, nothing wrong with inline SQL other than the difficulty of recompiling code when the DB structure changes. This can be avoided by abstracting the table structure using views. So still you can write inline SQLs safely. Please do correct me if you felt I am wrong.
Navaneeth How to use google | Ask smart questions
N a v a n e e t h wrote:
Please do correct me if you felt I am wrong.
Where do I start? This argument has been raised several times. Inline doesn't allow for separation of the business logic from the presentations, which a good design does, and increases maintenance and development. 10 apps with the same SQL statement must each be changed, rather changing one stored proc. Worse yet, if the schema changes, say a table or column is renamed, all statements must be changed instead of changing one stored proc. Inline statements also don't allow the RDBMS to optimize the execution or otherwise cache it for better performance. Just few of the many reasons. Then again, if you don't care about robust, well designed and performant applications, keep using inline statements.
only two letters away from being an asset
-
Sure I heard of stored procedures, I use them when I find necessary. "Response.Write("dr" + dr[0] + "
");" is for testing purposes. A lot of programmers do it when testing the results of the query. All the items are templated actually. You are right i mixed it with itemCreated. Thanks for the help.Albert83 wrote:
A lot of programmers do it when testing the results of the query.
:omg: :wtf: A lot of novice programmers. Professionals use a debugger.
only two letters away from being an asset
-
N a v a n e e t h wrote:
Please do correct me if you felt I am wrong.
Where do I start? This argument has been raised several times. Inline doesn't allow for separation of the business logic from the presentations, which a good design does, and increases maintenance and development. 10 apps with the same SQL statement must each be changed, rather changing one stored proc. Worse yet, if the schema changes, say a table or column is renamed, all statements must be changed instead of changing one stored proc. Inline statements also don't allow the RDBMS to optimize the execution or otherwise cache it for better performance. Just few of the many reasons. Then again, if you don't care about robust, well designed and performant applications, keep using inline statements.
only two letters away from being an asset
-
:laugh: :laugh: And if that one statement is executed 1000 times, what does that do for the performance of your system?
only two letters away from being an asset
-
:laugh: :laugh: And if that one statement is executed 1000 times, what does that do for the performance of your system?
only two letters away from being an asset
-
Albert83 wrote:
A lot of programmers do it when testing the results of the query.
:omg: :wtf: A lot of novice programmers. Professionals use a debugger.
only two letters away from being an asset