Github user gtapper commented on a diff in the pull request:
https://github.com/apache/incubator-trafodion/pull/457#discussion_r61673390
--- Diff:
docs/jdbct4ref_guide/src/asciidoc/_chapters/properties_detail.adoc ---
@@ -0,0 +1,959 @@
+////
+/**
+ *@@@ START COPYRIGHT @@@
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ * @@@ END COPYRIGHT @@@
+ */
+////
+
+[[type-4-driver-property-descriptions]]
+= Type 4 Driver Property Descriptions
+
+The properties are listed in alphabetic order with their descriptions.
+For the properties summarized in categories, see
+<<summary-of-type-4-driver-properties, Summary of Type 4 Driver
Properties>>.
+
+////
+[[blobtablename]]
+== blobTableName Property
+
+See <<lob-table-name, LOB Table Name Properties>>.
+////
+
+[[catalog]]
+== catalog Property
+
+The `catalog` property sets the default catalog used to access SQL objects
+referenced in SQL statements if the SQL objects are not fully qualified.
+
+Set this property on a `DataSource` object, `ConnectionPoolDataSource`
+object, or `DriverManager` object. For information about how to set
+properties, see
+<<how-to-specify-jdbc-type-4-properties, How to Specify JDBC Type 4
Properties>>.
+
+```
+Data type: String
+
+Default: none
+```
+
+*Example*
+
+Specifying the catalog Seabase:
+
+```
+catalog=Seabase
+```
+
+////
+[[clobtablename]]
+== clobTableName Property
+
+See <<lob-table-name, LOB Table Name Properties>>.
+////
+
+<<<
+[[connectiontimeout]]
+== connectionTimeout Property
+
+The `connectionTimeout` property sets the number of seconds a connection
+can be idle before the connection is physically closed by DCS.
+
+Set this property on a `DataSource` object, `ConnectionPoolDataSource`
+object, or `DriverManager` object. For information about how to set
+properties, see
+<<how-to-specify-jdbc-type-4-properties, How to Specify JDBC Type 4
Properties>>.
+
+```
+Data type: int
+
+Units: seconds
+
+Default: -1 (Use the ConnTimeout value set on the server-side data source.)
+
+Range: -1, 0 to 2147483647
+```
+
+* Zero (0) specifies infinity as the timeout value.
+* A non-zero positive value overrides the value set on the
+{project-name} data source, if allowed by the connectivity settings.
+* A negative value is treated as -1.
+
+*Example*
+
+Consider the following scenario.
+
+Even if a connection is not being used, it takes up resources. The
application
+abandons connections; that is, the application does not physically close a
+connection after the application finishes using the connection.
+
+However, you can configure the connection to close itself after 300
seconds by setting
+the `connectionTimeout` property. Then, when a connection is not
referenced for 300 seconds,
+the connection automatically closes itself.
+
+In this example, the specification to set the `connectionTimeout` property
is:
+
+```
+connectionTimeout=300
+```
+
+<<<
+[[fetchbuffersize]]
+== fetchBufferSize Property
+
+The `fetchBufferSize` property provides the benefits of bulk fetch.
+
+This property sets the value in kilobytes (KB) of the size of the fetch
+buffer that is used when rows are fetched from a `ResultSet` object after
+a successful `executeQuery()` operation on a statement.
+
+Set this property on a `DriverManager` object. For information about how
to set
+properties, see
+<<how-to-specify-jdbc-type-4-properties, How to Specify JDBC Type 4
Properties>>.
+
+```
+Data type: short
+
+Default size: 4
+
+Range: 4 through 32767
+```
+
+* Zero and negative values are treated as default values.
+* The Type 4 driver guarantees that the number of rows internally
+fetched will be no less than the minimum of the row size (set using
+the `setFetchSize` method) and the number of rows that will fit in the
+memory specified by the `setFetchSize` (set using the property).
+
+*Example*
+
+```
+fetchBufferSize=32
+```
+
+<<<
+[[initialpoolsize]]
+== initialPoolSize Property
+
+The `initialPoolSize` property sets the initial connection pool size when
+connection pooling is used with the Type 4 driver.
+
+Set this property on a `DataSource` object, `ConnectionPoolDataSource`
+object, or `DriverManager` object. For information about how to set
+properties, see
+<<how-to-specify-jdbc-type-4-properties, How to Specify JDBC Type 4
Properties>>.
+
+The driver creates _n_ connections (where _n_ is `initialPoolSize`) for
+each connection pool when the first connection is requested. For
+example, if `initialPoolSize` is set to `5` for a data source, then the
driver
+attempts to create and pool five connections the first time the
+application calls the data source's `getConnection()` method.
+
+```
+Data type: int
+
+Units: number of physical connections
+
+Default: -1 (Do not create an initial connection pool.)
+
+Range: -1 to maxPoolSize
+```
+
+* Any negative value is treated as -1.
+* Values can be less than `minPoolSize`, but must not exceed `maxPoolSize`.
+If the specified value is greater than `maxPoolSize`, the `maxPoolSize`
+property value is used.
+
+*Example*
+
+```
+initialPoolSize=10
+```
+
+<<<
+[[iso88591]]
+== ISO88591 Property
+
+The `ISO88591` character-set mapping property corresponds to the
+SQL ISO88591 character set, which is a single-byte
+8-bit character set for character data types. This property supports
+English and other Western European languages. For more information, see
+<<internationalization-support, Internationalization Support>>.
+
+Set this property on a `DataSource` object or `DriverManager` object. This
+property is ignored for connections made through the
+`ConnectionPoolDataSource` object.
+For information about how to set properties, see
+<<how-to-specify-jdbc-type-4-properties, How to Specify JDBC Type 4
Properties>>.
+```
+Data type: String
+
+Default: ISO88591_1
+```
+
+The value can be any valid Java Canonical Name as listed in the
+"Canonical Name for java.io and java.lang API" column of the
+http://docs.oracle.com/javase/6/docs/technotes/guides/intl/encoding.doc.html[Java
documentation].
+
+For more information, see
+<<internationalization-support, Internationalization Support>>.
+
+<<<
+[[kanji]]
+== KANJI Property
+
+The `KANJI` character-set mapping property corresponds to the
+SQL KANJI character set, which is a double-byte character set widely used
on Japanese mainframes.
+This property is a subset of Shift JIS: the double character portion. The
encoding for
+this property is big endian.
+
+Set this property on a `DataSource` object, `ConnectionPoolDataSource`
+object, or `DriverManager` object.
+For information about how to set properties, see
+<<how-to-specify-jdbc-type-4-properties, How to Specify JDBC Type 4
Properties>>.
+
+```
+Data type: String
+
+Default: SJIS (which is shift-JIS, Japanese)
+```
+
+*Example*
+
+```
+java -Dhpt4jdbc.KANJI=SJIS
--- End diff --
Changed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
