-
Deprecated Classes
-
Deprecated FieldsFieldDescriptionSince v2.0, supported coordinate systems must be declared in ADQLParser.Since v2.0, supported geometrical functions must be declared in ADQLParser.Since v2.0, supported coordinate systems must be declared in ADQLParser.Since ADQL-2.1.
-
Deprecated MethodsMethodDescriptionSince 2.0, the validation of coordinate systems is performed automatically by
ADQLParser
.Since 2.0, the validation of coordinate systems is performed automatically byADQLParser
.Since 2.0, validation of the geometric functions is performed automatically byADQLParser
. Geometric functions are optional features and should be declared as such in theADQLParser
if they are supported (seeADQLParser.getSupportedFeatures()
).Since 2.0, validation of the geometric functions is performed automatically byADQLParser
. Geometric functions are optional features and should be declared as such in theADQLParser
if they are supported (seeADQLParser.getSupportedFeatures()
).Since 2.0, the validation of REGIONs is performed automatically byADQLParser
.Since v2.0, the parameter 'mapTables' is no more used. You should usedDBChecker.resolveColumns(ADQLQuery, Stack, UnresolvedIdentifiersException)
instead.Since 2.0, the validation of coordinate systems is performed automatically byADQLParser
.Since 2.0, validation of the geometric functions is performed automatically byADQLParser
. Geometric functions are optional features and should be declared as such in theADQLParser
if they are supported (seeADQLParser.getSupportedFeatures()
).Since 2.0, the validation of STCs expressions is performed automatically byADQLParser
.Since v2.0, this tool function is no longer used. It was useful only to collect allowed geometries and coordinate systems....but these are now checked byADQLParser
.Since v2.0, the table name is not any more split automatically. So, it is not any more needed to join all its parts.Since v2.0, the table name is not any more split automatically.Since 2.0, prefer to use directlyADQLQueryFactory.createDistance(GeometryFunction, GeometryFunction)
since 1.4 ; Replaced byADQLQueryFactory.createOrder(int, boolean)
Since 2.0, a column reference can be a qualified column (i.e. anADQLColumn
). You should useADQLQueryFactory.createOrder(ADQLOperand, boolean)
instead.since 1.4 ; Former version's mistake: an ORDER BY item is either a regular/delimited column name or an integer, not a qualified column name ; Replaced byADQLQueryFactory.createOrder(adql.parser.IdentifierItems.IdentifierItem, boolean)
; This function is no longer used by ADQLParser.Since v2.0,ADQLQueryFactory.createQuery(ADQLVersion)
must be used/extended instead.Since ADQL-2.1, a column reference can be a qualified column (i.e. anADQLColumn
). You should useADQLOrder.setOrder(ADQLOperand, boolean)
instead.Since v2.0. This function is never used.Since v2.0. This piece of information is never used.Since v2.0. This function is never used.Since v2.0. This piece of information is never used.Since ADQL-2.1.Since ADQL-2.1.
-
Deprecated ConstructorsConstructorDescriptionSince v2.0, the check of geometrical functions support is performed in ADQLParser. It must now be done with
ADQLParser.getSupportedFeatures()
(see alsoFeatureSet
).Since v2.0, the check of geometrical functions support is performed in ADQLParser. It must now be done withADQLParser.getSupportedFeatures()
(see alsoFeatureSet
).Since ADQL-2.1, a column reference can be a qualified column (i.e. anADQLColumn
). You should useADQLOrder(ADQLOperand)
instead.Since ADQL-2.1, the coordinate system argument is deprecated.
UserDefinedFunction
instead.