Hi, > - I still think your feature comparison is very biased (H2 has more > drawbacks than listed)
Suggestions are welcome. I will add "windowing functions" as suggested elsewhere. I'm behind replying to emails, so it takes time, sorry. > and incomplete (at least Firebird should also > be there). But maybe, that's just because I treat my 11 RDBMS > equally :-) I believe SQLite would be more important than Firebird. But adding 11 RDBMS is simply too much to handle for me. > - Maybe the menu from the cheat sheet is missing? The cheat sheet is meant for printing, that's why there is no navigation. > - Add CSS cursor: pointer to the new (very useful) goTop arrow (when > it is visible) Fixed. > - 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? > - The tutorial is missing a section: how to use H2 with jOOQ ;-) Could you write a paragraph? > - A nice idea about the performance benchmark would be to show the > evolution, like jquery does. That way, users have a higher incentive > to upgrade. Scroll down a bit on this page to see what I mean: > http://blog.jquery.com/2011/05/03/jquery-16-released/ The performance of H2 rarely changes much (this is verified here: http://www.h2database.com/automated/news.xml). > - Speaking of performance, a side-note, how do you profile H2? Did you > know that Yourkit gives free licenses to OSS? Yourkit has become > really awesome. In any case, I'm missing some documentation about how > you guarantee to be and remain the fastest, as you claim. Right now, > this looks like a one-time benchmark. You might have some performance- > regression tests worth publishing? > http://yourkit.com/purchase/index.jsp I did use YourKit, but it's a bit a pain (license upgrade, configuration, how to start/stop profiling within an application?). Now I use the built-in profiler (org.h2.util.Profiler). > - What I think might be great is a demo-database, just like phpMyAdmin > has. Since you have both a flexible database that is easy to reset at > night, and a very nice console (compliments on that one, too!), that > might convince even more users to use H2. Also, such a public database > is nice to have when quickly testing some syntax or other feature when > I don't want to use my own DB. I don't know if this will simple to > achieve without concurrent session support, though... maybe by setting > up 20 demo databases? > http://demo.phpmyadmin.net/ I don't have Java web hosting so far. > - I personally think, you should make more use of your google issue > tracker. The changelog is nice, but sometimes it's also interesting to > see some details about a specific change. With a link to an issue, you > could more easily track discussions (also from the user group): > http://www.h2database.com/html/changelog.html 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. > - 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. > The Apache projects have that already integrated in JIRA (e.g. Derby). I don't like JIRA because it's simply too slow for my taste. I know JIRA, and I use it myself (Apache Jackrabbit). > Do your site-building tools have the same > license as the rest of H2? Currently, yes, but I don't have a problem using a different license (such as Apache) in most cases. > I wouldn't have a problem to give credits > to the H2 site-building tools, should I actually use them for my own > page. Just to get it right... What you could do is use add them to your source repository, but keep the license headers. Regards, Thomas -- 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.
