I am using git/github, but I don't think it's worth setting up a common repo as I personally won't have much time to look at this any time soon.
If you really think the changes are that simple though, by all means go ahead and see if you can get it working. CS_ as a prefix was very confusing to me-- when I first saw it all I could think of was Computer Science. On Apr 4, 7:33 pm, Maaartin <[email protected]> wrote: > 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. > > > 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 see, there's already a setting DATABASE_TO_UPPER (default=true), > which works like a negated version of CASE_SENSITIVE_NAMES. It allows > things like tables with names differing in casing only, however for me > it's not clean from the Javadoc. -- 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.
