Merge remote-tracking branch 'origin/release/8.1' into trunk

Author: rsomla1

doc/devapi_ref.txt

@@ -1,7 +1,7 @@
-Connector/C++ 8.0 X DevAPI Reference {#devapi_ref}
+Connector/C++ 8 X DevAPI Reference {#devapi_ref}
 ====================================
 
-Connector/C++ 8.0 implements the X DevAPI, as described in
+Connector/C++ 8 implements the X DevAPI, as described in
 the [X DevAPI User Guide]
 (http://dev.mysql.com/doc/x-devapi-userguide/en/index.html).
 The X DevAPI allows one to work with MySQL Servers implementing a document store
@@ -41,7 +41,7 @@ the X DevAPI is presented below. See also the [list of X DevAPI classes]
 The following Connector/C++ application connects to a MySQL Server with
 X Plugin, creates a document collection, adds a few documents to it, queries
 the collection and displays the result. The sample code can be found in file
-`testapp/devapi_test.cc` in the source distribution of Connector/C++ 8.0.
+`testapp/devapi_test.cc` in the source distribution of Connector/C++ 8.
 See @ref usage for instructions on how to build the sample code.
 
 @dontinclude devapi_test.cc

doc/index.txt

@@ -2,7 +2,7 @@ MySQL Connector/C++ Documentation  {#mainpage}
 =================================
 
 MySQL Connector/C++ is a library for applications written in C or C++ that
-communicate with MySQL database servers. Version 8.0 of Connector/C++
+communicate with MySQL database servers. Version 8 of Connector/C++
 implements three different APIs which can be used by applications:
 
 - The new [X DevAPI](@ref devapi_ref) for applications written in C++.
@@ -11,14 +11,14 @@ implements three different APIs which can be used by applications:
   also implemented in version 1.1 of the connector.
 
 The new APIs give access to MySQL implementing a 
-[document store](https://dev.mysql.com/doc/refman/8.0/en/document-store.html). 
+[document store](https://dev.mysql.com/doc/refman/en/document-store.html). 
 Internally these APIs use the new X Protocol to communicate with the MySQL 
 Server. Consequently, code written against these APIs can work only with MySQL 
 Server 8 with the X Plugin enabled in it. Apart from accessing the document 
 store, the new APIs allow executing traditional SQL queries as well.
 
 Applications written against the JDBC4 based API of Connector/C++ 1.1 can be also
-compiled with Connector/C++ 8.0 which is backward compatible with the earlier
+compiled with Connector/C++ 8 which is backward compatible with the earlier
 version. Such code does not require the X Plugin and can communicate with older
 versions of the MySQL Server using the legacy protocol.
 
@@ -33,7 +33,7 @@ More information:
 - [Indexing Document Collections](@ref indexing)
 
 See also our
-[online documentation](https://dev.mysql.com/doc/connector-cpp/8.0/en/)
+[online documentation](https://dev.mysql.com/doc/connector-cpp/en/)
 
 <!--
   Copyright (c) 2015, 2022, Oracle and/or its affiliates.

doc/indexing.txt

@@ -61,22 +61,22 @@ If the index type is not specified, or is set to "INDEX" then a plain index
 is created as by SQL command "CREATE INDEX ...". If the index type is set
 to "SPATIAL" then the created index is like one created by SQL command
 "CREATE SPATIAL INDEX ...", see
-https://dev.mysql.com/doc/refman/8.0/en/spatial-index-optimization.html
+https://dev.mysql.com/doc/refman/en/spatial-index-optimization.html
 and
-https://dev.mysql.com/doc/refman/8.0/en/creating-spatial-indexes.html.
+https://dev.mysql.com/doc/refman/en/creating-spatial-indexes.html.
 In this case it is not allowed to set the "required" field to false in field
 descriptions.
 
 Values of indexed fields are converted from JSON to the type specified
 in the index field description using standard MySQL type conversions (see
-https://dev.mysql.com/doc/refman/8.0/en/type-conversion.html). Note that
+https://dev.mysql.com/doc/refman/en/type-conversion.html). Note that
 this means that, for example, when using a numeric type in an index field
 description and the actual field value is non-numeric, it will be usually
 converted to 0.
 
 For index fields with GEOJSON type MySQL function ST_GeomFromGeoJSON() is used
 for conversion (see
- https://dev.mysql.com/doc/refman/8.0/en/spatial-geojson-functions.html#function_st-geomfromgeojson).
+ https://dev.mysql.com/doc/refman/en/spatial-geojson-functions.html#function_st-geomfromgeojson).
 In this case, the "options" and "srid" fields might be present in the field
 description and if this is the case they are used as parameters for
 ST_GeomFromGeoJSON() during conversion.

doc/jdbc_ref.txt

@@ -1,14 +1,13 @@
-Connector/C++ 8.0 legacy C++ API based on JDBC4 {#jdbc_ref}
+Connector/C++ 8 legacy C++ API based on JDBC4 {#jdbc_ref}
 =======================================
 
-Connector/C++ 8.0 supports the legacy C++ API based on the JDBC4 specification.
+Connector/C++ 8 supports the legacy C++ API based on the JDBC4 specification.
 
-This allows an easy migration to Connector/C++ version 8.0 for applications
+This allows an easy migration to Connector/C++ version 8.x for applications
 that use Connector/C++ version 1.1.
 
 More detailed information about the legacy C++ API can be found in the
-[X MySQL Connector/C++ Developer Guide]
-(https://dev.mysql.com/doc/connector-cpp/en/)
+[MySQL Connector/C++ 1.1 Developer Guide](https://dev.mysql.com/doc/connector-cpp/1.1/en/)
 of MySQL online manual.
 
 
@@ -23,7 +22,7 @@ legacy C++ API.
 
 After the connection is established the code executes a simple SQL statement
 and reads the result from the server. The source file can be found in
-testapp/jdbc_test.cc in the source distribution of Connector/C++ 8.0.
+testapp/jdbc_test.cc in the source distribution of Connector/C++ 8.
 See @ref usage for instructions on how to build the sample code.
 
 Each program which uses the legacy C++ API has to include this header:

doc/usage.txt

@@ -1,10 +1,10 @@
-Using Connector/C++ 8.0  {#usage}
+Using Connector/C++ 8  {#usage}
 =======================
 
-Connector/C++ 8.0 implements new APIs for accessing document store of
+Connector/C++ 8 implements new APIs for accessing document store of
 MySQL Server 8: X DevAPI for applications written in C++11 and X DevAPI for C
 for applications written in plain C. The same APIs can be also used to execute
-traditional SQL queries. Connector/C++ 8.0 also implements the legacy C++ API
+traditional SQL queries. Connector/C++ 8 also implements the legacy C++ API
 based on JDBC4 which is backward compatible with version 1.1 of the connector.
 
 The choice of the API is done by including appropriate public headers.
@@ -53,7 +53,7 @@ Depending on the platform, the shared Connector/C++ library is named:
 - `mysqlcppconn8-1-vsXX.dll` on Windows platforms
   (with import library vsXX/mysqlcppconn8.lib)
 
-This library implements the new X DevAPI and X DevAPI for C. Connector/C++ 8.0
+This library implements the new X DevAPI and X DevAPI for C. Connector/C++ 8
 also includes the legacy connector library `libmsysqlcppconn(.so/.dylib/.dll)`
 which implements the legacy JDBC4 API.
 
@@ -243,7 +243,7 @@ target computer on which the application will run.
 
 For more information on building code that uses Connector/C++ consult our
 [online documentation]
-(https://dev.mysql.com/doc/connector-cpp/8.0/en/connector-cpp-apps.html).
+(https://dev.mysql.com/doc/connector-cpp/en/connector-cpp-apps.html).
 
 
 <!--

doc/xapi_ref.txt

@@ -1,4 +1,4 @@
-Connector/C++ 8.0 X DevAPI for C Reference {#xapi_ref}
+Connector/C++ 8 X DevAPI for C Reference {#xapi_ref}
 ================================
 
 Connector/C++ implements a variant of X DevAPI that can be used by applications
@@ -93,7 +93,7 @@ ways such as plain SQL with parameters and table INSERT statements. Next,
 the code reads the table rows and displays the result.
 
 The sample code can be found in file `testapp/xapi_test.cc` in the source
-distribution of Connector/C++ 8.0. See @ref usage for instructions on how
+distribution of Connector/C++ 8. See @ref usage for instructions on how
 to build the sample code.
 
 @dontinclude xapi_test.c