http://16cards.com/2006/08/07/object-persistence-vs-data-access-api/ no significant tagline Mon, 20 Jul 2009 18:03:11 +0000 hourly 1 http://wordpress.org/?v=3.0 http://16cards.com/2006/08/07/object-persistence-vs-data-access-api/comment-page-1/#comment-1575 Jorge Thu, 30 Apr 2009 16:25:45 +0000 http://16cards.com/2006/08/07/object-persistence-vs-data-access-api/#comment-1575 What do you really think is better, or what escenarios could be better modeled with persistence API rather than using data access API, in my opinion Data access API lets you code things in simpler way, when you use persistence API, it lets you work more because you have to create classes to map tables and this consumes more developing time, and after that if the model changes you will have to make more changes because you will have to change the class, the ui, and the code, and when you use data access you might only change the ui and the code. What do you think of this? What do you really think is better, or what escenarios could be better modeled with persistence API rather than using data access API, in my opinion Data access API lets you code things in simpler way, when you use persistence API, it lets you work more because you have to create classes to map tables and this consumes more developing time, and after that if the model changes you will have to make more changes because you will have to change the class, the ui, and the code, and when you use data access you might only change the ui and the code.
What do you think of this?

]]>