Skip to content
Snippets Groups Projects
  1. Mar 05, 2019
  2. Jan 12, 2018
    • 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
  3. Jan 11, 2018
  4. Nov 30, 2017
  5. Sep 11, 2017
  6. Sep 08, 2017
    • gmantele's avatar
      [ADQL] Fix the transformation of NATURAL JOIN and JOIN...USING of MS-SQLServer. · e03e5725
      gmantele authored
      In the resulting SQL query, if there are an alias on the joined tables, these
      aliases must be used in the ON clause (instead of the full table name).
      
      For instance, the following ADQL query:
      
      ```sql
        SELECT *
        FROM tableA AS a NATURAL JOIN tableB AS b;
      ```
      
      should be translated into the following SQL:
      
      ```sql
        SELECT *
        FROM tableA AS a
          INNER JOIN tableB AS b
            ON a.id = b.id
      ```
      
      This commit complete the resolution of the Pull Request #16
      (more details about the issue can be got in there)
      e03e5725
    • gmantele's avatar
      [ADQL] Fix return type of some math. functions for MS-SQLServer. · 73630130
      gmantele authored
      In MS-SQLServer, the following functions return a value of the same
      type as the given argument:
        - abs
        - ceiling
        - degrees
        - floor
        - radians
        - round.
      
      Since ADQL requires that these functions return a DOUBLE
      (i.e. a float in MS-SQLServer), it must be ensured that the given
      argument is a float.
      
      This commit partially fixes the Pull Request #16
      73630130
  7. Aug 02, 2017
    • gmantele's avatar
      [ADQL,TAP] Basic MySQL support. · cf721ff2
      gmantele authored
      On the contrary to other DBMS, MySQL supports schemas, but as databases.
      Which means that JDBCConnection gets from the JDBC driver that MySQL does
      not support schemas and so it tries to access TAP_SCHEMA tables with a
      'TAP_SCHEMA_' prefix instead of 'TAP_SCHEMA.' one. Since MySQL does
      behave like it supports schemas, JDBCConnection.supportsSchema must be
      set to 'true' if the DBMS is MySQL.
      
      Besides, since no schemas are returned by the JDBC driver
      (cf DatabaseMetadata.listSchema(...)), the function
      JDBCConnection.isSchemaExisting(String, DatabaseMetaData) must always assume
      that the specified schema exists if the DBMS is MySQL. This is particularly
      important when the existence of 'TAP_UPLOAD' must be checked, because if the
      function returns 'false' the library will attempt to create the database/schema
      'TAP_UPLOAD' and will obviously fail due to a lack of permissions. Of course,
      it means that the TAP implementor must create manually the schema/database
      'TAP_UPLOAD' him-/her-self.
      
      The second particularity of MySQL is the quote character for identifiers.
      It is a back-quote (`) instead of a double quote ("). To reflect this
      difference, JDBCTranslator.appendIdentifier(...) has been overwritten in a new
      JDBCTranslator extension: MySQLTranslator.
      
      The translation of all SQL types and mathematical functions have been adapted to
      MySQL according to the online documentation. Few tests have been done locally
      with a tiny database. This seems to work but further testing should be
      performed in order to ensure the stability of this implementation.
      cf721ff2
  8. Mar 29, 2017
  9. Feb 24, 2017
  10. Feb 20, 2017
  11. Feb 09, 2017
  12. Oct 12, 2016
  13. Aug 10, 2016
  14. Jul 14, 2016
  15. Jun 08, 2016
  16. Apr 20, 2016
  17. Mar 17, 2016
    • gmantele's avatar
      [ADQL] Add an ADQL translator for MS SQL Server. This particular translator · a2fb29ad
      gmantele authored
      deals with NATURAL JOINs and JOINs using the keyword USING so that being
      supported by SQL Server. Basically, they are translated as a list of ON
      conditions.
      Warning: This translator is just guaranteed to solve the NATURAL and USING
      issue. Support for datatypes conversion and case sensitivity has to be
      reviewed. Besides no geometrical function is translated for SQL Server.
      a2fb29ad
  18. Dec 01, 2015
  19. Sep 30, 2015
  20. Jul 20, 2015
  21. Jun 08, 2015
  22. May 04, 2015
  23. Apr 22, 2015
  24. Feb 11, 2015
  25. Feb 06, 2015
  26. 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
  27. Oct 29, 2014
  28. Oct 08, 2014
  29. Sep 09, 2014
  30. Aug 21, 2014
  31. Aug 05, 2014
  32. Apr 10, 2014
  33. Apr 09, 2014
  34. Apr 04, 2014
    • gmantele's avatar
      ADQL: Completely change/improve Joins management, and particularly NATURAL... · 9acc3d8d
      gmantele authored
      ADQL: Completely change/improve Joins management, and particularly NATURAL JOIN and USING JOIN. Now, every joined columns are represented by a DBCommonColumn instance which has a given table coverage.
      Before, there was a problem while using at least 3 or 4 NATURAL JOINs. Bug raised by Menelaos Perdikeas (ESAC).
      9acc3d8d
  35. Apr 03, 2014
Loading