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  
One other option is to have a flag paired with it or have a complex object to encapsulate pair of limit and offset values, where both are required for the object.  Then can just check if the object is passed as an arg or not.


----- 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) {
> 
> True that autobox bug is very tricky, that worry came to my mind as well when
> I wrote this snippet but I thought using a special number as a value, like
> negative  numbers, to represent when the value is not specified but maybe
> for a database implementation could consider this value as valid, in the
> earlier example, if -1 was specified it would take the last row and then the
> first until reaching the limit. Well, as we can create specific
> implementation classes, we can change this code to whatever we think is
> better now. What is you suggestion? A flag like Long.MIN_VALUE, for
> instance)
> 
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/lightblue-platform/lightblue-rdbms/pull/9/files#r17375725