Unverified Commit 66301072 authored by Astrinus's avatar Astrinus Committed by GitHub

Fixed broken links in client.md

parent 6cb7a835
......@@ -110,24 +110,24 @@ statement st = (sql.prepare <<
"insert into numbers(value) values(:val)", use(i));
```
`operator<<` that is a shortcut forwarder to the equivalent operator of the `once` member. Example:
* `operator<<` that is a shortcut forwarder to the equivalent operator of the `once` member. Example:
```cpp
sql << "drop table persons";
```
* `got_data` returns true if the last executed query had non-empty result.
* `get_next_sequence_value` returns true if the next value of the sequence with the specified name was generated and returned in its second argument. Unless you can be sure that your program will use only databases that support sequences, consider using this method in conjunction with `get_last_insert_id()` as explained in ["Working with sequences"](beyond.html#sequences) section.
* `get_next_sequence_value` returns true if the next value of the sequence with the specified name was generated and returned in its second argument. Unless you can be sure that your program will use only databases that support sequences, consider using this method in conjunction with `get_last_insert_id()` as explained in ["Working with sequences"](../beyond.md#sequences) section.
* `get_last_insert_id` returns true if it could retrieve the last value automatically generated by the database for an auto-incremented field. Notice that although this method takes the table name, for some databases, such as Microsoft SQL Server and SQLite, this value is actually global, so you should attempt to retrieve it immediately after performing an insertion.
* `get_query_stream` provides direct access to the stream object that is used to accumulate the query text and exists in particular to allow the user to imbue specific locale to this stream.
* `set_log_stream` and `get_log_stream` functions for setting and getting the current stream object used for basic query logging. By default, it is `NULL`, which means no logging The string value that is actually logged into the stream is one-line verbatim copy of the query string provided by the user, without including any data from the `use` elements. The query is logged exactly once, before the preparation step.
* `get_last_query` retrieves the text of the last used query.
* `uppercase_column_names` allows to force all column names to uppercase in dynamic row description; this function is particularly useful for portability, since various database servers report column names differently (some preserve case, some change it).
* `get_dummy_from_table` and `get_dummy_from_clause()`: helpers for writing portable DML statements, see [DML helpers](statement.html#dml) for more details.
* `get_dummy_from_table` and `get_dummy_from_clause()`: helpers for writing portable DML statements, see [DML helpers](../utilities.md#dml) for more details.
* `get_backend` returns the internal pointer to the concrete backend implementation of the session. This is provided for advanced users that need access to the functionality that is not otherwise available.
* `get_backend_name` is a convenience forwarder to the same function of the backend object.
See [Connections and simple queries](basics.html) for more examples.
See [connection](../connections.md) and [queries](../queries.md) for more examples.
## class connection_parameters
......@@ -230,7 +230,7 @@ int count;
sql << "select count(*) from person", into(count);
```
See [Binding local dat](exchange.html#bind_local) for more examples
See [Binding output data](../binding.md#binding-output-data-into) for more examples
## function use
......@@ -263,7 +263,7 @@ int val = 7;
sql << "insert into numbers(val) values(:val)", use(val);
```
See [Binding local data](exchange.html#bind_local) for more examples.
See [Binding input data](../binding.md#binding-input-data-use) for more examples.
## class statement
......@@ -330,9 +330,9 @@ statement stmt(sql);
* `exchange_for_rowset` as a special case for binding `rowset` objects.
* `get_backend` function that returns the internal pointer to the concrete backend implementation of the statement object. This is provided for advanced users that need access to the functionality that is not otherwise available.
See [Statement preparation and repeated execution](statements.html#preparation) for example uses.
See [Statement preparation and repeated execution](../statements.md) for example uses.
Most of the functions from the `statement` class interface are called automatically, but can be also used explicitly. See [Interfaces](interfaces) for the description of various way to use this interface.
Most of the functions from the `statement` class interface are called automatically, but can be also used explicitly. See [Interfaces](../interfaces.md) for the description of various way to use this interface.
## class procedure
......@@ -352,7 +352,7 @@ public:
The constructor expects the result of using `prepare` on the `session` object.
See [Stored procedures](statements.html#procedures) for examples.
See [Stored procedures](../procedures.md) for examples.
## class type_conversion
......@@ -372,7 +372,7 @@ struct type_conversion
Users are supposed to properly implement the `from_base` and `to_base` functions in their specializations of this template class.
See [Extending SOCI to support custom (user-defined) C++ types](exchange.html#custom_types).
See [Extending SOCI to support custom (user-defined) C++ types](../types.md#user-defined-c-types).
## class row
......@@ -427,7 +427,7 @@ This class contains the following members:
* `operator>>` for convenience stream-like extraction interface. Subsequent calls to this function are equivalent to calling `get` with increasing position parameter, starting from the beginning.
* `skip` and `reset_get_counter` allow to change the order of data extraction for the above operator.
See [Dynamic resultset binding](exchange.html#dynamic) for examples.
See [Dynamic resultset binding](../types.md#dynamic-binding) for examples.
## class column_properties
......@@ -447,7 +447,7 @@ This class contains the following members:
* `get_name` function that returns the name of the column.
* `get_data_type` that returns the type of the column.
See [Dynamic resultset binding](exchange.html#dynamic) for examples.
See [Dynamic resultset binding](../types.md#dynamic-binding) for examples.
## class values
......@@ -498,7 +498,7 @@ This class contains the same members as the `row` class (with the same meaning)
* `set` function for storing values in named columns or in subsequent positions.
* `operator<<` for convenience.
See [Object-relational mapping](exchange.html#object_relational) for examples.
See [Object-relational mapping](../types.md#object-relational-mapping) for examples.
## class blob
......@@ -531,7 +531,7 @@ This class contains the following members:
* `trim` function that truncates the existing data to the new length.
* `get_backend` function that returns the internal pointer to the concrete backend implementation of the BLOB object. This is provided for advanced users that need access to the functionality that is not otherwise available.
See [Large objects (BLOBs)](exchange.html#blob) for more discussion.
See [Large objects (BLOBs)](../lobs.md) for more discussion.
## class rowid
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment