Answered by:
do the patterns use for database application ?

Question
-
do the patterns use for database application ? for example in a congress system that manage a conngress on web in this system we have some auhters that send some articles and then oprator receive this article and send that for arbiters then arbiters number this article. i want to know that in this simple systam , can we have benefite of using design pattern? if the answer is yes so which one is? thanks
هنگام سپیده دم خـروس سحری , دانی که چرا همی کند نوحـه گری , یعنی که نمودند در آیـینه صبح , کز عمر شبی گذشت و تو بی خبریMonday, July 27, 2009 9:05 AM
Answers
-
Hi
the following data access patterns are commonly
- repository pattern
http://martinfowler.com/eaaCatalog/repository.html
- active record
http://martinfowler.com/eaaCatalog/activeRecord.html
It also depends on the technology you're using in doing data acces (stored procedures, dynamic sql, linq to sql, nhibernate, ...)
Hope this helps you out
KR
Frederik
Please close the thread if your question is answered, and don't forget to rate the best responses!- Proposed as answer by frederikm Friday, July 31, 2009 6:59 AM
- Marked as answer by Esther FanMicrosoft employee Saturday, September 11, 2010 5:01 AM
Monday, July 27, 2009 9:49 AM -
It depends on the context. Patterns are always structured in the “problem, context, solution” form. It helped me to read a lot of data access related patterns and reflect on the problem and context for our particular application. As soon as you start seeing the connection between theory and practice in a useful way for a problem at hand, you probably can put a pattern to good use.
Please do realize that patterns are no surrogate for your own intuition and that applying or overloading your application with patterns will only increase complexity.
Have fun exploring,
Paul Gielens
http://paulgielens.com- Proposed as answer by Paul Gielens Wednesday, July 29, 2009 2:59 PM
- Marked as answer by Esther FanMicrosoft employee Saturday, September 11, 2010 5:01 AM
Wednesday, July 29, 2009 9:39 AM
All replies
-
Hi
the following data access patterns are commonly
- repository pattern
http://martinfowler.com/eaaCatalog/repository.html
- active record
http://martinfowler.com/eaaCatalog/activeRecord.html
It also depends on the technology you're using in doing data acces (stored procedures, dynamic sql, linq to sql, nhibernate, ...)
Hope this helps you out
KR
Frederik
Please close the thread if your question is answered, and don't forget to rate the best responses!- Proposed as answer by frederikm Friday, July 31, 2009 6:59 AM
- Marked as answer by Esther FanMicrosoft employee Saturday, September 11, 2010 5:01 AM
Monday, July 27, 2009 9:49 AM -
It depends on the context. Patterns are always structured in the “problem, context, solution” form. It helped me to read a lot of data access related patterns and reflect on the problem and context for our particular application. As soon as you start seeing the connection between theory and practice in a useful way for a problem at hand, you probably can put a pattern to good use.
Please do realize that patterns are no surrogate for your own intuition and that applying or overloading your application with patterns will only increase complexity.
Have fun exploring,
Paul Gielens
http://paulgielens.com- Proposed as answer by Paul Gielens Wednesday, July 29, 2009 2:59 PM
- Marked as answer by Esther FanMicrosoft employee Saturday, September 11, 2010 5:01 AM
Wednesday, July 29, 2009 9:39 AM