Skip to content

Commit 7c8bb1d

Browse files
author
Alexandre Dutra
committed
Fix wrong links in tuple documentation
1 parent 0c8be03 commit 7c8bb1d

1 file changed

Lines changed: 7 additions & 7 deletions

File tree

‎manual/tuples/README.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -14,8 +14,8 @@ CREATE TABLE ks.collect_things (
1414

1515
### Fetching Tuples from Rows results
1616

17-
The DataStax Java driver exposes a special [TupleValue] class to handle such columns.
18-
[TupleValue] exposes getters allowing to extract from the tuple all the data types
17+
The DataStax Java driver exposes a special [`TupleValue`][TupleValue] class to handle such columns.
18+
[`TupleValue`][TupleValue] exposes getters allowing to extract from the tuple all the data types
1919
supported by Cassandra:
2020

2121
```java
@@ -33,7 +33,7 @@ Float thirdValueInTuple = tupleValue.getFloat(2);
3333
### Using tuples as statement parameters
3434

3535
A prepared statement may contain a Tuple as a query parameter. In such cases, users
36-
will need to create or gather a [TupleType] first, in order to be able to create a [TupleValue]
36+
will need to create or gather a [`TupleType`][TupleType] first, in order to be able to create a [`TupleValue`][TupleValue]
3737
to bind:
3838

3939
```java
@@ -50,12 +50,12 @@ bs.setTupleValue("v", tupleType.newValue(1, "hello", 2.3f));
5050
session.execute(bs);
5151
```
5252

53-
The method [newValue(Object...)][newValueVararg] follows the same rules as `new SimpleStatement(String, Object...)`,
53+
The method [`newValue(Object...)`][newValueVararg] follows the same rules as `new SimpleStatement(String, Object...)`;
5454
there can be ambiguities due to the fact that the driver will infer the data types from the values
5555
given in parameters of the method, whereas the data types required may differ (numeric
5656
literals are always interpreted as `int`).
5757

58-
To avoid such ambiguities, a [TupleValue] returned by [newValue()][newValue] also exposes specific
58+
To avoid such ambiguities, a [`TupleValue`][TupleValue] returned by [`newValue()`][newValue] also exposes specific
5959
setters for all the existing Cassandra data types:
6060

6161
```java
@@ -83,7 +83,7 @@ session.execute(bs);
8383

8484
More generally, the `IN` keyword in a `SELECT` query will be used to define a *list* of
8585
desired values of the filtered clustering keys, those would simply be bound as a list of
86-
[TupleValue] with the Java driver:
86+
[`TupleValue`][TupleValue] with the Java driver:
8787

8888
```java
8989
TupleType oneTimeUsageTuple = cluster.getMetadata().newTupleType(DataType.text(), DataType.text());
@@ -98,5 +98,5 @@ session.execute(bs);
9898

9999
[TupleType]: http://docs.datastax.com/en/drivers/java/3.2/com/datastax/driver/core/TupleType.html
100100
[TupleValue]: http://docs.datastax.com/en/drivers/java/3.2/com/datastax/driver/core/TupleValue.html
101-
[GettableByIndexData]: http://docs.datastax.com/en/drivers/java/3.2/com/datastax/driver/core/GettableByIndexData.html[newValueVararg]: http://docs.datastax.com/en/drivers/java/3.2/com/datastax/driver/core/TupleType.html#newValue-java.lang.Object...-
101+
[newValueVararg]: http://docs.datastax.com/en/drivers/java/3.2/com/datastax/driver/core/TupleType.html#newValue-java.lang.Object...-
102102
[newValue]: http://docs.datastax.com/en/drivers/java/3.2/com/datastax/driver/core/TupleType.html#newValue--

0 commit comments

Comments
 (0)