Merge pull request #37153 from MicrosoftDocs/FromPublicRepo

Confirm merge from FromPublicRepo to main to sync with https://github.com/MicrosoftDocs/sql-docs (branch live)

Author: Albertyang0

docs/odbc/reference/syntax/sqlgetinfo-function.md

@@ -585,6 +585,7 @@ The following table alphabetically lists each information type, the version of O
 |SQL_ODBC_VER|1.0|A character string with the version of ODBC to which the Driver Manager conforms. The version is of the form ##.##.0000, where the first two digits are the major version and the next two digits are the minor version. This is implemented only in the Driver Manager.|
 |SQL_OJ_CAPABILITIES|2.01|An SQLUINTEGER bitmask enumerating the types of outer joins supported by the driver and data source. The following bitmasks are used to determine which types are supported:<br/>SQL_OJ_LEFT = Left outer joins are supported.<br/>SQL_OJ_RIGHT = Right outer joins are supported.<br/>SQL_OJ_FULL = Full outer joins are supported.<br/>SQL_OJ_NESTED = Nested outer joins are supported.<br/>SQL_OJ_NOT_ORDERED = The column names in the ON clause of the outer join do not have to be in the same order as their respective table names in the **OUTER JOIN** clause.<br/>SQL_OJ_INNER = The inner table (the right table in a left outer join or the left table in a right outer join) can also be used in an inner join. This does not apply to full outer joins, which do not have an inner table.<br/>SQL_OJ_ALL_COMPARISON_OPS = The comparison operator in the ON clause can be any of the ODBC comparison operators. If this bit is not set, only the equals (=) comparison operator can be used in outer joins.<br/><br/>If none of these options is returned as supported, no outer join clause is supported.<br/><br/>For information about the support of relational join operators in a SELECT statement, as defined by SQL-92, see SQL_SQL92_RELATIONAL_JOIN_OPERATORS.|
 |SQL_ORDER_BY_COLUMNS_IN_SELECT|2.0|A character string: "Y" if the columns in the **ORDER BY** clause must be in the select list; otherwise, "N".|
+|SQL_OUTER_JOINS|1.0|Note: The information type was introduced in ODBC 1.0; each return value is labeled with the version in which it was introduced.<br/><br/>A character string:<br/><br/>"N" = No. The data source does not support outer joins. (ODBC 1.0)<br/><br/>"Y" = Yes. The data source supports two-table outer joins, and the driver supports the ODBC outer join syntax except for nested outer joins. However, columns on the left side of the comparison operator in the ON clause must come from the left-hand table in the outer join, and columns on the right side of the comparison operator must come from the right-hand table. (ODBC 1.0)<br/><br/>"P" = Partial. The data source partially supports nested outer joins, and the driver supports the ODBC outer join syntax. However, columns on the left side of the comparison operator in the ON clause must come from the left-hand table in the outer join and columns on the right side of the comparison operator must come from the right-hand table. Also, the right-hand table of an outer join cannot be included in an inner join. (ODBC 2.0)<br/><br/>"F" = Full. The data source fully supports nested outer joins, and the driver supports the ODBC outer join syntax. (ODBC 2.0)|
 |SQL_PARAM_ARRAY_ROW_COUNTS|3.0|An SQLUINTEGER enumerating the driver's properties regarding the availability of row counts in a parameterized execution. Has the following values:<br/>SQL_PARC_BATCH = Individual row counts are available for each set of parameters. This is conceptually equivalent to the driver generating a batch of SQL statements, one for each parameter set in the array. Extended error information can be retrieved by using the SQL_PARAM_STATUS_PTR descriptor field.<br/>SQL_PARC_NO_BATCH = There is only one row count available, which is the cumulative row count resulting from the execution of the statement for the entire array of parameters. This is conceptually equivalent to treating the statement together with the complete parameter array as one atomic unit. Errors are handled the same as if one statement were executed.|
 |SQL_PARAM_ARRAY_SELECTS|3.0|An SQLUINTEGER enumerating the driver's properties regarding the availability of result sets in a parameterized execution. Has the following values:<br/>SQL_PAS_BATCH = There is one result set available per set of parameters. This is conceptually equivalent to the driver generating a batch of SQL statements, one for each parameter set in the array.<br/>SQL_PAS_NO_BATCH = There is only one result set available, which represents the cumulative result set resulting from the execution of the statement for the complete array of parameters. This is conceptually equivalent to treating the statement together with the complete parameter array as one atomic unit.<br/>SQL_PAS_NO_SELECT = A driver does not allow a result-set generating statement to be executed with an array of parameters.|
 |SQL_POS_OPERATIONS|2.0|An SQLINTEGER bitmask enumerating the support operations in **SQLSetPos**.<br/><br/>The following bitmasks are used together with the flag to determine which options are supported.<br/>SQL_POS_POSITION (ODBC 2.0)<br/>SQL_POS_REFRESH (ODBC 2.0)<br/>SQL_POS_UPDATE (ODBC 2.0)<br/>SQL_POS_DELETE (ODBC 2.0)<br/>SQL_POS_ADD (ODBC 2.0)|