軟件截圖:
Apache Empire-db functions like a Java ORM but it provides extra support for basic data persistence methods.
This implicitly means better targeted SQL statements that provide better and more efficient query results.
Empire-db is easy to use, not requiring any special configuration, but it also comes well documented and with no special XML schema to learn.
If Empire-db is not what you were looking for, then check out Hibernate or the Java JPA.
What is new in this release:
- Implemented limitRows and skipRows for Oracle
- Improved DDL Syntax by allowing variable parameters for primary key and relations
- Allow replacement of statements in a DBScript
- Allow enabling / disabling foreign key constraints
- Improved JSF example, add business logic for retired state
What is new in version 2.4.3:
- Implemented limitRows and skipRows for Oracle
- Improved DDL Syntax by allowing variable parameters for primary key and relations
- Allow replacement of statements in a DBScript
- Allow enabling / disabling foreign key constraints
- Improved JSF example, add business logic for retired state
What is new in version 2.3.0:
- Allow specification of delete action for each DBRelation (ON DELETE CASCADE).
- Extend Record and Column interfaces by Record.isReadOnly() and Column.validate() methods.
- Simplify use of DBCommand:DBCommandParam class.
- Allow expression based indexes.
- Allow to specify the character column length in bytes (Non-Unicode) or chars (Unicode) for DDL generation.
What is new in version 2.2.0:
- A major API change by removing unrecommended legacy features that have been non-standard Java.
What is new in version 2.1.0:
- New and improved utilization of prepared statements which can be enabled / disabled by database property.
- Use of SLF4J instead of commons logging/Log4J.
評論沒有發現