Databases
StackOverflow2013
Postsdbo
POAbout Data Objects and DAO Design when using Hibernate
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAbout Data Objects and DAO Design when using Hibernate
    primarykey
    data
    text
    <p>I'm hesitating between two designs of a database project using Hibernate.</p> <p>Design #1.</p> <p>(1) Create a general data provider interface, including a set of DAO interfaces and general data container classes. It hides the underneath implementation. A data provider implementation could access data in database, or an XML file, or a service, or something else. The user of a data provider does not to know about it.</p> <p>(2) Create a database library with Hibernate. This library implements the data provider interface in (1).</p> <p>The bad thing about Design #1 is that in order to hide the implementation details, I need to create two sets of data container classes. One in the general data provider interface - let's call them DPI-Objects, the other set is used in the database library, exclusively for entity/attribute mapping in Hibernate - let's call them H-Objects. In the DAO implementation, I need to read data from database to create H-Objects (via Hibernate) and then convert H-Objects into DPI-Objects.</p> <p>Design #2.</p> <p>Do not create a general data provider interface. Expose H-Objects directly to components that use the database lib. So the user of the database library needs to be aware of Hibernate.</p> <p>I like design #1 more, but I don't want to create two sets of data container classes. Is that the right way to hide H-Objects and other Hibernate implementation details from the user who uses the database-based data provider?</p> <p>Are there any drawbacks of Design #2? I will not implement other data provider in the new future, so should I just forget about the data provider interface and use Design #2?</p> <p>What do you think about this? Thanks for your time!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USevergreen
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAbout Data Objects and DAO Design when using Hibernate
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POAbout Data Objects and DAO Design when using Hibernate
      1. USevergreen
      1. VTFavorite
    3. VO
      singulars
      1. POAbout Data Objects and DAO Design when using Hibernate
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload