Skip to content
  1. Aug 20, 2014
  2. Aug 08, 2014
  3. Aug 06, 2014
  4. Aug 05, 2014
  5. Jul 10, 2014
  6. Jul 04, 2014
  7. Jul 03, 2014
  8. Jun 27, 2014
  9. Jun 26, 2014
  10. Jun 25, 2014
  11. Jun 24, 2014
  12. May 28, 2014
  13. Apr 15, 2014
  14. Apr 11, 2014
  15. Apr 10, 2014
  16. Apr 09, 2014
  17. Apr 04, 2014
    • gmantele's avatar
      TAP: Fix incorrect XML format: the INFO for PROVIDER was not ended properly =>... · 33b4623b
      gmantele authored
      TAP: Fix incorrect XML format: the INFO for PROVIDER was not ended properly => an error was raised by TOPCAT when a Java error was occuring in TAP or in a query execution.
      33b4623b
    • 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
    • gmantele's avatar
      ADQL: 2 BIG BUGS fixed in TextualSearchList: · 2c18b1b3
      gmantele authored
      (1) Missing contains(Object) function. Without this function, any ArrayList function like retainAll(...) did not work properly: the research in the collection was made with a bad key. KeyExtractor was not used.
      (2) Result of a research (function get(...)) must return a copy of the result, since the result is an ArrayList, value of the HashMap used for research. If a copy is not returned, any modification (and particularly remove(...)) can be made on the value of the index (HashMap) used for the research.
      2c18b1b3