On Apr 4, 9:31 pm, Arthur Blake <[email protected]> wrote: > 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.
So is mine. I want a clean code, without any mixed case garbage, so I want to switch it all at once. > 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?) Actually, for me CS is (nearly) as clear as CASE_SENSITIVE, but agreed, verbosity has no disadvantage here. > 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. I've already started, but haven't done much. However, I don't think there's much to do, replacing a couple of case-insensitive comparisons by case-sensitive ones and writing a couple of tests should do the job. Are you using git? If yes, should we create a common repo? If no, I'd prefer to just exchange small patches. When everything works fine, we'll send it to Thomas as one larger patch. -- 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.
