Isolating the database to libraries is usually the best approach. Database independence is being able to move to different DB's without code change outside the database. This is often a pipedream IMHO.
Thanks, Shawn Wildermuth http://adoguy.com C# MVP, MCSD.NET, Author and Speaker ->-----Original Message----- ->From: Unmoderated discussion of advanced .NET topics. ->[mailto:[EMAIL PROTECTED] On Behalf Of Chip Dunning ->Sent: Wednesday, September 14, 2005 10:33 AM ->To: [email protected] ->Subject: Re: [ADVANCED-DOTNET] Business logic -> ->I do not understand why so many thing database independence ->is a fallacy? A good design is flexible enough to absorb the ->redesign of any one component without failing. If you cannot ->rip out your database and put in a new one then you are too ->tightly coupled. It would be like being so dependent upon IIS ->that you could not roll out a solution using Apache. Neither ->would be considered a good design. It does not matter what ->component of the system it is (Web Server, Compiler, ->libraries, or database) if you cannot pull it out and replace ->it without disrupting the system - it is a bad design. -> ->I have been on 3 database changes. The first moved from ->Access to Oracle. ->The second moved from Poet (OODB) to Oracle. The last moved ->from Oracle to SQL Server. The first one was an abject ->failure because our DBA was a ID-10-T. The second went faily ->smoothly because all database calls were encapsulated in ->libraries. Each GUI application had to be re-compiled since ->they had static links to these libraries, but not a single ->line was changed. ->The third was ongoing when I moved to a new job, but it was ->going very positive. -> -> -> ->Chip -> ->On 9/13/05, Shawn Wildermuth <[EMAIL PROTECTED]> wrote: ->> ->> Yes and no. I would probably not put it in the database, but that ->> doesn't mean its wrong. The fact of the matter is that even outside ->> the database (ours was entirely outside the database), it still ->> required a major re-write. Database independence is a ->falicy. Keeping ->> your logic outside the DB doesn't buy you much unless you are doing ->> strict SQL '92/95...which no one does because it performs ->like a dog. ->> But DB Independence is an entirely different topic that I ->don't want ->> to get caught walking the tangent gangplank ;) ->> ->> Thanks, ->> ->> Shawn Wildermuth ->> http://adoguy.com ->> C# MVP, MCSD.NET <http://MCSD.NET>, Author and Speaker ->> ->> ->-----Original Message----- ->> ->From: Unmoderated discussion of advanced .NET topics. ->> ->[mailto:[EMAIL PROTECTED] On Behalf Of ->Franklin ->> ->Gray ->> ->Sent: Tuesday, September 13, 2005 6:10 PM ->> ->To: [email protected] ->> ->Subject: Re: [ADVANCED-DOTNET] Business logic ->> -> ->> ->""No technical or functional requirement, just a business ->one. This ->> ->is the very nature of how business gets done and ends up with a ->> ->myriad of different architectures" ->> -> ->> ->Wouldn't this be an example as to why not to put the BL ->in the DB? ->> ->Never know when somebody is going to say "lets switch". ->> -> ->> ->=================================== ->> ->This list is hosted by DevelopMentor. http://www.develop.com ->> -> ->> ->View archives and manage your subscription(s) at ->> ->http://discuss.develop.com ->> 09/13/2005 06:15:13 PM ->> ->> =================================== ->> This list is hosted by DevelopMentor(r) http://www.develop.com ->> ->> View archives and manage your subscription(s) at ->> http://discuss.develop.com ->> -> -> -> ->-- ->"The reason the mainstream is considered a stream is because ->it's so shallow" --George Carlin -> ->=================================== ->This list is hosted by DevelopMentorR http://www.develop.com -> ->View archives and manage your subscription(s) at ->http://discuss.develop.com 09/14/2005 10:52:40 AM =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
