Yes, I agree having two options is even better as then we can all have it set up exactly the way we want it.
Should there also be an option for alias names (stored procs), triggers, functions, etc. or would they follow the CS_NAMES setting? My vote is yes it should just be one setting. How about calling the options CASE_SENSITIVE_NAMES and CASE_SENSITIVE_KEYWORDS to be explicit (presumably you would only issue the options at db or connection creation time on the URL, right?) I have a feeling this feature request won't make it's way into the code anytime soon as there doesn't seem to be much demand for it-- and it's not very high priority. That is, unless one of us can supply a very high quality patch complete with test cases. Maybe if I get the time I'll work on it. On Apr 4, 7:28 am, Maaartin <[email protected]> wrote: > 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.
