https://wiki.tachyony.co.uk/w/index.php?action=history&feed=atom&title=Identity_map_pattern 2026-06-28T02:20:20Z Revision history for this page on the wiki MediaWiki 1.44.0 https://wiki.tachyony.co.uk/w/index.php?title=Identity_map_pattern&diff=48019&oldid=prev 2025-11-05T17:32:45Z

<p>Added short description</p> <p><b>New page</b></p><div>{{Short description|Database access design pattern}}<br /> {{One source|date=April 2020}}<br /> <br /> In [[database]] design, the &#039;&#039;&#039;identity map pattern&#039;&#039;&#039; is a database access [[Software design pattern|design pattern]] used to improve performance by providing a context-specific, in-memory [[database caching|cache]] to prevent duplicate retrieval of the same object data from the database.&lt;ref&gt;{{cite book | last = Fowler | first = Martin | title = Patterns of Enterprise Application Architecture | pages = 195–199 | publisher = Addison-Wesley | isbn = 0-321-12742-0 | year = 2003<br /> }}&lt;/ref&gt;<br /> <br /> If the requested data has already been loaded from the database, the identity map returns the same instance of the already instantiated object, but if it has not been loaded yet, it loads it and stores the new object in the map. In this way, it follows a similar principle to [[lazy loading]].<br /> <br /> There are 4 types of identity maps<br /> #Explicit<br /> #Generic<br /> #Session<br /> #Class<br /> <br /> == See also ==<br /> * [[Active record pattern|Active record]]<br /> * [[Identity function]]<br /> * [[Map (mathematics)]]<br /> * [[Lazy loading]]<br /> <br /> == References ==<br /> {{reflist}}<br /> <br /> {{Design Patterns Patterns}}<br /> <br /> [[Category:Architectural pattern (computer science)]]<br /> [[Category:Software design patterns]]<br /> <br /> <br /> {{comp-sci-stub}}</div>

imported>Chimneychobga