Skip to content
Snippets Groups Projects
  1. Jan 29, 2016
  2. Dec 01, 2015
  3. Sep 30, 2015
  4. Sep 01, 2015
    • gmantele's avatar
      [ADQL,TAP] Fix bug (reported by G. Landais) in the understanding of UNKNOWN · 271e03cc
      gmantele authored
      types. The notion of "unknown type" is different in function of the target
      object:
        - a DBType and a FunctionDef have an unknown type if their function
          isUnknown() returns true. In such case, the other functions such as
      	isNumeric/String/Geometry() will return false.
        - an ADQLOperand (e.g. ADQLColumn) does NOT have a isUnknown() function.
          But if the type of the operand is unknown, its functions isNumeric(),
      	isString() and isGeometry() must ALL return true. Otherwise, just one of
      	these functions can return true.
      271e03cc
  5. Aug 27, 2015
    • gmantele's avatar
      [ADQL] Fix a Big Bug reported by M.Taylor and M.Demleitner: in ORDER BY, GROUP... · 13a2dc54
      gmantele authored
      [ADQL] Fix a Big Bug reported by M.Taylor and M.Demleitner: in ORDER BY, GROUP BY and USING only regular and delimited identifiers are accepted, not qualified column names.
      For instance: "SELECT table.column_name FROM table ORDER BY table.column_name" is wrong. We should instead write:
      "SELECT table.column_name FROM table ORDER BY column_name".
      "SELECT table.column_name AS mycol FROM table ORDER BY mycol" is also correct.
      Of course, for ORDER BY and GROUP BY, it is still possible to reference a column using its index in the SELECT clause.
      For instance: "SELECT table.column_name FROM table ORDER BY 1".
      13a2dc54
  6. Aug 25, 2015
    • gmantele's avatar
      [ADQL] Fix a bug reported by M. Taylor about qualified table name: · 84ede4bf
      gmantele authored
      when in a table definition (extension of DBTable) no schema is
      specified, it was possible to prefix the table name by a fake
      schema name ; it was checked at all:
      e.g. "SELECT * FROM no_schema.foo".
      This is no longer possible: if no schema is specified, no schema
      must be used in an ADQL query. But if one is specified, the schema
      prefix is optional.
      84ede4bf
  7. Aug 03, 2015
    • gmantele's avatar
      [ADQL,TAP] Fix 2 bugs notified by M.Taylor: · b49f8160
      gmantele authored
      1/ Bad parsing of UDF's parameter type or return type. Database types whose the
      name has a space (e.g. 'double precision') were not accepted. These type names
      should be accepted according to TAPRegExt.
      2/ An error message thrown by the DBChecker has been modified for the cases
      the type of a parameter is unknown. Before the returned type was NUMERIC. Now,
      it will be 'param' followed by the parameter index (e.g. 'param1').
      b49f8160
  8. Jul 20, 2015
  9. Jun 16, 2015
  10. Jun 09, 2015
  11. Jun 08, 2015
  12. May 19, 2015
    • Mark Taylor's avatar
      replace references to since-J2SE6 methods in ADQL lib · 6f8ff70a
      Mark Taylor authored
      Replace uses of String.isEmpty and Arrays.copyOf methods
      (both introduced in java 6) with equivalent code that makes
      use of only methods available in the java 5 runtime.
      This allows the ADQL library, if cross-compiled for java 5,
      to run without errors on a java 5 runtime.
      6f8ff70a
  13. May 04, 2015
  14. Apr 22, 2015
  15. Feb 11, 2015
  16. Feb 10, 2015
  17. Feb 06, 2015
  18. Dec 09, 2014
  19. Dec 05, 2014
  20. Nov 05, 2014
    • gmantele's avatar
      [ADQL,TAP] Add geometry format in output and correct upload of STC-S regions.... · 6f607bc6
      gmantele authored
      [ADQL,TAP] Add geometry format in output and correct upload of STC-S regions. Geometrical type conversion from and into a DB type is now required in all JDBCTranslator. This allows formatting of geometrical column value coming from the database, but also the translation of STC-S expressions provided in uploaded table into geometrical column values.
      6f607bc6
  21. Oct 29, 2014
  22. Oct 28, 2014
    • gmantele's avatar
      [ADQL,TAP] Add STC-S and UDFs support in the ADQL parser. Now, it is possible... · 496e769c
      gmantele authored
      [ADQL,TAP] Add STC-S and UDFs support in the ADQL parser. Now, it is possible to provide a list of allowed UDFs, regions and coordinate systems. The ServiceConnection of TAP is now able to provide these lists and to propagate them to the ADQLExecutor. UDFs and allowed regions are now listed automatically in the /capabilities resource of TAP. The type 'geometry' is now fully supported in ADQL. That's why the new function 'isGeometry()' has been added to all ADQLOperand extensions. Now the DBChecker is also able to check roughly types of columns and UDFs (unknown when parsing syntactically a query). The syntax of STC-S regions (expressed in the REGION function) are now checked by DBChecker. However, for the moment, geometries are not serialized in STC-S in the output....but it should be possible in some way in the next commit(s).
      496e769c
  23. Oct 08, 2014
  24. Oct 01, 2014
  25. Sep 25, 2014
  26. Sep 10, 2014
  27. Sep 09, 2014
  28. Aug 21, 2014
  29. Aug 20, 2014
  30. Aug 08, 2014
  31. Aug 05, 2014
  32. Jul 03, 2014
  33. May 28, 2014
  34. Apr 15, 2014
Loading