GeekArticles 
Java J2SEHibernate 3 Formulas
Author: onjava.com |
Published: 26th Aug 2005 |
Visited: 1222 times |
Add CommentFiled in: J2SE
Hibernate's formula element has been limited in previous versions of the popular object-relational mapping framework, but in Hibernate 3, your formulas can be used in many new ways that will simplify and empower your programming. Dai Yifan shows you what's new.
Read Article Sponsored Links
Related Articles
• The Java EE Application as an EJB/Spring/Hibernate Hybrid Java EE 5 provides all the features you need to build a robust enterprise application right in an EJB 3.0 container, but incorporating the relative strengths of Spring and Hibernate can further improve the productivity and quality of your applicat ...
• New Tutorial: Hibernate Learn to use this open source tool that provides object/relational persistence and query servi ...
• Support of Custom Fields with Hibernate Introduction
When developing corporate-level business applications (Enterprise Scale) customers often requires implementing support for extensibility of the application object model not modifying the system source code. Use of extensible domain model allows for development of new functionality with ...
• New Tutorial: Hibernate Learn to use this open source tool that provides object/relational persistence and query servi ...
• Agile Database Refactoring with Hibernate
Your data model was near perfect when your application was first written. Since then, it has... evolved. In this article, we will show readers how to upgrade their faulty schemas and data models without affecting existing applications or processes. ...
• An Introduction to Hibernate 3 Annotations
Hibernate is just about the defacto standard for Java database persistence. With Hibernate 3, it has become even easier to specify how your Java objects are stored in a database. In this article, John Smart shows how Java 5 annotations are used by Hibernate to simplify your code and make persis ...
• Don't Let Hibernate Steal Your Identity
Hibernate has one set of ideas about how to make something unique, such as using a database sequence number as an ID. But this clashes with Java's need for implementations of equals() and hashCode() that determine identity for objects, even those that haven't yet made a trip to the da ...
