2013/6/24 Roger Thomas <[email protected]> > Yes, "choose" would be much better. Given that "else" is mapped to >> "otherwise", "choose" wouldn't be too bad. This would at least remind of >> XSL or JSTL. Both XSL and JSTL also know "then", so it would at least be >> more consistent. >> >> I guess, a short-term solution would include either "case_" or "choose" >> > > If you are looking to add a nice short-term solution if would say case_ > (and I guess else_) as both of these use the correct SQL verb and would > both operate correctly in an IDE lookahead editor. >
I'm also inclined towards these, even if they're a bit ugly. But *if* the ALL_UPPER_CASE() API is added, then suffixing is the only option for the camelCase() API for API consistency and predictability between the two. And adding them now would prevent deprecating decode() *and* choose() in a later release. -- 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.
