This has now been implemented. We won't just simply turn on case
insensitivity by default, but we'll allow to specify all regex pattern
flags as specified in java.util.regex.Pattern. By default COMMENTS and
CASE_INSENSITIVE will be turned on in jOOQ 3.6+. If someone wants jOOQ 3.5
behaviour, they can specify to just set the COMMENTS flag to be turned on
and all the other flags stay off.

The new types in jooq-codegen-3.6.0.xsd will look like this:

  <simpleType name="RegexFlags">
    <list itemType="tns:RegexFlag"/>
  </simpleType>

  <simpleType name="RegexFlag">
    <restriction base="string">
      <enumeration value="UNIX_LINES"/>
      <enumeration value="CASE_INSENSITIVE"/>
      <enumeration value="COMMENTS"/>
      <enumeration value="MULTILINE"/>
      <enumeration value="LITERAL"/>
      <enumeration value="DOTALL"/>
      <enumeration value="UNICODE_CASE"/>
      <enumeration value="CANON_EQ"/>
      <enumeration value="UNICODE_CHARACTER_CLASS"/>
    </restriction>
  </simpleType>


Cheers,
Lukas

2014-12-11 9:37 GMT+01:00 Lukas Eder <[email protected]>:
>
>
> 2014-12-11 4:23 GMT+01:00 <[email protected]>:
>
>> I would assume it would be better if the code responsible (within
>> context) for code generation is case insensitive, it might save new users
>> some time.
>>
>
> Yes, it might save new users (or any users) some time, indeed, because
> many DDLs are indeed case-insensitive, and the risk of collisions between
> "COLUMN" and "column" is rather slim. Perhaps we should wrap all regular
> expressions from the code generation configuration in *(?i: ... )* per
> default, and allow users to explicitly specify case-sensitive sections with 
> *(?-i:
> ... )*. Obviously, this behaviour can be turned off again via a new
> configuration flag...
>
> I've registered an issue for this:
> https://github.com/jOOQ/jOOQ/issues/3860
>

-- 
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.

Reply via email to