2013/6/24 Roger Thomas <[email protected]> > On Sunday, June 23, 2013 9:34:34 AM UTC+1, Lukas Eder wrote: >> >> 2013/6/23 Lukas Eder <[email protected]> >> >>> 2013/6/23 Roger Thomas <[email protected]> >>> >>> I have to say, if you were to change things to get around reserved >>>> words I would vote for d (all-uppercase). >>>> >>>> The logic is no more than - this seems to be the way people have/do >>>> write SQL queries. I can't say its part of any standard, but it does seem >>>> to be the convention and its one I've been following for rather to many >>>> years. It maybe just because I and SQL come from an age when uppercase was >>>> use in languages such as Informix 4GL :) >>>> >>> >>> .... and FORTRAN, COBOL, BASIC, I remember those days. Pascal and C >>> really messed up our upper / lower casing universe! ;-) >>> >>> It's odd, but I think Informix was mixed case, its just SQL was by >> convention uppercase. Having looked around a bit the old embedded SQL in C >> and SQLJ also followed this convention of SQL reserved words being upper >> case in a mixed case world. Its odd how such a hangover from the 80s can >> still be a strong convention now. >> > (hmm, I wrote this? :-) )
I'm not so sure about the convention. I'm actually used to writing SQL keywords in lower case while identifiers are upper cased. This convention helps visually distinguishing the two. Of course, you could do it the other way round to achieve the same goal. But in most databases, case-insensitive identifiers are actually upper-cased. Anyway, identifier casing is an entirely other story... > I presume to get the different styles of case (current, upper and > camel-case) would involve writting each method in DSL.java 3 times over - > each with the different name and each with it's own java doc. > Yes, something along those lines. Or simply duplicating DSL. Or, duplicating the whole deliverable. Whatever solution is chosen, clearly, a code generator will do the tedious work. I have made good experiences with Xtend, which I'm using to generate the Row1..Row22 and related types. Cheers Lukas -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
