To create the JaQu jar file, run: <codeclass="notranslate">build jarJaqu</code>. This will create the file <codeclass="notranslate">bin/h2jaqu.jar</code>.
To create the JaQu jar file, run: <code>build jarJaqu</code>. This will create the file <code>bin/h2jaqu.jar</code>.
</p>
<h2>Requirements</h2>
...
...
@@ -88,7 +88,7 @@ work with any database that supports the JDBC API.
</p>
<h2>Example Code</h2>
<preclass="notranslate">
<pre>
package org.h2.test.jaqu;
import java.math.BigDecimal;
import java.util.List;
...
...
@@ -226,10 +226,10 @@ public class Test {
<p>
JaQu does not require any configuration when using the default mapping.
To define table indices, or if you want to map a class to a table with a different name,
or a field to a column with another name, create a function called 'define' in the data class.
or a field to a column with another name, create a function called <code>define</code> in the data class.
Example:
</p>
<preclass="notranslate">
<pre>
public class Product implements Table {
public Integer productId;
...
...
@@ -247,7 +247,7 @@ public class Product implements Table {
}
</pre>
<p>
The method <codeclass="notranslate">define()</code> contains the mapping definition. It is called once
The method <code>define()</code> contains the mapping definition. It is called once
when the class is used for the first time. Like annotations, the mapping is defined in the class itself.
Unlike when using annotations, the compiler can check the syntax even for multi-column
objects (multi-column indexes, multi-column primary keys and so on).
...
...
@@ -262,7 +262,7 @@ To do that, the condition class is de-compiled to a SQL condition.
A proof of concept decompiler is included (but it doesn't work yet).
