Figure out what to do about case mapping

[cashapp]

Figure out what to do about case mapping

[JakeWharton]

Repurposing this method as a general WTF do we want to do about case mapping. Currently there's a bunch of weird rules and un-encoded conventions.

• Sqlite wants lower_snake columns which gets converted to camelCase for methods and parameter names as well as UPPER_SNAKE for constants.
• Named queries are currently camelCase by convention which get turned into UPPER_SNAKE for constants

We should figure out hard rules which minimize the potential for ambiguity and surprise.

[AlecKazakova]

it would certainly clean up a lot of code to not worry about casing...also I wouldn't have to depend on guava for CaseFormat which would make the gradle plugin a lot smaller.

[JakeWharton]

• Tables, columns, and named queries will be lower_snake
• Java method names will be named the same as their columns (lower_snake)
• Java constant names will be toUpperCase(Locale.US) from their column names
• Mappers will be switched to per-type, not per-column, and be named the same as the class name with "Mapper" appended.