*4. Generator strategies*
>
>
> Most customisation is about naming style. Do you want your database
> objects in PascalCase? camelCase? UPPER_CASE? lower_case?
>
> Is this feature sufficient? What's missing here?
>
> I know it was raised a year or two back, but it would be nice to be able
to write
create.SELECT (AUTHOR.FIRST_NAME, AUTHOR.LAST_NAME, count())
.FROM (AUTHOR)
.JOIN (BOOK).ON(AUTHOR.ID.equal(BOOK.AUTHOR_ID))
.WHERE (BOOK.LANGUAGE.eq("DE"))
.AND (BOOK.PUBLISHED.gt(date("2008-01-01")))
.GROUP_BY (AUTHOR.FIRST_NAME, AUTHOR.LAST_NAME)
.HAVING (count().gt(5))
.ORDER_BY (AUTHOR.LAST_NAME.asc().nullsFirst())
.LIMIT (2)
.OFFSET (1)
I know its not very Java like, but uppercase is still the SQL way of writing
statements. Also _ for spaces is clear than medial capitals (camelCase) if we
are able to step away from Java 'standards'.
My use of JOOQ is still very much that of a DBA doing some coding and so I
would like the mapping between SQL scripts and Java code to be as near as
possible.
(The spacing is just how I pad out SQL statements as it works for me)
--
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].
For more options, visit https://groups.google.com/d/optout.
