Apache Empire-db: Difference between revisions

Content deleted Content added
m convert special characters found by Wikipedia:Typo Team/moss (via WP:JWB)
Changed no citations template to notability (couldn't find secondary sources)
Line 1:
{{Notability|Products|date=March 2022}}{{Infobox software
{{Unreferenced|date=May 2011}}
{{Infobox software
| name = Apache Empire-db
| logo = Apache_Empire-db_Logo.svg
Line 22 ⟶ 21:
Compared to [[Object-relational mapping]] (ORM) or other data persistence solutions such as [[Hibernate (Java)|Hibernate]], [[iBATIS]] or [[TopLink]] Empire-db does not use XML files or Java annotations to provide a mapping of plain (old) Java object ([[POJO]]'s) to database tables, views and columns. Instead Empire-db uses a Java object model to describe the underlying data model and an API that works almost solely with object references rather than [[string literal]]s.
 
Empire-db's aim is to provide better software quality and improved maintainability through increased compile-time safety and reduced redundancy of metadata. Additionally applications may benefit from better performance due to full control over [[SQL]] statements and their execution by the developer compared to most OR-mapping solutions.<ref>{{Cite web |title=Apache Empire-db |url=https://empire-db.apache.org/pages/home.html |access-date=2022-03-21 |website=empire-db.apache.org}}</ref>
 
== Major benefits ==