| ActiveMac | Anonymous | Create a User | Reviews | News | Forums | Advertise |
|
|
|
User Controls |
|
New User |
|
Login |
|
Edit/View My Profile |
|
|
|
|
|
|
|
ActiveMac |
|
Articles |
|
Forums |
|
Links |
|
News |
|
News Search |
|
Reviews |
|
|
|
|
|
|
|
News Centers |
|
Windows/Microsoft |
|
DVD |
|
ActiveHardware |
|
Xbox |
|
MaINTosh |
|
News Search |
|
|
|
|
|
|
|
ANet Chats |
|
The Lobby |
|
Special Events Room |
|
Developer's Lounge |
|
XBox Chat |
|
|
|
|
|
|
|
FAQ's |
|
Windows 98/98 SE |
|
Windows 2000 |
|
Windows Me |
|
Windows "Whistler" XP |
|
Windows CE |
|
Internet Explorer 6 |
|
Internet Explorer 5 |
|
Xbox |
|
DirectX |
|
DVD's |
|
|
|
|
|
|
|
TopTechTips |
|
Registry Tips |
|
Windows 95/98 |
|
Windows 2000 |
|
Internet Explorer 4 |
|
Internet Explorer 5 |
|
Windows NT Tips |
|
Program Tips |
|
Easter Eggs |
|
Hardware |
|
DVD |
|
|
|
|
|
|
|
Latest Reviews |
|
Applications |
|
Microsoft Windows XP Professional |
|
Norton SystemWorks 2002 |
|
|
|
Hardware |
|
Intel Personal Audio Player 3000 |
|
Microsoft Wireless IntelliMouse Explorer |
|
|
|
|
|
|
|
Site News/Info |
|
About This Site |
|
Affiliates |
|
ANet Forums |
|
Contact Us |
|
Default Home Page |
|
Link To Us |
|
Links |
|
Member Pages |
|
Site Search |
|
Awards |
|
|
|
|
|
|
|
Credits |
 |
CRUD, Only When You Can Afford It | |
|
||
| Time: 02:40 EST/07:40 GMT | News Source: Microsoft | Posted By: Robert Stein | ||
|
Microsoft Architect Maarten Mullender examines the CRUD (Create, Read, Update, Delete) model, and determines that CRUD requires a deep understanding of its limits, specifically when dealing with concurrency issues. | ||
|
Write Comment
Return to News |
Displaying 1 through 25 of 148 Last | Next |
The time now is
5:50:23 PM
ET.
Any comment problems? E-mail us |
| #1 By 135 (69.7.134.5) at 10/25/2004 8:42:30 AM |
| This is one of those articles you have to read through 3 times to fully understand what he is talking about. |
| #2 By 13030 (198.22.121.120) at 10/25/2004 3:51:32 PM |
| I think he's a little too hard on CRUD. A journal design does have one significant drawback that I didn't see him mention: answering the question "what is the current state of this entity?" Summary info is always calculated unless you want to violate the "never store summary data" tenet. A blended approach is always most practical since concurrency, ease of design implementation, ease of maintenance, and performance all must be considered. |
|
Write Comment
Return to News |
Displaying 1 through 25 of 148 Last | Next |
The time now is
5:50:23 PM
ET.
Any comment problems? E-mail us |
