One is not better than the other. They are different.
Sometimes it's better to say that the API point of compatibility is the database and its stored procs, and sometimes it's better to say that the API point of compatibility is a data access layer. They both have advantages and disadvantages, and there is no single right answer. "The best" implies "for who" and "for what". There is no single "the best", whether you're talking about data access strategies, or APIs, or OSes, or cars, or houses, or... The key to survival is consistency. Whatever you do, encapsulate it well and consistently, and you'll be fine. On 11/16/06, Chris Wuestefeld <[EMAIL PROTECTED]> wrote:
I agree that the quality level can be fine. The problem is that you're storing the lowest-level persistence *INSIDE* the next layer up doubles (at least) maintenance tasks. When data model changes occur, you've got to change dependent SQL in every relevant module.
-- Brad Wilson http://www.agileprogrammer.com/dotnetguy/ http://www.flickr.com/photos/dotnetguy/ "If programmers got paid to remove code from software instead of writing new code, software would be a whole lot better." - Nicholas Negroponte =================================== This list is hosted by DevelopMentor� http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
