On Jun 12, 2014, at 5:06 PM, Jacques Nadeau <[email protected]> wrote:
> It seems like the right approach is to create a new subclass of > SqlSpecialOperator. What do I have to do to make sure this doesn't cause > other problems? The subclass already exists - SqlOrderBy.Operator. Needs to override createCall, as SqlSelectOperator does. Julian
