 | This article is rated Stub-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||
| |||||||||||
Shouldn't this article be merged with Database abstraction layer, or at least reference it? "Six by nine. Forty two." 13:14, 2 January 2011 (UTC) — Preceding unsigned comment added by Falcor84 (talk • contribs)
- I think so, especially since this has errors and definitely has omissions. Sam Tomato (talk) 05:33, 21 August 2017 (UTC)
- I revised the article to try to give it a clearer scope distinct from Database abstraction layer and Data access object. My view is that a data access layer is the broader architectural boundary for accessing data, while a database abstraction layer is more specifically about abstracting differences between database systems, and a data access object is a particular object-oriented pattern. I also tried to reduce the previous conflation with ORM-style examples by treating ORM as one implementation pattern rather than the definition. Happy for others to improve or trim. Cryptonomicant (talk) 19:40, 24 May 2026 (UTC)
ASP.NET
editThis currently says "This acronym is prevalently used in Microsoft ASP.NET environments.". I will remove "ASP.NET" from that; there is nothing that limits its use to ASP.NET. Sam Tomato (talk) 05:36, 21 August 2017 (UTC)