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. I think that would be easier on the eyes too. For now I'll just have to be content with placing quotes around every column name and table name, everywhere.
On Apr 3, 10:49 am, Maaartin <[email protected]> wrote: > On Apr 2, 10:06 pm, Arthur Blake <[email protected]> wrote: > > > I would like to see a setting or mode in h2 where table names and > > column names are always completely case sensitive (whether quoted or > > not.) > > So would I. Additionally, It'd be nice to require keywords to be all > uppercase, so you could use any lowercase or camelcase word as an > identifier. > > > It would be very nice when working tightly with C family based > > languages (including Java and Javascript of couse.) Yes it goes > > against the long tradition of case insensitivity in the SQL standards > > and various RDBMS's. But why don't we innovate here a little bit and > > make something better? Better is subjective of course, but I think > > it's more expressive and ultimately more useful. > > It helps to keep the code clean, avoiding mixtures of "password" and > "passWord" (and "SELECT" and "select") and similar inconsistencies so > common in case-insensitive languages. IMHO, it shouldn't be a mode, > since the compatibility modes influence many other things which could > be combined with the case-sensitivity, too. So I'd propose a separate > setting. -- 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.
