Talk:Data Access Object

From Wikipedia, the free encyclopedia

Contents 1 Razor 2 persistencifier? 3 Doubt 4 Disadvantages

[edit] Razor

I've read through the Occam's razor page and I can't find any discussion on how it's typically used in the field of applied science, let alone software development. I think it's use in this article is invalid and confusing and should be removed. This design pattern should be used because of pragmatic reasons in order to abstract as much as possible the interaction between complex systems. This can be a valid reason to add an extra layer and there's no reason to shed doubt over this requirement if it's not constructive."

[edit] persistencifier?

Sorry, persistencifier is not a word.

[edit] Doubt

How i can call a procedure created in the module section of Access 97 from Visual Basic by using DAO?

[edit] Disadvantages

The section was deleted because it was really about any kind of database abstraction, because the asserted complexity is actually a matter of taste, and because the asserted runtime abstraction penalty is simply not plausible: a DAO transforms data between objects and single columns, which is unavoidable, and executes the same queries as any other abstraction or non-abstraction, without adding excess baggage other than function calls and object references. —Preceding unsigned comment added by 81.208.61.202 (talk) 11:12, 6 September 2007 (UTC)