Hi Matthias, Thank you very much for your very interesting questions. I will comment inline:
On Fri, Aug 30, 2019 at 10:12 PM Matthias Kurz <[email protected]> wrote: > - Is the procedural language API included in your cheapest commercial > offering, the "Express" edition? > Yes it is part of the Express Edition, which you may use with PostgreSQL (among the other RDBMS listed below) with up to 3 licenses: https://www.jooq.org/legal/licensing#databases > Meaning, if I want to make use of _all_ jOOQ's new, advanced commercial > features, is it enough to purchase the Express edition (even though I use > Postgres and won't use any database offered by the Express edition)? > In the future, there will be further functional differences between the editions, but we haven't designed this part of our roadmap in detail yet, so with jOOQ 3.12, the main difference between the commercial distributions, functionality wise, are: - Commercial RDBMS support - JDK version support (Only the jOOQ 3.12 Enterprise Edition still supports Java 6 / 7) There are also differences in terms of SLA. > Will the only distinction between the different jOOQ _commercial_ editions > be the number of database products each _commercial_ edition supports? Or > will you start to offer some commercial features e.g. only starting with > "Professional", holding them back for "Express" users? > In the future, some commercial features will be offered to Enterprise Edition customers only. There might also be Professional Edition only features. We will soon publish a roadmap of the things we intend to implement in the next few minor releases, and what editions will get access to them. Most features (as always) will be available in all editions, including the jOOQ Open Source Edition. Some very advanced features will be reserved to commercial distributions. > Further: Do you plan a (maybe cheaper than "Express") option to purchase > only the commercial features? > We're not planning to introduce any additional low end price plans as the Express Edition is already very low priced, and we already have quite a few price plans - adding more price plans would complicate the decision process for customers, without adding significant value. - When you talk about "row level security" - do you mean actually rls on > database level (like > https://www.postgresql.org/docs/11/ddl-rowsecurity.html)? Or do you talk > about "row level security" in a sense that jOOQ just adds "WHERE user_id = > xxx" to each query? > No, jOOQ cannot implement such a feature on the database level. You could, of course, but jOOQ doesn't manage your schema for you, or make any assumptions about your schema. Nevertheless, if all queries pass by jOOQ (including parsed ones), then we can implement row level security and similar features by transforming all SQL in jOOQ. Many users already do this with today's VisitListener, but that's very difficult and error prone. Please let me know if you have any further questions, and I will be very happy to assist you. Best Regards, Lukas -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/CAB4ELO7mQED25p%2BniVpq1O3kc5B_FjmUbMCxXa_qSYAUx3f2jA%40mail.gmail.com.
