When we did this, the project manager had the idea that actually inlining SQL statements (like SELECT col1, col2, etc.) in the C# code is a good idea. Some of us told him it's going to be painful, but he didn't listen. It became a nightmare after roughly a week; by that time the code had a lot of inline SQL code and any table changes involved going through the code and fitting all SQL code to work with the new schema. But even then he decided to stick to it - I still don't know, why.
I was lucky, because I got out on my own, but almost the entire team was fired later when the project was still in shambles months after the deadline. > -----Original Message----- > From: Discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of Brady Kelly > Sent: Thursday, November 16, 2006 10:02 > To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM > Subject: Re: [ADVANCED-DOTNET] Data Structures in .Net? > > Why is this? Let's first look at the term 'inline'. Taken > literally I'll agree with you about the nightmare, because > the SQL is just splashed around in whatever code sections > need it, but if I can use the term 'coded' SQL to mean SQL > statements written in, say, C#, I will argue that the > nightmare isn't always implied. > > If each SQL operation is well thought out, and coded > according to certain quality standards, there is very little > different to using stored procs. > The Create method that takes a business object as a > parameter, and calls a stored procedure, and the Create > method that takes the same parameter and builds a SQL > statement appear exactly the same to my client code, and once > developed and tested, can be trusted the same by my client code. > > > -----Original Message----- > > From: Discussion of advanced .NET topics. [mailto:ADVANCED- > > [EMAIL PROTECTED] On Behalf Of Gyorgy Bozoki > > Sent: 16 November 2006 05:55 PM > > To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM > > Subject: Re: [ADVANCED-DOTNET] Data Structures in .Net? > > > > I fully agree with you stored procedures - using inline SQL > turns code > > into a nightmare very quickly. Been there, done that (although I > > opposed doing > > it.) =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
