Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Well, you can either access the database by:</p> <ul> <li>providing the url/driver/password/etc. information in the <code>persistence.xml</code> using your jpa-provider properties (in your case <code>hibernate.connection.*</code>) or the JPA 2.0 standardised <code>javax.persistence.jdbc.*</code> ones - this basically looks like the example you've posted,</li> <li><p>creating a Data Source in the ApplicationServer and just referring to it in the <code>persistence.xml</code> (through it's JNDI name you provide during creation) which might look similar to this (without the XML schema definition for the sake of brevity) :</p> <pre><code>&lt;persistence&gt; &lt;persistence-unit name="SomeApp"&gt; &lt;provider&gt;org.hibernate.ejb.HibernatePersistence&lt;/provider&gt; &lt;jta-data-source&gt;jdbc/myDB&lt;/jta-data-source&gt; &lt;/persistence-unit&gt; &lt;/persistence&gt; </code></pre></li> </ul> <p>What you're actually doing right now (with these properties) is using the JDBC.</p> <hr> <p>I would definitely go with the creation of the Data Source in the ApplicationServer rather than providing it in the properties in <code>persistence.xml</code>. It allows you to dynamically change the end-database, it's type, credentials, manage connection pools, etc. without even touching your descriptor.</p> <p>It's also safer, as the credentials are not written in the plain file left on your server.</p> <p>As a side note, please remember that the <code>javax.persistence.jdbc.*</code> properties are a JPA provider <strong>must requirement</strong> for the <strong>Java SE</strong> environment, but it's <strong>optional</strong> for <strong>Java EE</strong>.</p> <p>Hope that helps!</p>
    singulars
    1. This table or related slice is empty.
    1. PODo I need DataSource in JPA Hibernate project?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USPiotr Nowicki
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODo I need DataSource in JPA Hibernate project?
      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. 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. VTAcceptedByOriginator
    1. COHelped a lot! Now I undersand the difference.
      singulars
      1. PO
      1. USrivasket
    2. COBut still I don't feel this mysql connector idea. Do I have to deploy it on JBoss or not? I have noticed that during war file deployment on JBoss I get such info between a lot of other ones: 01:06:27,794 WARN [org.hibernate.engine.jdbc.internal.JdbcServicesImpl] (MSC service thread 1-4) HHH00342:Could not obtain connection to query metadata : No suitable driver found for jdbc:mysql://localhost:3306/... Why it cannot find driver even if I have it either in JBOSS deployments directory or WEB-INF/lib?
      singulars
      1. PO
      1. USrivasket
    3. CO@rivasket take a look at [DataSource Configuration In AS7](http://community.jboss.org/wiki/DataSourceConfigurationInAS7). And give me a sign if it was of any help to you.
      singulars
      1. PO
      1. USPiotr Nowicki
 

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