On Apr 9, 3:04 pm, Thomas Mueller <[email protected]> wrote: > > require keywords to be all uppercase, so you could use any lowercase or camelcase word as an identifier. > > I don't think I want to support this. First of all, it would no longer > be SQL or compatible with any database.
Sure, but it's compatible with Java as it allows to use any table/column name for things conforming to Java coding conventions. Moreover, it can be used as a consistency check for your SQL coding style. > Then, it would look kind of > ugly: > > SELECT id, name FROM test; > > If at all, I would like to "enforce" lowercase keywords: > > select Id, Name from Test; Actually, the latter looks very ugly to me and the former is the way I always use. But this is just matter of style. What I really want is to enforce a consistent use. So the setting CASE_SENSITIVE_KEYWORDS=TRUE would be enough without specifying the case: Both your and mine preferred style would work, but SELECT id, name from test; would not since it's mixed case. Nor would "Select" work, but I don't think anybody prefers camel case for SQL keywords. > But I'm not sure about that. Enforcing keyword case is not compatible > with any other database I know. Someone must be the first. :D > I'm thinking about switching the documentation to use lowercase > keywords, but that would be a bigger change. Even in the SQLite > documentation everything is uppercase. I wouldn't do it... it's a lot of work and I see no gain. > > we'll send it to Thomas as one larger patch. > > I actually prefer smaller patches. I think it's possible to split it > into multiple smaller patches. I just meant to aggregate it into one meaningfull patch - or more patches, whatever makes more sense. > But I guess it's easier if I implement it myself. That's quite possible, the Parser is a big beast. -- 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.
