Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
V
vollt
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Sonia Zorba
vollt
Commits
e10cca67
Commit
e10cca67
authored
10 years ago
by
gmantele
Browse files
Options
Downloads
Patches
Plain Diff
[TAP] Update Javadoc of ServiceConnection
parent
98cd4408
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
src/tap/ServiceConnection.java
+5
-5
5 additions, 5 deletions
src/tap/ServiceConnection.java
with
5 additions
and
5 deletions
src/tap/ServiceConnection.java
+
5
−
5
View file @
e10cca67
...
...
@@ -42,7 +42,7 @@ import adql.db.FunctionDef;
* </p>
*
* @author Grégory Mantelet (CDS;ARI)
* @version 2.0 (1
2
/201
4
)
* @version 2.0 (
0
1/201
5
)
*/
public
interface
ServiceConnection
{
...
...
@@ -204,7 +204,8 @@ public interface ServiceConnection {
* </ul>
*
* <p><i><b>Important note:</b>
* To save performances, it is strongly recommended to use ROWS limit rather than in bytes. Indeed, the rows limit can be taken
* Currently, the default implementations of the library is only able to deal with output limits in ROWS.<br/>
* Anyway, in order to save performances, it is strongly recommended to use ROWS limit rather than in bytes. Indeed, the rows limit can be taken
* into account at the effective execution of the query (so before getting the result), on the contrary of the bytes limit which
* will be applied on the query result.
* </i></p>
...
...
@@ -228,7 +229,8 @@ public interface ServiceConnection {
* </ul>
*
* <p><i><b>Important note:</b>
* To save performances, it is strongly recommended to use ROWS limit rather than in bytes. Indeed, the rows limit can be taken
* Currently, the default implementations of the library is only able to deal with output limits in ROWS.<br/>
* Anyway, in order to save performances, it is strongly recommended to use ROWS limit rather than in bytes. Indeed, the rows limit can be taken
* into account at the effective execution of the query (so before getting the result), on the contrary of the bytes limit which
* will be applied on the query result.
* </i></p>
...
...
@@ -392,8 +394,6 @@ public interface ServiceConnection {
*
* @return NULL to allow ALL coordinate systems, an empty list to allow NO coordinate system,
* or a list of coordinate system patterns otherwise.
*
* @since 2.0
*/
public
Collection
<
String
>
getCoordinateSystems
();
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment