Hi Thomas,
> Suggestions are welcome. I will add "windowing functions" as suggested
> elsewhere. I'm behind replying to emails, so it takes time, sorry.
No worries. I see you have had a couple of urgent issues recently...
> > - The tutorial contains a section: "Special H2 Console Syntax". That's
> > very useful, but not documented elsewhere
>
> Why should it be documented in two different places?
My point is, that I wouldn't expect to find this in the tutorial, and
I think it's too important to miss. You could make this a section in
the Reference menu...
> > - The tutorial is missing a section: how to use H2 with jOOQ ;-)
>
> Could you write a paragraph?
Of course!
-----------------------------------------------------------------------
<h2>Using H2 with jOOQ</h2>
jOOQ adds a thin layer on top of JDBC, allowing for type-safe SQL
construction, including advanced SQL, stored procedures and advanced
data types. jOOQ takes your database schema as a base for code
generation. If this is your example schema
<pre class="notranslate">
CREATE TABLE USER (ID INT, NAME VARCHAR(50));
</pre>
...then run the jOOQ code generator on the command line using this
command:
<pre class="notranslate">
java -cp jooq.jar;jooq-meta.jar;jooq-codegen.jar;h2-1.3.158.jar;.
org.jooq.util.GenerationTool /codegen.properties
</pre>
...where codegen.properties contains this information
<pre class="notranslate">
jdbc.Driver=org.h2.Driver
jdbc.URL=jdbc:h2:~/test
jdbc.Schema=PUBLIC
jdbc.User=sa
jdbc.Password=
generator=org.jooq.util.DefaultGenerator
generator.database=org.jooq.util.h2.H2Database
generator.database.includes=.*
generator.database.excludes=
generator.generate.relations=true
generator.target.package=org.jooq.h2.generated
generator.target.directory=./src
</pre>
Using the generated source, code start type-safe querying your
database like this
<pre class="notranslate">
Factory create = new H2Factory(connection);
Result<UserRecord> result =
create.selectFrom(USER)
.where(NAME.like("Johnny%"))
.orderBy(ID)
.fetch();
</pre>
See more details on <a href="http://www.jooq.org";>jOOQ Homepage</a>
and in the <a href="http://sourceforge.net/apps/trac/jooq/wiki/Manual/
META/Configuration">jOOQ Manual</a>
-----------------------------------------------------------------------
> The performance of H2 rarely changes much (this is verified
> here:http://www.h2database.com/automated/news.xml).
Nice, I didn't know about this feed. I thought about performance,
because I had seen issues recently about sub-optimal performance of
certain clauses/constructs. This can be interesting even for very
specific improvements to one SQL clause. But I understand it's more
work....
> Very few people monitor the issue tracker. In many cases, people log
> issues that are in fact not issues but questions. Therefore, always
> using the issue tracker would result in lower quality support at the
> end. Also, it would mean more work as it's more 'paperwork' to manage
> feature requests in two places.
It's up to you. I didn't find that to be much additional work in jOOQ.
Once I have tickets, release notes are very easy to do, and the
discussion can be in the news group or in the tracker. But you have
more requests, so maybe I underestimate that.
> > - A voting feature on the roadmap might be interesting.
>
> Yes, that's true. So far I manually update the roadmap. But, in
> addition to just voting, in many cases I would like to understand the
> actual use case.
Of course
> What you could do is use add them to your source repository, but keep
> the license headers.
I finally decided not to create static HTML. I'm going to use a CMS
such as plone
Thanks for your time!
Lukas
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
