Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I use the following configuration (directly inspired by the <a href="http://docs.jboss.org/hibernate/core/3.3/reference/en/html/tutorial.html#tutorial-firstapp-configuration" rel="noreferrer">Hibernate tutorial</a>) without any problem:</p> <pre><code>&lt;hibernate-configuration&gt; &lt;session-factory&gt; &lt;!-- Database connection settings --&gt; &lt;property name="hibernate.connection.driver_class" value="org.hsqldb.jdbcDriver"/&gt; &lt;property name="hibernate.connection.url" value="jdbc:hsqldb:mem:foobar"/&gt; &lt;property name="hibernate.connection.username" value="sa"/&gt; &lt;property name="hibernate.connection.password" value=""/&gt; &lt;!-- JDBC connection pool (use the built-in) --&gt; &lt;property name="connection.pool_size"&gt;1&lt;/property&gt; &lt;!-- SQL dialect --&gt; &lt;property name="hibernate.dialect" value="org.hibernate.dialect.HSQLDialect"/&gt; &lt;!-- Enable Hibernate's automatic session context management --&gt; &lt;property name="current_session_context_class"&gt;thread&lt;/property&gt; &lt;!-- Disable the second-level cache --&gt; &lt;property name="cache.provider_class"&gt;org.hibernate.cache.NoCacheProvider&lt;/property&gt; &lt;!-- Echo all executed SQL to stdout --&gt; &lt;property name="show_sql"&gt;true&lt;/property&gt; &lt;!-- Drop and re-create the database schema on startup --&gt; &lt;property name="hibernate.hbm2ddl.auto" value="update"/&gt; &lt;mapping resource="..."/&gt; &lt;/session-factory&gt; &lt;/hibernate-configuration&gt; </code></pre> <p>When using an in-memory HSQLDB, there is no need to start anything explicitly. Just use the <code>mem:</code> protocol and the in-memory database will get started from JDBC. </p> <h3>See also</h3> <ul> <li><a href="http://www.theserverside.com/news/1365222/Unit-Testing-Hibernate-With-HSQLDB" rel="noreferrer">Unit-Testing Hibernate With HSQLDB</a></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POstarting and stopping hsqldb from unit tests
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USPascal Thivent
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POstarting and stopping hsqldb from unit tests
      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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThis is exactly what I'm doing, but when I run the unit test I get a java.sql.SQLException: socket creation error. I also get a [main] WARN org.hibernate.cfg.SettingsFactory - Could not obtain connection to query metadata from hibernate.
      singulars
      1. PO
      1. USCasey
    2. COI've noticed that it also is always creating files in my classpath that I would expect to be created if I was using a file based DB and not an in memory one.
      singulars
      1. PO
      1. USCasey
    3. COI'm giving you the answer for confirming that my configuration was correct, leading me to look at other reasons this was failing. Thanks!
      singulars
      1. PO
      1. USCasey
 

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