<p>The translator to use in order to translate ADQL to a SQL compatible with the used DBMS and its spatial extension.</p>
<p>The translator to use in order to translate ADQL to a SQL compatible with the
<p>The TAP library supports only Postgresql (no spatial extension), PostgreSQL+PgSphere, SQLServer (no spatial extension) and MySQL (no spatial extension) for the moment. But you can provide your own SQL translator
used DBMS and its spatial extension.</p>
(even if it does not have spatial features), by providing the name of a class (within brackets: {...}) that implements ADQLTranslator and which have at least an empty constructor.</p>
<p>The TAP library supports only Postgresql (no spatial extension),
PostgreSQL+PgSphere, SQLServer (no spatial extension), MySQL (no spatial
extension) and H2 (no spatial extension) for the moment. But you can provide
your own SQL translator (even if it does not have spatial features), by
providing the name of a class (within brackets: {...}) that implements
ADQLTranslator (for instance: {apackage.MyADQLTranslator}) and which have at