Do you really need support?
Our apologies. We hadn’t realised that we didn’t advertise the support-free jOOQ licenses, which we had been offering for quite a while now well enough on our website. So we have fixed that now.
We think that jOOQ is such a high quality, intuitive piece of software with a vibrant community that our customers might not even need us at Data Geekery to support them! That is why we have been offering support-less subscriptions where customers get to use the jOOQ Professional Edition or the jOOQ Enterprise Edition for 20% less than if they had our guaranteed reaction times.
All you need to do is enter the “NO SUPPORT” discount code with your next purchase, and start coding. More details here. Note that this will only remove our support guarantees, not the warranty. All upgrades and bugfixes are still included.
And while we’re at it, if you’re planning on purchasing 10 licenses or more, please contact us to learn about our high-volume tiered pricing model to further increase the value you’re getting out of jOOQ.
One year ago, on August 15 2013, Data Geekery GmbH was founded to provide commercial licensing and support for jOOQ. We’ve had exciting times behind us, and even more exciting times ahead of us. Here’s a quick wrap-up of what happend in the last year:
- 2013-08-15: Data Geekery enters the Zurich trade register
- 2013-10-09: jOOQ 3.2 is released under the new dual licensing strategy
- 2013-10-29: jOOQ gets roughly 10% votes on this InfoQ poll
- 2013-12-18: We’re having the 8th conference or JUG talk about jOOQ
- 2014-12-31: Data Geekery is profitable. A Happy New Year, indeed!
- 2014-01-01: Our monthly downloads have recovered from dual licensing
- 2014-01-17: Our articles reach 1M reads on DZone
- 2014-02-14: jOOQ 3.3 is released with Keyset pagination support
- 2014-02-19: The 200th Stack Overflow question about jOOQ was asked
- 2014-05-21: jOOQ is referenced from the RebelLabs reports
- 2014-06-12: We’re having the 21st conference or JUG talk about jOOQ
- 2014-06-20: jOOQ 3.4 is released with CTE, transactions, and DDL support
- 2014-06-23: The 500th GitHub Star was added
- 2014-07-01: Our monthly downloads have doubled compared to last year
- 2014-08-08: The 400th blog post was published bringing the 650’000th hit
So, what’s next?
jOOQ is a big success story. Many minor frameworks by other “data geeks” copy jOOQ’s approach to writing internal domain-specific languages for a subset of SQL or of another query language. Examples are:
Being the industry’s leading type safe embedded SQL API, we’re going to continue pushing embedded SQL in Java, and SQL in general. Stay tuned for a very exciting second year of Data Geekery!
Our customers, users, and followers are sharing their love for jOOQ with the world and we can hardly catch up with them! Here are:
- Sean Cassidy, who agrees that in the long run, SQL win beat ORM for explicitness and statelessness.
- Petri Kainulainen, who has unlocked an achievement by paginating his query results using the jOOQ SEEK clause.
- Christoph Henkelmann, who doesn’t want God to kill kittens. Yes, Christoph. We should all think a bit more about the kittens.
Thanks for the shouts, guys! You make the jOOQ experience rock!
COUNT(*) seems to be a practical way for many SQL developers to ensure that there is exactly one result record. No more, no less. But often, if you want exactly one record, you can achieve the same thing using a
CASE expression along with an
EXISTS predicate, which is likely to be much faster than the
COUNT(*) alternative, because you probably don’t care about the exact number of records, only about the existence of such records.
Does that sound too abstract? Read this article here, and decide for yourself, if you find potential for optimisation in your code.
If you’re using Oracle or SQL Server (or another standards-compliant database), you can put constraints (“CHECK OPTIONS”) on your database views. This can be extremely useful when you want to prevent users from inserting data into views that don’t match the view itself. Take this view for instance:
CREATE VIEW expensive_books AS SELECT id, title, price FROM books WHERE price > 100 WITH CHECK OPTION;
This view will not allow you to insert any books with a price lower than 100, because of the CHECK OPTION. An incredibly useful feature that will also be supported by the upcoming jOOQ 3.5.
Read this blog post for more information.
After a summer break, we’re back on the road!
Have you missed any of our previous jOOQ talks? Soon you’ll get another chance to hear us talk about jOOQ or SQL in general in any of these upcoming events:
- Sept 9-11, 2014: JavaZone in Oslo, Norway (English, about SQL)
- Sept 28-Oct 02, 2014: JavaOne in San Francisco, USA (English, about jOOQ)
- Oct 23, 2014: Soft-Shake in Gemeva, Switzerland (English, about jOOQ)
- Oct 24, 2014: GeeCON CZ in Prague, Czech Republic (English, about SQL)
- Oct 25, 2014: Firebird Conference in Prague, Czech Republic (English, about Java 8, Hibernate, and jOOQ – talk by Mark Rotteveel, the Jaybird developer)
Stay informed about 2014 events on www.jooq.org/news.