RDBMS tests and init of the new module

The tests to check some Expressions to SQL statement conversion and started the new module which will provide a tool to generate the RDBMS module configuration by reverse engineering  
The problem I see is not that it won't work, it is that long term it could be broken if someone doesn't realize the potential risk to changing things.  With encapsulation the risk is mitigated.  That is the benefit.  I hate debugging auto-boxing issues..

----- Original Message -----
> > +        if(groupBy != null && groupBy.size() < 0){
> > +            throw Error.get("GroupBy not supported", "no handler");
> > +        }
> > +    }
> > +
> > +    protected void generateOrderBy(SelectStmt s, StringBuilder queryStr,
> > List<String> orderBy) {
> > +        if(orderBy != null && orderBy.size() < 0) {
> > +            queryStr.append("ORDER BY ");
> > +            for (String order : orderBy) {
> > +                queryStr.append(order).append(" ,");
> > +            }
> > +            queryStr.deleteCharAt(queryStr.length() - 1); //remove the
> > last ',
> > +        }
> > +    }
> > +
> > +    protected void generateLimitOffset(SelectStmt s, StringBuilder
> > queryStr, Long limit, Long offset) {
> 
> I dont know, I feel that this would just add (a bit) more complex logic (the
> encapsulation) for almost no advantages, I mean, the two values come from
> the CRUDController interface, so you think we could put them together in
> Range object to move the validation for null to this new class, right ?
> 
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/lightblue-platform/lightblue-rdbms/pull/9/files#r17376384