On Apr 4, 3:57 am, Arthur Blake <[email protected]> wrote: > I agree, a setting would be better. > I also agree that when this setting is used, the keywords should also > be case sensitive, although I think all lowercase would be a better > choice, to be consistent with java.
It's consistent with the Java keywords casing, but not with Java identifier conventions: The only Java identifiers written in all uppercase are constants and enum names. Neither of them needs ever be used as identifier in a DB. There may be a class with a field "from", so you may want to use "from" as a column name. For a constant or enum member "FROM" you need no DB identifier. > I think that would be easier on the eyes too. Surely, it's easier to type. So we'd need two options: - CS_NAMES=TRUE/FALSE for case-sensitive identifiers - CS_KEYWORDS=UPPER/LOWER/NO for case-sensitive keywords The two options could be completely independent. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
