On the other hand, most RDBMS do have BOOLEAN types, so I don't see why any of TINYINT(1), INT(1), CHAR(1), etc should be used instead. For compatibility reasons with Oracle?
MySQL have, but only as a synonym to TINYINT(1) generator.mapping.types. BOOLEAN=^schemaName\.\w+\.visible$,^schemaName\.\w+\.\w+ed$ generator.mapping.types.BINARY=data This is for mapping column names to types. Good idea. But does Oracle have type domains? One can create a domain MYBOOL, which is actually type TINYINT(1) to use it across huge database. In this case name mapping is ineffective, I think, because there can be like 100 different MYBOOL fields in database. This is where type name mapping is more effective, I think. Column name mapping is a good thing, if a database is designed in a way, where you can always tell column type from it's name. But I think this is not always the case, I think. More, may be this is almost never the case. Note, that both org.jooq.Record and org.jooq.Result provide means for converting any data to BOOLEAN: Thanks, this is a good way. I will use it now.
