Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 CRUD

Author  Topic 

mpetanovitch
Yak Posting Veteran

52 Posts

Posted - 2005-04-26 : 19:35:18
I want to get people's take on the concept of CRUDing a database.
To those who do not know what CRUD is.
C - create
R - read
U - update
D - delete

The concept is simple, you have these basic stored procedures for each table in your database. The application would use these to communicate with your database in a very generic way. .NET data adpaters and data sets have alot of support for these concepts, thus I see why more and more application developers think in this manner.

Note: there can be more complex select statements as to utilize complex joining and the power of TSQL set based language, so I think the R part of CRUD is not a viable architecture. My main concern in CRUDing lies in the simplicity of update/insert/delete statements.

Here is a good link to someone against CRUD:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/crud-afford.asp

Again, please share any comments or opinions you may have. Thanks


byrmol
Shed Building SQL Farmer

1591 Posts

Posted - 2005-04-26 : 20:23:07
I must say I found it a very difficult article to follow. That's just me I guess..

My big issue here is the almost complete lack of understanding of what a half decent database can and should do.
quote:
Databases do not provide business logic to protect updates. The end user or client is not allowed to update the database directly. Applications or services provide that business logic to keep the state consistent and they update the data. Therefore databases can expose CRUD logic, they don't need to know anything more about the data.


......Shudder.......

A well designed database can/should, if you can excuse the terminology, stand naked before all users/interfaces. It is up to the DBA, not the UI/middle tier/whatever programmers to protect data consistency. Which brings up the final point.. What is the difference between business logic and data logic?

DavidM

A front-end is something that tries to violate a back-end.
Go to Top of Page

robvolk
Most Valuable Yak

15732 Posts

Posted - 2005-04-26 : 20:28:28
Business logic is an oxymoron, I know that for a fact.
Go to Top of Page

derrickleggett
Pointy Haired Yak DBA

4184 Posts

Posted - 2005-04-26 : 22:36:47
What is the difference between business logic and data logic?
--Data logic IS the business logic. And if you don't have data logic, the business will eventually pay for it dearly.
/RANT

MeanOldDBA
derrickleggett@hotmail.com

When life gives you a lemon, fire the DBA.
Go to Top of Page
   

- Advertisement -