Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The story of database persistence in Java is already long and full of twists and turns:</p> <ul> <li><p><strong>JDBC</strong> is the low level API that <strong>everybody uses</strong> at the end to talk to a database. But without using a higher level API, you have to do all the grunt work yourself (writing SQL queries, mapping results to objects, etc).</p></li> <li><p><strong>EJB 1.0 CMP Entity Beans</strong> was a first try for a higher level API and has been successfully adopted by the big Java EE providers (BEA, IBM) but not by users. Entity Beans were too complex and had too much overhead (understand, poor performance). <strong>FAIL!</strong></p></li> <li><p><strong>EJB 2.0 CMP</strong> tried to reduce some of the complexity of Entity Beans with the introduction of local interfaces, but the majority of the complexity remained. EJB 2.0 also lacked portability (because the object-relational mapping were not part of the spec and the deployment descriptor were thus proprietary). <strong>FAIL!</strong></p></li> <li><p>Then came <strong>JDO</strong> which <em>is</em> a datastore agnostic standard for object persistence (can be used with RDBMS, OODBMS, XML, Excel, LDAP). But, while there are several open-source implementations and while JDO has been adopted by small independent vendors (mostly OODBMS vendors hoping that JDO users would later switch from their RDBMS datastore to an OODBMS - but this obviously never happened), it failed at being adopted by big Java EE players and users (because of weaving which was a pain at development time and scaring some customers, of a weird query API, of being actually too abstract). So, while the standard itself is not dead, I consider it as a failure. <strong>FAIL!</strong></p></li> <li><p>And indeed, despite the existence of two standards, proprietary APIs like <strong>Toplink</strong>, an old player, or <strong>Hibernate</strong> have been preferred by users over EJB CMP and JDO for object to relational database persistence (competition between standards, unclear positioning of JDO, earlier failure of CMP and bad marketing have a part of responsibility in this I believe) and Hibernate actually became the de facto standard in this field (it's a great open source framework). <strong>SUCCESS!</strong></p></li> <li><p>Then Sun realized they had to simplify things (and more generally the whole Java EE) and they did it in Java EE 5 with <strong>JPA</strong>, the Java Persistence API, which is part of EJB 3.0 and is the new standard for object to relational database persistence. JPA unifies EJB 2 CMP, JDO, Hibernate, and TopLink APIs / products and seems to succeed where EJB CMP and JDO failed (ease of use and adoption). <strong>SUCCESS!</strong></p></li> </ul> <p>To summarize, Java's standard for <strong>database persistence</strong> is <strong>JPA</strong> and should be preferred over others proprietary APIs (using Hibernate's implementation of JPA is fine but use JPA API) unless an ORM is not what you need. It provides a higher level API than JDBC and is meant to save you a lot of manual work (this is simplified but that's the idea).</p>
    singulars
    1. This table or related slice is empty.
    1. POJava - JDBC alternatives
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPascal Thivent
    1. USPascal Thivent
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POJava - JDBC alternatives
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    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. CObrilliant, THIS IS what I exaclty wanted, help most appreciated! BTW : Do you know what does NetBeans IDE use byt default? F.e. when I drag&drop DB table to JTable, NetBeans generates class with some management ... uses Entity Manager , Query Result etc.
      singulars
      1. PO
      1. USMike
    2. CO@Mike Thanks. Regarding NetBeans, recent versions have support for JPA by default (as Sun's standard, that makes sense). And indeed, `EntityManager` is part of JPA.
      singulars
      1. PO
      1. USPascal Thivent
    3. COgreat, I'll give a try to JPA I guess:)
      singulars
      1. PO
      1. USMike
 

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