Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I can recommend <a href="https://www.hibernate.org/" rel="noreferrer">Hibernate</a>. It is widely used (and for good reasons), and the fact that the <a href="http://java.sun.com/javaee/technologies/persistence.jsp" rel="noreferrer">Java Persistence API</a> specification was lead by the main designer of Hibernate guarantees that it will be around for the foreseeable future :-) If portability and vendor neutrality is important to you, you may use it via JPA, so in the future you can easily switch to another JPA implementation.</p> <p>Lacking personal experience with JDO, I can't really compare the two. However, the benefits of Hibernate (or ORM in general) at first sight seem to be pretty much the same as what is listed on the <a href="http://java.sun.com/jdo/" rel="noreferrer">JDO page</a>. To me the most important points are:</p> <ul> <li>DB neutrality: Hibernate supports several SQL dialects in the background, switching between DBs is as easy as changing a single line in your configuration</li> <li>performance: lazy fetching by default, and a lot more optimizations going on under the hood, which you woulds need to handle manually with JDBC</li> <li>you can focus on your domain model and OO design instead of lower level DB issues (but you can of course fine-tune DML and DDL if you wish so)</li> </ul> <p>One potential drawback (of ORM tools in general) is that it is not that suitable for batch processing. If you need to update 1 million rows in your table, ORM by default will never perform as well as a JDBC batch update or a stored procedure. Hibernate can incorporate stored procedures though, and it supports batch processing to some extent (I am not familiar with that yet, so I can't really say whether it is up to the task in this respect compared to JDBC - but judging from what I know so far, probably yes). So if your app requires some batch processing but mostly deals with individual entities, Hibernate can still work. If it is predominantly doing batch processing, maybe JDBC is a better choice.</p>
    singulars
    1. This table or related slice is empty.
    1. POJava - JDBC alternatives
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPéter Török
    1. USPéter Török
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO+1 - you beat me to it. Hibernate is a great ORM to use, with sufficient flexibility to allow you to complete pretty much any task that you would do in JDBC directly.
      singulars
      1. PO
      1. USElie
    2. COYep I heared lot of about Hibernate Do you recommend it to use in small projects? Like 50 classes, 10-15 DB tables? Or stick to manual JDBC data management?
      singulars
      1. PO
      1. USMike
    3. CO@Mike Good question. Some say it is overkill for small projects. I have done a smaller project using Cayenne (http://cayenne.apache.org), a similar ORM tool, and I was satisfied. So I would definitely give it a try. It _might_ feel like you need to do a lot of "extra" work at startup, but IMHO it will pay back in the long run.
      singulars
      1. PO
      1. USPéter Török
 

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