Skip to content
  • gmantele's avatar
    [ADQL] Fix the parsing and translation of a concatenation expression. · e4f38c95
    gmantele authored
    * The parsing did not allow unsigned numerics and SQL SET functions as
      specified in the ADQL 2.0 grammar
    
    * It was even forbidden to put a column whose the type is not String.
    
    * The translation of a concatenation expression was always prefixed by the
      ADQLList's name: CONCAT_STR. Of course, no database likes that...
    
    Regarding this last point, this commit fixes the GitHub issue #54
    e4f38c95