Wow, this is cool. I sort of "understood" what you were doing to create the SQL BNF in Java, but I didn't realize the complexity of it. I really should have, I do understand how complicated BNF gets from my work, but implementing them by hand in Java...
I find out about more cool tools by being on this mailing list then any other, haha. On Monday, April 1, 2013 2:54:06 PM UTC-4, Lukas Eder wrote: > > Hi Christopher, > > 2013/4/1 Christopher Deckers <[email protected] <javascript:>>: > > Hi Lukas, > > > >> To be sure that we're discussing on a common > >> grounds, I assume that the fluent API building technique, which jOOQ > >> is based on, is known: > >> > http://blog.jooq.org/2012/01/05/the-java-fluent-api-designer-crash-course > > > > > > OK, now we are on common ground, I wasn't completely :) > > > > So, if I am not mistaken, the hierarchy represents the grammar you > > implement. The more complex the grammar, the deeper level of > inheritance. I > > would have to give it a more thorough look to be able to continue that > > discussion though because you seem to have a point in the maintainance > of > > the API. > > Well, I'm at a point where I can say that maintaining it sucks a bit. > So when I have time, I will clearly put some effort in an API > generator - possibly based on Xtext / Xtend. Because I'm not entirely > happy with all the inheritance either and I've had similar feedback to > yours, before. Inline SQL syntax is best described and documented > using a BNF notation, and possibly a tool like H2's railroad diagram > generator (see http://www.h2database.com/jcr/grammar.html). > > But for now, this is as good as it gets... > > 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.
