[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-trafodion/pull/457


---
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.
---

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61689861
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/tracing_logging.adoc 
---
@@ -0,0 +1,195 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[tracing-and-logging-facilities]]
+= Tracing and Logging Facilities
+
+The Type 4 driver provides two tracing and logging facilities:
+
+* Standard JDBC tracing and logging functionality as defined by the JDBC 
standard
+* Type 4 driver logging facility
+
+Server-side tracing (logging) is enabled by configuring DCS.
+
+[[standard-jdbc-tracing-and-logging-facility]]
+== Standard JDBC Tracing and Logging Facility
+
+The JDBC standard provides a logging and tracing facility, which allows
+tracing JDBC method calls by setting the log writer. To set the log
+writer, either call the `setLogWriter()` method on the `DriverManager` 
class
+or call the `setLogWriter()` method on the `DataSource` class
+(or `ConnectionPoolDataSource` class).
+
+* A `DriverManager` log writer is a character output stream to which all
+logging and tracing messages for all connections made through the
+`DriverManager` are printed. This stream includes messages printed by the
+methods of this connection, messages printed by methods of other objects
+manufactured by the connection, and so on. The `DriverManager` log writer
+is initially null, that is, the default is for logging to be disabled.
+
+For information about using the setLogWriter method, see the

+https://docs.oracle.com/javase/7/docs/api/java/sql/DriverManager.html[DriverManager
 class API].
+
+* A `DataSource` log writer is a character output stream to which all
+logging and tracing messages for this data source are printed. This
+stream includes messages printed by the methods of this object, messages
+printed by methods of other objects manufactured by this object, and so
+on. Messages printed to a data-source-specific log writer are not
+printed to the log writer associated with the `java.sql.DriverManager`
+class. When a `DataSource` object is created, the log writer is initially
+null; that is, the default is for logging to be disabled.
+
+For information about using the setLogWriter method, see the

+https://docs.oracle.com/cd/E16338_01/appdev.112/e13995/oracle/jdbc/pool/OracleDataSource.html[DriverSource
 interface API].
+
+<<<
+[[the-type-4-driver-logging-facility]]
+== The Type 4 Driver Logging Facility
+
+
+The Type 4 driver Logging facility allows you to retrieve internal
+tracing information, which you can use in debugging the driver. It also
+allows you to capture error and warning messages.
+
+In addition to the standard JDBC tracing and logging facility, the Type
+4 driver provides an independent logging facility (Type 4 Driver
+Logging). The Type 4 Driver Logging provides the same level of logging
+and tracing as the standard JDBC tracing and logging facility with the
+following additional information:
+
+* More detail about the internals of the Type 4 driver and internal 
tracing information
+* Type 4 driver performance-tuning information
+* Finer control over the amount and type of logging information
+* Error and warning messages
+
+[[accessing-the-type-4-driver-logging-facility]]
+=== Accessing the Type 4 Driver Logging Facility
+
+The Type 4 Driver Logging facility is based on the `java.util.logging`
+package. The Type 4 driver instantiates a `java.util.logging.Logger` class
+and names the logger `org.trafodion.jdbc.t4.logger`.
+
+Your JDBC program can access the Type 4 driver logger directly by
+calling the `java.util.logging.Logger` static method `getLogger(String)`.
+
+*example*
+
+[source, java]
+
+String t4Logger =
+   

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61689858
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/tracing_logging.adoc 
---
@@ -0,0 +1,195 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[tracing-and-logging-facilities]]
+= Tracing and Logging Facilities
+
+The Type 4 driver provides two tracing and logging facilities:
+
+* Standard JDBC tracing and logging functionality as defined by the JDBC 
standard
+* Type 4 driver logging facility
+
+Server-side tracing (logging) is enabled by configuring DCS.
+
+[[standard-jdbc-tracing-and-logging-facility]]
+== Standard JDBC Tracing and Logging Facility
+
+The JDBC standard provides a logging and tracing facility, which allows
+tracing JDBC method calls by setting the log writer. To set the log
+writer, either call the `setLogWriter()` method on the `DriverManager` 
class
+or call the `setLogWriter()` method on the `DataSource` class
+(or `ConnectionPoolDataSource` class).
+
+* A `DriverManager` log writer is a character output stream to which all
+logging and tracing messages for all connections made through the
+`DriverManager` are printed. This stream includes messages printed by the
+methods of this connection, messages printed by methods of other objects
+manufactured by the connection, and so on. The `DriverManager` log writer
+is initially null, that is, the default is for logging to be disabled.
+
+For information about using the setLogWriter method, see the

+https://docs.oracle.com/javase/7/docs/api/java/sql/DriverManager.html[DriverManager
 class API].
+
+* A `DataSource` log writer is a character output stream to which all
+logging and tracing messages for this data source are printed. This
+stream includes messages printed by the methods of this object, messages
+printed by methods of other objects manufactured by this object, and so
+on. Messages printed to a data-source-specific log writer are not
+printed to the log writer associated with the `java.sql.DriverManager`
+class. When a `DataSource` object is created, the log writer is initially
+null; that is, the default is for logging to be disabled.
+
+For information about using the setLogWriter method, see the

+https://docs.oracle.com/cd/E16338_01/appdev.112/e13995/oracle/jdbc/pool/OracleDataSource.html[DriverSource
 interface API].
+
+<<<
+[[the-type-4-driver-logging-facility]]
+== The Type 4 Driver Logging Facility
+
+
+The Type 4 driver Logging facility allows you to retrieve internal
+tracing information, which you can use in debugging the driver. It also
+allows you to capture error and warning messages.
+
+In addition to the standard JDBC tracing and logging facility, the Type
+4 driver provides an independent logging facility (Type 4 Driver
+Logging). The Type 4 Driver Logging provides the same level of logging
+and tracing as the standard JDBC tracing and logging facility with the
+following additional information:
+
+* More detail about the internals of the Type 4 driver and internal 
tracing information
+* Type 4 driver performance-tuning information
+* Finer control over the amount and type of logging information
+* Error and warning messages
+
+[[accessing-the-type-4-driver-logging-facility]]
+=== Accessing the Type 4 Driver Logging Facility
+
+The Type 4 Driver Logging facility is based on the `java.util.logging`
+package. The Type 4 driver instantiates a `java.util.logging.Logger` class
+and names the logger `org.trafodion.jdbc.t4.logger`.
+
+Your JDBC program can access the Type 4 driver logger directly by
+calling the `java.util.logging.Logger` static method `getLogger(String)`.
+
+*example*
+
+[source, java]
+
+String t4Logger =
+   

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61689853
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/tracing_logging.adoc 
---
@@ -0,0 +1,195 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[tracing-and-logging-facilities]]
+= Tracing and Logging Facilities
+
+The Type 4 driver provides two tracing and logging facilities:
+
+* Standard JDBC tracing and logging functionality as defined by the JDBC 
standard
+* Type 4 driver logging facility
+
+Server-side tracing (logging) is enabled by configuring DCS.
+
+[[standard-jdbc-tracing-and-logging-facility]]
+== Standard JDBC Tracing and Logging Facility
+
+The JDBC standard provides a logging and tracing facility, which allows
+tracing JDBC method calls by setting the log writer. To set the log
+writer, either call the `setLogWriter()` method on the `DriverManager` 
class
+or call the `setLogWriter()` method on the `DataSource` class
+(or `ConnectionPoolDataSource` class).
+
+* A `DriverManager` log writer is a character output stream to which all
+logging and tracing messages for all connections made through the
+`DriverManager` are printed. This stream includes messages printed by the
+methods of this connection, messages printed by methods of other objects
+manufactured by the connection, and so on. The `DriverManager` log writer
+is initially null, that is, the default is for logging to be disabled.
+
+For information about using the setLogWriter method, see the

+https://docs.oracle.com/javase/7/docs/api/java/sql/DriverManager.html[DriverManager
 class API].
+
+* A `DataSource` log writer is a character output stream to which all
+logging and tracing messages for this data source are printed. This
+stream includes messages printed by the methods of this object, messages
+printed by methods of other objects manufactured by this object, and so
+on. Messages printed to a data-source-specific log writer are not
+printed to the log writer associated with the `java.sql.DriverManager`
+class. When a `DataSource` object is created, the log writer is initially
+null; that is, the default is for logging to be disabled.
+
+For information about using the setLogWriter method, see the

+https://docs.oracle.com/cd/E16338_01/appdev.112/e13995/oracle/jdbc/pool/OracleDataSource.html[DriverSource
 interface API].
+
+<<<
+[[the-type-4-driver-logging-facility]]
+== The Type 4 Driver Logging Facility
+
+
+The Type 4 driver Logging facility allows you to retrieve internal
+tracing information, which you can use in debugging the driver. It also
+allows you to capture error and warning messages.
+
+In addition to the standard JDBC tracing and logging facility, the Type
+4 driver provides an independent logging facility (Type 4 Driver
+Logging). The Type 4 Driver Logging provides the same level of logging
+and tracing as the standard JDBC tracing and logging facility with the
+following additional information:
+
+* More detail about the internals of the Type 4 driver and internal 
tracing information
+* Type 4 driver performance-tuning information
+* Finer control over the amount and type of logging information
+* Error and warning messages
+
+[[accessing-the-type-4-driver-logging-facility]]
+=== Accessing the Type 4 Driver Logging Facility
+
+The Type 4 Driver Logging facility is based on the `java.util.logging`
+package. The Type 4 driver instantiates a `java.util.logging.Logger` class
+and names the logger `org.trafodion.jdbc.t4.logger`.
+
+Your JDBC program can access the Type 4 driver logger directly by
+calling the `java.util.logging.Logger` static method `getLogger(String)`.
+
+*example*
+
+[source, java]
+
+String t4Logger =
+   

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61689828
  
--- Diff: 
docs/jdbct4ref_guide/src/asciidoc/_chapters/properties_overview.adoc ---
@@ -0,0 +1,245 @@
+
+/**
+ *@@@ 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-properties]]
+= Type 4 Driver Properties
+
+[[summary-of-type-4-driver-properties]]
+== Summary of Type 4 Driver Properties
+
+Type 4 driver properties that effect client-side operations are
+summarized in the following tables. For the detailed description, click
+the link provided in the property name.
+
+NOTE: Unless otherwise noted in the brief description, the particular
+property applies to the `DataSource` object, `DriverManager` object, and
+`ConnectionPoolDataSource` object.
+
+[[client-side-properties]]
+=== Client-Side Properties
+
+*Connection-Control Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>`   | Specifies the registered 
DataSource or ConnectionPoolDataSource name. (Can be set only on the 
DriverManager object.) | None.
+| `<>`   | Sets the time limit that a 
connection can be attempted before the connection disconnects. | 60 (seconds)
+| `<>`   | Sets a time limit that the 
driver waits for a reply from the database server. | 0 (No network timeout is 
specified. 
+|===
+
+*Pooling Management Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>` | Sets the initial connection 
pool size when connection pooling is used with the Type 4 driver. (Ignored for
+connections made through the ConnectionPoolDataSource object.) | -1 (Do 
not create an initial connection pool.)
+| `<>` | Sets the number of seconds that 
a physical connection can remain unused in the pool before the connection is 
closed. | 0 (Specifies no limit.)
+| `<>` | Sets the maximum number of 
physical connections that the pool can contain. | -1 (Disables connection 
pooling.) 
+| `<>` | Sets the total number of 
PreparedStatement objects that the connection pool should cache. | 0 (Disables 
statement pooling.)
+| `<>` | Limits the number of physical 
connections that can be in the free connection pool. | -1 (The minPoolSize 
value is ignored.)
+|===
+
+
+*Operations on CLOB and BLOB Data*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>` | Specifies the LOB table for 
using BLOB columns. | None.
+| `<>` | Specifies the LOB table for 
using CLOB columns. | None.
+| `<>` | Sets the number of data 
locators to be reserved for a process that stores data in a LOB table. | 100 
+|===
+
+
+<<<
+*Internationalization Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>`   | Sets character-set mapping that 
corresponds to the ISO88591 character set. | ISO88591_1
+| `<>` | Sets character-set mapping that 
corresponds to the KANJI character set. | SJIS (which is shift-JIS, Japanese)
+| `<>` | Sets character-set mapping that 
corresponds to the KSC5601 character set. | ECU_KR (which is KS C 5601, ECU 
encoding, Korean)
+| `<>`   | Sets the language 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61689832
  
--- Diff: 
docs/jdbct4ref_guide/src/asciidoc/_chapters/properties_overview.adoc ---
@@ -0,0 +1,245 @@
+
+/**
+ *@@@ 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-properties]]
+= Type 4 Driver Properties
+
+[[summary-of-type-4-driver-properties]]
+== Summary of Type 4 Driver Properties
+
+Type 4 driver properties that effect client-side operations are
+summarized in the following tables. For the detailed description, click
+the link provided in the property name.
+
+NOTE: Unless otherwise noted in the brief description, the particular
+property applies to the `DataSource` object, `DriverManager` object, and
+`ConnectionPoolDataSource` object.
+
+[[client-side-properties]]
+=== Client-Side Properties
+
+*Connection-Control Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>`   | Specifies the registered 
DataSource or ConnectionPoolDataSource name. (Can be set only on the 
DriverManager object.) | None.
+| `<>`   | Sets the time limit that a 
connection can be attempted before the connection disconnects. | 60 (seconds)
+| `<>`   | Sets a time limit that the 
driver waits for a reply from the database server. | 0 (No network timeout is 
specified. 
+|===
+
+*Pooling Management Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>` | Sets the initial connection 
pool size when connection pooling is used with the Type 4 driver. (Ignored for
+connections made through the ConnectionPoolDataSource object.) | -1 (Do 
not create an initial connection pool.)
+| `<>` | Sets the number of seconds that 
a physical connection can remain unused in the pool before the connection is 
closed. | 0 (Specifies no limit.)
+| `<>` | Sets the maximum number of 
physical connections that the pool can contain. | -1 (Disables connection 
pooling.) 
+| `<>` | Sets the total number of 
PreparedStatement objects that the connection pool should cache. | 0 (Disables 
statement pooling.)
+| `<>` | Limits the number of physical 
connections that can be in the free connection pool. | -1 (The minPoolSize 
value is ignored.)
+|===
+
+
+*Operations on CLOB and BLOB Data*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>` | Specifies the LOB table for 
using BLOB columns. | None.
+| `<>` | Specifies the LOB table for 
using CLOB columns. | None.
+| `<>` | Sets the number of data 
locators to be reserved for a process that stores data in a LOB table. | 100 
+|===
+
+
+<<<
+*Internationalization Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>`   | Sets character-set mapping that 
corresponds to the ISO88591 character set. | ISO88591_1
+| `<>` | Sets character-set mapping that 
corresponds to the KANJI character set. | SJIS (which is shift-JIS, Japanese)
+| `<>` | Sets character-set mapping that 
corresponds to the KSC5601 character set. | ECU_KR (which is KS C 5601, ECU 
encoding, Korean)
+| `<>`   | Sets the language 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61689796
  
--- Diff: 
docs/jdbct4ref_guide/src/asciidoc/_chapters/properties_overview.adoc ---
@@ -0,0 +1,245 @@
+
+/**
+ *@@@ 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-properties]]
+= Type 4 Driver Properties
+
+[[summary-of-type-4-driver-properties]]
+== Summary of Type 4 Driver Properties
+
+Type 4 driver properties that effect client-side operations are
+summarized in the following tables. For the detailed description, click
+the link provided in the property name.
+
+NOTE: Unless otherwise noted in the brief description, the particular
+property applies to the `DataSource` object, `DriverManager` object, and
+`ConnectionPoolDataSource` object.
+
+[[client-side-properties]]
+=== Client-Side Properties
+
+*Connection-Control Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>`   | Specifies the registered 
DataSource or ConnectionPoolDataSource name. (Can be set only on the 
DriverManager object.) | None.
+| `<>`   | Sets the time limit that a 
connection can be attempted before the connection disconnects. | 60 (seconds)
+| `<>`   | Sets a time limit that the 
driver waits for a reply from the database server. | 0 (No network timeout is 
specified. 
+|===
+
+*Pooling Management Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>` | Sets the initial connection 
pool size when connection pooling is used with the Type 4 driver. (Ignored for
+connections made through the ConnectionPoolDataSource object.) | -1 (Do 
not create an initial connection pool.)
+| `<>` | Sets the number of seconds that 
a physical connection can remain unused in the pool before the connection is 
closed. | 0 (Specifies no limit.)
+| `<>` | Sets the maximum number of 
physical connections that the pool can contain. | -1 (Disables connection 
pooling.) 
+| `<>` | Sets the total number of 
PreparedStatement objects that the connection pool should cache. | 0 (Disables 
statement pooling.)
+| `<>` | Limits the number of physical 
connections that can be in the free connection pool. | -1 (The minPoolSize 
value is ignored.)
+|===
+
+
+*Operations on CLOB and BLOB Data*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>` | Specifies the LOB table for 
using BLOB columns. | None.
+| `<>` | Specifies the LOB table for 
using CLOB columns. | None.
+| `<>` | Sets the number of data 
locators to be reserved for a process that stores data in a LOB table. | 100 
+|===
+
+
+<<<
+*Internationalization Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>`   | Sets character-set mapping that 
corresponds to the ISO88591 character set. | ISO88591_1
+| `<>` | Sets character-set mapping that 
corresponds to the KANJI character set. | SJIS (which is shift-JIS, Japanese)
+| `<>` | Sets character-set mapping that 
corresponds to the KSC5601 character set. | ECU_KR (which is KS C 5601, ECU 
encoding, Korean)
+| `<>`   | Sets the language 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61689786
  
--- Diff: 
docs/jdbct4ref_guide/src/asciidoc/_chapters/properties_overview.adoc ---
@@ -0,0 +1,245 @@
+
+/**
+ *@@@ 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-properties]]
+= Type 4 Driver Properties
+
+[[summary-of-type-4-driver-properties]]
+== Summary of Type 4 Driver Properties
+
+Type 4 driver properties that effect client-side operations are
+summarized in the following tables. For the detailed description, click
+the link provided in the property name.
+
+NOTE: Unless otherwise noted in the brief description, the particular
+property applies to the `DataSource` object, `DriverManager` object, and
+`ConnectionPoolDataSource` object.
+
+[[client-side-properties]]
+=== Client-Side Properties
+
+*Connection-Control Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>`   | Specifies the registered 
DataSource or ConnectionPoolDataSource name. (Can be set only on the 
DriverManager object.) | None.
+| `<>`   | Sets the time limit that a 
connection can be attempted before the connection disconnects. | 60 (seconds)
+| `<>`   | Sets a time limit that the 
driver waits for a reply from the database server. | 0 (No network timeout is 
specified. 
+|===
+
+*Pooling Management Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>` | Sets the initial connection 
pool size when connection pooling is used with the Type 4 driver. (Ignored for
+connections made through the ConnectionPoolDataSource object.) | -1 (Do 
not create an initial connection pool.)
+| `<>` | Sets the number of seconds that 
a physical connection can remain unused in the pool before the connection is 
closed. | 0 (Specifies no limit.)
+| `<>` | Sets the maximum number of 
physical connections that the pool can contain. | -1 (Disables connection 
pooling.) 
+| `<>` | Sets the total number of 
PreparedStatement objects that the connection pool should cache. | 0 (Disables 
statement pooling.)
+| `<>` | Limits the number of physical 
connections that can be in the free connection pool. | -1 (The minPoolSize 
value is ignored.)
+|===
+
+
+*Operations on CLOB and BLOB Data*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>` | Specifies the LOB table for 
using BLOB columns. | None.
+| `<>` | Specifies the LOB table for 
using CLOB columns. | None.
+| `<>` | Sets the number of data 
locators to be reserved for a process that stores data in a LOB table. | 100 
+|===
+
+
+<<<
+*Internationalization Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>`   | Sets character-set mapping that 
corresponds to the ISO88591 character set. | ISO88591_1
+| `<>` | Sets character-set mapping that 
corresponds to the KANJI character set. | SJIS (which is shift-JIS, Japanese)
+| `<>` | Sets character-set mapping that 
corresponds to the KSC5601 character set. | ECU_KR (which is KS C 5601, ECU 
encoding, Korean)
+| `<>`   | Sets the language 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61675683
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/tracing_logging.adoc 
---
@@ -0,0 +1,195 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[tracing-and-logging-facilities]]
+= Tracing and Logging Facilities
+
+The Type 4 driver provides two tracing and logging facilities:
+
+* Standard JDBC tracing and logging functionality as defined by the JDBC 
standard
+* Type 4 driver logging facility
+
+Server-side tracing (logging) is enabled by configuring DCS.
+
+[[standard-jdbc-tracing-and-logging-facility]]
+== Standard JDBC Tracing and Logging Facility
+
+The JDBC standard provides a logging and tracing facility, which allows
+tracing JDBC method calls by setting the log writer. To set the log
+writer, either call the `setLogWriter()` method on the `DriverManager` 
class
+or call the `setLogWriter()` method on the `DataSource` class
+(or `ConnectionPoolDataSource` class).
+
+* A `DriverManager` log writer is a character output stream to which all
+logging and tracing messages for all connections made through the
+`DriverManager` are printed. This stream includes messages printed by the
+methods of this connection, messages printed by methods of other objects
+manufactured by the connection, and so on. The `DriverManager` log writer
+is initially null, that is, the default is for logging to be disabled.
+
+For information about using the setLogWriter method, see the

+https://docs.oracle.com/javase/7/docs/api/java/sql/DriverManager.html[DriverManager
 class API].
+
+* A `DataSource` log writer is a character output stream to which all
+logging and tracing messages for this data source are printed. This
+stream includes messages printed by the methods of this object, messages
+printed by methods of other objects manufactured by this object, and so
+on. Messages printed to a data-source-specific log writer are not
+printed to the log writer associated with the `java.sql.DriverManager`
+class. When a `DataSource` object is created, the log writer is initially
+null; that is, the default is for logging to be disabled.
+
+For information about using the setLogWriter method, see the

+https://docs.oracle.com/cd/E16338_01/appdev.112/e13995/oracle/jdbc/pool/OracleDataSource.html[DriverSource
 interface API].
+
+<<<
+[[the-type-4-driver-logging-facility]]
+== The Type 4 Driver Logging Facility
+
+
+The Type 4 driver Logging facility allows you to retrieve internal
+tracing information, which you can use in debugging the driver. It also
+allows you to capture error and warning messages.
+
+In addition to the standard JDBC tracing and logging facility, the Type
+4 driver provides an independent logging facility (Type 4 Driver
+Logging). The Type 4 Driver Logging provides the same level of logging
+and tracing as the standard JDBC tracing and logging facility with the
+following additional information:
+
+* More detail about the internals of the Type 4 driver and internal 
tracing information
+* Type 4 driver performance-tuning information
+* Finer control over the amount and type of logging information
+* Error and warning messages
+
+[[accessing-the-type-4-driver-logging-facility]]
+=== Accessing the Type 4 Driver Logging Facility
--- End diff --

Remove this section "Accessing the Type4 Driver Logging Facility"


---
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.
---

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61675650
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/tracing_logging.adoc 
---
@@ -0,0 +1,195 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[tracing-and-logging-facilities]]
+= Tracing and Logging Facilities
+
+The Type 4 driver provides two tracing and logging facilities:
+
+* Standard JDBC tracing and logging functionality as defined by the JDBC 
standard
+* Type 4 driver logging facility
+
+Server-side tracing (logging) is enabled by configuring DCS.
+
+[[standard-jdbc-tracing-and-logging-facility]]
+== Standard JDBC Tracing and Logging Facility
+
+The JDBC standard provides a logging and tracing facility, which allows
+tracing JDBC method calls by setting the log writer. To set the log
+writer, either call the `setLogWriter()` method on the `DriverManager` 
class
+or call the `setLogWriter()` method on the `DataSource` class
+(or `ConnectionPoolDataSource` class).
+
+* A `DriverManager` log writer is a character output stream to which all
+logging and tracing messages for all connections made through the
+`DriverManager` are printed. This stream includes messages printed by the
+methods of this connection, messages printed by methods of other objects
+manufactured by the connection, and so on. The `DriverManager` log writer
+is initially null, that is, the default is for logging to be disabled.
+
+For information about using the setLogWriter method, see the

+https://docs.oracle.com/javase/7/docs/api/java/sql/DriverManager.html[DriverManager
 class API].
+
+* A `DataSource` log writer is a character output stream to which all
+logging and tracing messages for this data source are printed. This
+stream includes messages printed by the methods of this object, messages
+printed by methods of other objects manufactured by this object, and so
+on. Messages printed to a data-source-specific log writer are not
+printed to the log writer associated with the `java.sql.DriverManager`
+class. When a `DataSource` object is created, the log writer is initially
+null; that is, the default is for logging to be disabled.
+
+For information about using the setLogWriter method, see the

+https://docs.oracle.com/cd/E16338_01/appdev.112/e13995/oracle/jdbc/pool/OracleDataSource.html[DriverSource
 interface API].
+
+<<<
+[[the-type-4-driver-logging-facility]]
+== The Type 4 Driver Logging Facility
+
+
+The Type 4 driver Logging facility allows you to retrieve internal
+tracing information, which you can use in debugging the driver. It also
+allows you to capture error and warning messages.
+
+In addition to the standard JDBC tracing and logging facility, the Type
+4 driver provides an independent logging facility (Type 4 Driver
+Logging). The Type 4 Driver Logging provides the same level of logging
+and tracing as the standard JDBC tracing and logging facility with the
+following additional information:
+
+* More detail about the internals of the Type 4 driver and internal 
tracing information
+* Type 4 driver performance-tuning information
+* Finer control over the amount and type of logging information
+* Error and warning messages
+
+[[accessing-the-type-4-driver-logging-facility]]
+=== Accessing the Type 4 Driver Logging Facility
+
+The Type 4 Driver Logging facility is based on the `java.util.logging`
+package. The Type 4 driver instantiates a `java.util.logging.Logger` class
+and names the logger `org.trafodion.jdbc.t4.logger`.
+
+Your JDBC program can access the Type 4 driver logger directly by
+calling the `java.util.logging.Logger` static method `getLogger(String)`.
+
+*example*
+
+[source, java]
+
+String t4Logger =
+   

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61675642
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/tracing_logging.adoc 
---
@@ -0,0 +1,195 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[tracing-and-logging-facilities]]
+= Tracing and Logging Facilities
+
+The Type 4 driver provides two tracing and logging facilities:
+
+* Standard JDBC tracing and logging functionality as defined by the JDBC 
standard
+* Type 4 driver logging facility
+
+Server-side tracing (logging) is enabled by configuring DCS.
+
+[[standard-jdbc-tracing-and-logging-facility]]
+== Standard JDBC Tracing and Logging Facility
+
+The JDBC standard provides a logging and tracing facility, which allows
+tracing JDBC method calls by setting the log writer. To set the log
+writer, either call the `setLogWriter()` method on the `DriverManager` 
class
+or call the `setLogWriter()` method on the `DataSource` class
+(or `ConnectionPoolDataSource` class).
+
+* A `DriverManager` log writer is a character output stream to which all
+logging and tracing messages for all connections made through the
+`DriverManager` are printed. This stream includes messages printed by the
+methods of this connection, messages printed by methods of other objects
+manufactured by the connection, and so on. The `DriverManager` log writer
+is initially null, that is, the default is for logging to be disabled.
+
+For information about using the setLogWriter method, see the

+https://docs.oracle.com/javase/7/docs/api/java/sql/DriverManager.html[DriverManager
 class API].
+
+* A `DataSource` log writer is a character output stream to which all
+logging and tracing messages for this data source are printed. This
+stream includes messages printed by the methods of this object, messages
+printed by methods of other objects manufactured by this object, and so
+on. Messages printed to a data-source-specific log writer are not
+printed to the log writer associated with the `java.sql.DriverManager`
+class. When a `DataSource` object is created, the log writer is initially
+null; that is, the default is for logging to be disabled.
+
+For information about using the setLogWriter method, see the

+https://docs.oracle.com/cd/E16338_01/appdev.112/e13995/oracle/jdbc/pool/OracleDataSource.html[DriverSource
 interface API].
+
+<<<
+[[the-type-4-driver-logging-facility]]
+== The Type 4 Driver Logging Facility
+
+
+The Type 4 driver Logging facility allows you to retrieve internal
+tracing information, which you can use in debugging the driver. It also
+allows you to capture error and warning messages.
+
+In addition to the standard JDBC tracing and logging facility, the Type
+4 driver provides an independent logging facility (Type 4 Driver
+Logging). The Type 4 Driver Logging provides the same level of logging
+and tracing as the standard JDBC tracing and logging facility with the
+following additional information:
+
+* More detail about the internals of the Type 4 driver and internal 
tracing information
+* Type 4 driver performance-tuning information
+* Finer control over the amount and type of logging information
+* Error and warning messages
+
+[[accessing-the-type-4-driver-logging-facility]]
+=== Accessing the Type 4 Driver Logging Facility
+
+The Type 4 Driver Logging facility is based on the `java.util.logging`
+package. The Type 4 driver instantiates a `java.util.logging.Logger` class
+and names the logger `org.trafodion.jdbc.t4.logger`.
+
+Your JDBC program can access the Type 4 driver logger directly by
+calling the `java.util.logging.Logger` static method `getLogger(String)`.
+
+*example*
+
+[source, java]
+
+String t4Logger =
+   

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61675603
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/tracing_logging.adoc 
---
@@ -0,0 +1,195 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[tracing-and-logging-facilities]]
+= Tracing and Logging Facilities
+
+The Type 4 driver provides two tracing and logging facilities:
+
+* Standard JDBC tracing and logging functionality as defined by the JDBC 
standard
+* Type 4 driver logging facility
+
+Server-side tracing (logging) is enabled by configuring DCS.
+
+[[standard-jdbc-tracing-and-logging-facility]]
+== Standard JDBC Tracing and Logging Facility
+
+The JDBC standard provides a logging and tracing facility, which allows
+tracing JDBC method calls by setting the log writer. To set the log
+writer, either call the `setLogWriter()` method on the `DriverManager` 
class
+or call the `setLogWriter()` method on the `DataSource` class
+(or `ConnectionPoolDataSource` class).
+
+* A `DriverManager` log writer is a character output stream to which all
+logging and tracing messages for all connections made through the
+`DriverManager` are printed. This stream includes messages printed by the
+methods of this connection, messages printed by methods of other objects
+manufactured by the connection, and so on. The `DriverManager` log writer
+is initially null, that is, the default is for logging to be disabled.
+
+For information about using the setLogWriter method, see the

+https://docs.oracle.com/javase/7/docs/api/java/sql/DriverManager.html[DriverManager
 class API].
+
+* A `DataSource` log writer is a character output stream to which all
+logging and tracing messages for this data source are printed. This
+stream includes messages printed by the methods of this object, messages
+printed by methods of other objects manufactured by this object, and so
+on. Messages printed to a data-source-specific log writer are not
+printed to the log writer associated with the `java.sql.DriverManager`
+class. When a `DataSource` object is created, the log writer is initially
+null; that is, the default is for logging to be disabled.
+
+For information about using the setLogWriter method, see the

+https://docs.oracle.com/cd/E16338_01/appdev.112/e13995/oracle/jdbc/pool/OracleDataSource.html[DriverSource
 interface API].
+
+<<<
+[[the-type-4-driver-logging-facility]]
+== The Type 4 Driver Logging Facility
+
+
+The Type 4 driver Logging facility allows you to retrieve internal
+tracing information, which you can use in debugging the driver. It also
+allows you to capture error and warning messages.
+
+In addition to the standard JDBC tracing and logging facility, the Type
+4 driver provides an independent logging facility (Type 4 Driver
+Logging). The Type 4 Driver Logging provides the same level of logging
+and tracing as the standard JDBC tracing and logging facility with the
+following additional information:
+
+* More detail about the internals of the Type 4 driver and internal 
tracing information
+* Type 4 driver performance-tuning information
+* Finer control over the amount and type of logging information
+* Error and warning messages
+
+[[accessing-the-type-4-driver-logging-facility]]
+=== Accessing the Type 4 Driver Logging Facility
+
+The Type 4 Driver Logging facility is based on the `java.util.logging`
+package. The Type 4 driver instantiates a `java.util.logging.Logger` class
+and names the logger `org.trafodion.jdbc.t4.logger`.
+
+Your JDBC program can access the Type 4 driver logger directly by
+calling the `java.util.logging.Logger` static method `getLogger(String)`.
+
+*example*
+
+[source, java]
+
+String t4Logger =
+   

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61675402
  
--- Diff: 
docs/jdbct4ref_guide/src/asciidoc/_chapters/properties_overview.adoc ---
@@ -0,0 +1,245 @@
+
+/**
+ *@@@ 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-properties]]
+= Type 4 Driver Properties
+
+[[summary-of-type-4-driver-properties]]
+== Summary of Type 4 Driver Properties
+
+Type 4 driver properties that effect client-side operations are
+summarized in the following tables. For the detailed description, click
+the link provided in the property name.
+
+NOTE: Unless otherwise noted in the brief description, the particular
+property applies to the `DataSource` object, `DriverManager` object, and
+`ConnectionPoolDataSource` object.
+
+[[client-side-properties]]
+=== Client-Side Properties
+
+*Connection-Control Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>`   | Specifies the registered 
DataSource or ConnectionPoolDataSource name. (Can be set only on the 
DriverManager object.) | None.
+| `<>`   | Sets the time limit that a 
connection can be attempted before the connection disconnects. | 60 (seconds)
+| `<>`   | Sets a time limit that the 
driver waits for a reply from the database server. | 0 (No network timeout is 
specified. 
+|===
+
+*Pooling Management Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>` | Sets the initial connection 
pool size when connection pooling is used with the Type 4 driver. (Ignored for
+connections made through the ConnectionPoolDataSource object.) | -1 (Do 
not create an initial connection pool.)
+| `<>` | Sets the number of seconds that 
a physical connection can remain unused in the pool before the connection is 
closed. | 0 (Specifies no limit.)
+| `<>` | Sets the maximum number of 
physical connections that the pool can contain. | -1 (Disables connection 
pooling.) 
+| `<>` | Sets the total number of 
PreparedStatement objects that the connection pool should cache. | 0 (Disables 
statement pooling.)
+| `<>` | Limits the number of physical 
connections that can be in the free connection pool. | -1 (The minPoolSize 
value is ignored.)
+|===
+
+
+*Operations on CLOB and BLOB Data*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>` | Specifies the LOB table for 
using BLOB columns. | None.
+| `<>` | Specifies the LOB table for 
using CLOB columns. | None.
+| `<>` | Sets the number of data 
locators to be reserved for a process that stores data in a LOB table. | 100 
+|===
+
+
+<<<
+*Internationalization Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>`   | Sets character-set mapping that 
corresponds to the ISO88591 character set. | ISO88591_1
+| `<>` | Sets character-set mapping that 
corresponds to the KANJI character set. | SJIS (which is shift-JIS, Japanese)
+| `<>` | Sets character-set mapping that 
corresponds to the KSC5601 character set. | ECU_KR (which is KS C 5601, ECU 
encoding, Korean)
+| `<>`   | Sets the language 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61675360
  
--- Diff: 
docs/jdbct4ref_guide/src/asciidoc/_chapters/properties_overview.adoc ---
@@ -0,0 +1,245 @@
+
+/**
+ *@@@ 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-properties]]
+= Type 4 Driver Properties
+
+[[summary-of-type-4-driver-properties]]
+== Summary of Type 4 Driver Properties
+
+Type 4 driver properties that effect client-side operations are
+summarized in the following tables. For the detailed description, click
+the link provided in the property name.
+
+NOTE: Unless otherwise noted in the brief description, the particular
+property applies to the `DataSource` object, `DriverManager` object, and
+`ConnectionPoolDataSource` object.
+
+[[client-side-properties]]
+=== Client-Side Properties
+
+*Connection-Control Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>`   | Specifies the registered 
DataSource or ConnectionPoolDataSource name. (Can be set only on the 
DriverManager object.) | None.
+| `<>`   | Sets the time limit that a 
connection can be attempted before the connection disconnects. | 60 (seconds)
+| `<>`   | Sets a time limit that the 
driver waits for a reply from the database server. | 0 (No network timeout is 
specified. 
+|===
+
+*Pooling Management Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>` | Sets the initial connection 
pool size when connection pooling is used with the Type 4 driver. (Ignored for
+connections made through the ConnectionPoolDataSource object.) | -1 (Do 
not create an initial connection pool.)
+| `<>` | Sets the number of seconds that 
a physical connection can remain unused in the pool before the connection is 
closed. | 0 (Specifies no limit.)
+| `<>` | Sets the maximum number of 
physical connections that the pool can contain. | -1 (Disables connection 
pooling.) 
+| `<>` | Sets the total number of 
PreparedStatement objects that the connection pool should cache. | 0 (Disables 
statement pooling.)
+| `<>` | Limits the number of physical 
connections that can be in the free connection pool. | -1 (The minPoolSize 
value is ignored.)
+|===
+
+
+*Operations on CLOB and BLOB Data*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>` | Specifies the LOB table for 
using BLOB columns. | None.
+| `<>` | Specifies the LOB table for 
using CLOB columns. | None.
+| `<>` | Sets the number of data 
locators to be reserved for a process that stores data in a LOB table. | 100 
+|===
+
+
+<<<
+*Internationalization Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>`   | Sets character-set mapping that 
corresponds to the ISO88591 character set. | ISO88591_1
+| `<>` | Sets character-set mapping that 
corresponds to the KANJI character set. | SJIS (which is shift-JIS, Japanese)
+| `<>` | Sets character-set mapping that 
corresponds to the KSC5601 character set. | ECU_KR (which is KS C 5601, ECU 
encoding, Korean)
+| `<>`   | Sets the language 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61675377
  
--- Diff: 
docs/jdbct4ref_guide/src/asciidoc/_chapters/properties_overview.adoc ---
@@ -0,0 +1,245 @@
+
+/**
+ *@@@ 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-properties]]
+= Type 4 Driver Properties
+
+[[summary-of-type-4-driver-properties]]
+== Summary of Type 4 Driver Properties
+
+Type 4 driver properties that effect client-side operations are
+summarized in the following tables. For the detailed description, click
+the link provided in the property name.
+
+NOTE: Unless otherwise noted in the brief description, the particular
+property applies to the `DataSource` object, `DriverManager` object, and
+`ConnectionPoolDataSource` object.
+
+[[client-side-properties]]
+=== Client-Side Properties
+
+*Connection-Control Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>`   | Specifies the registered 
DataSource or ConnectionPoolDataSource name. (Can be set only on the 
DriverManager object.) | None.
+| `<>`   | Sets the time limit that a 
connection can be attempted before the connection disconnects. | 60 (seconds)
+| `<>`   | Sets a time limit that the 
driver waits for a reply from the database server. | 0 (No network timeout is 
specified. 
+|===
+
+*Pooling Management Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>` | Sets the initial connection 
pool size when connection pooling is used with the Type 4 driver. (Ignored for
+connections made through the ConnectionPoolDataSource object.) | -1 (Do 
not create an initial connection pool.)
+| `<>` | Sets the number of seconds that 
a physical connection can remain unused in the pool before the connection is 
closed. | 0 (Specifies no limit.)
+| `<>` | Sets the maximum number of 
physical connections that the pool can contain. | -1 (Disables connection 
pooling.) 
+| `<>` | Sets the total number of 
PreparedStatement objects that the connection pool should cache. | 0 (Disables 
statement pooling.)
+| `<>` | Limits the number of physical 
connections that can be in the free connection pool. | -1 (The minPoolSize 
value is ignored.)
+|===
+
+
+*Operations on CLOB and BLOB Data*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>` | Specifies the LOB table for 
using BLOB columns. | None.
+| `<>` | Specifies the LOB table for 
using CLOB columns. | None.
+| `<>` | Sets the number of data 
locators to be reserved for a process that stores data in a LOB table. | 100 
+|===
+
+
+<<<
+*Internationalization Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>`   | Sets character-set mapping that 
corresponds to the ISO88591 character set. | ISO88591_1
+| `<>` | Sets character-set mapping that 
corresponds to the KANJI character set. | SJIS (which is shift-JIS, Japanese)
+| `<>` | Sets character-set mapping that 
corresponds to the KSC5601 character set. | ECU_KR (which is KS C 5601, ECU 
encoding, Korean)
+| `<>`   | Sets the language 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61675346
  
--- Diff: 
docs/jdbct4ref_guide/src/asciidoc/_chapters/properties_overview.adoc ---
@@ -0,0 +1,245 @@
+
+/**
+ *@@@ 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-properties]]
+= Type 4 Driver Properties
+
+[[summary-of-type-4-driver-properties]]
+== Summary of Type 4 Driver Properties
+
+Type 4 driver properties that effect client-side operations are
+summarized in the following tables. For the detailed description, click
+the link provided in the property name.
+
+NOTE: Unless otherwise noted in the brief description, the particular
+property applies to the `DataSource` object, `DriverManager` object, and
+`ConnectionPoolDataSource` object.
+
+[[client-side-properties]]
+=== Client-Side Properties
+
+*Connection-Control Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>`   | Specifies the registered 
DataSource or ConnectionPoolDataSource name. (Can be set only on the 
DriverManager object.) | None.
+| `<>`   | Sets the time limit that a 
connection can be attempted before the connection disconnects. | 60 (seconds)
+| `<>`   | Sets a time limit that the 
driver waits for a reply from the database server. | 0 (No network timeout is 
specified. 
+|===
+
+*Pooling Management Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>` | Sets the initial connection 
pool size when connection pooling is used with the Type 4 driver. (Ignored for
+connections made through the ConnectionPoolDataSource object.) | -1 (Do 
not create an initial connection pool.)
+| `<>` | Sets the number of seconds that 
a physical connection can remain unused in the pool before the connection is 
closed. | 0 (Specifies no limit.)
+| `<>` | Sets the maximum number of 
physical connections that the pool can contain. | -1 (Disables connection 
pooling.) 
+| `<>` | Sets the total number of 
PreparedStatement objects that the connection pool should cache. | 0 (Disables 
statement pooling.)
+| `<>` | Limits the number of physical 
connections that can be in the free connection pool. | -1 (The minPoolSize 
value is ignored.)
+|===
+
+
+*Operations on CLOB and BLOB Data*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>` | Specifies the LOB table for 
using BLOB columns. | None.
+| `<>` | Specifies the LOB table for 
using CLOB columns. | None.
+| `<>` | Sets the number of data 
locators to be reserved for a process that stores data in a LOB table. | 100 
+|===
+
+
+<<<
+*Internationalization Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>`   | Sets character-set mapping that 
corresponds to the ISO88591 character set. | ISO88591_1
+| `<>` | Sets character-set mapping that 
corresponds to the KANJI character set. | SJIS (which is shift-JIS, Japanese)
+| `<>` | Sets character-set mapping that 
corresponds to the KSC5601 character set. | ECU_KR (which is KS C 5601, ECU 
encoding, Korean)
+| `<>`   | Sets the language 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61675332
  
--- Diff: 
docs/jdbct4ref_guide/src/asciidoc/_chapters/properties_overview.adoc ---
@@ -0,0 +1,245 @@
+
+/**
+ *@@@ 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-properties]]
+= Type 4 Driver Properties
+
+[[summary-of-type-4-driver-properties]]
+== Summary of Type 4 Driver Properties
+
+Type 4 driver properties that effect client-side operations are
+summarized in the following tables. For the detailed description, click
+the link provided in the property name.
+
+NOTE: Unless otherwise noted in the brief description, the particular
+property applies to the `DataSource` object, `DriverManager` object, and
+`ConnectionPoolDataSource` object.
+
+[[client-side-properties]]
+=== Client-Side Properties
+
+*Connection-Control Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>`   | Specifies the registered 
DataSource or ConnectionPoolDataSource name. (Can be set only on the 
DriverManager object.) | None.
+| `<>`   | Sets the time limit that a 
connection can be attempted before the connection disconnects. | 60 (seconds)
+| `<>`   | Sets a time limit that the 
driver waits for a reply from the database server. | 0 (No network timeout is 
specified. 
+|===
+
+*Pooling Management Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>` | Sets the initial connection 
pool size when connection pooling is used with the Type 4 driver. (Ignored for
+connections made through the ConnectionPoolDataSource object.) | -1 (Do 
not create an initial connection pool.)
+| `<>` | Sets the number of seconds that 
a physical connection can remain unused in the pool before the connection is 
closed. | 0 (Specifies no limit.)
+| `<>` | Sets the maximum number of 
physical connections that the pool can contain. | -1 (Disables connection 
pooling.) 
+| `<>` | Sets the total number of 
PreparedStatement objects that the connection pool should cache. | 0 (Disables 
statement pooling.)
+| `<>` | Limits the number of physical 
connections that can be in the free connection pool. | -1 (The minPoolSize 
value is ignored.)
+|===
+
+
+*Operations on CLOB and BLOB Data*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>` | Specifies the LOB table for 
using BLOB columns. | None.
+| `<>` | Specifies the LOB table for 
using CLOB columns. | None.
+| `<>` | Sets the number of data 
locators to be reserved for a process that stores data in a LOB table. | 100 
+|===
+
+
+<<<
+*Internationalization Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>`   | Sets character-set mapping that 
corresponds to the ISO88591 character set. | ISO88591_1
+| `<>` | Sets character-set mapping that 
corresponds to the KANJI character set. | SJIS (which is shift-JIS, Japanese)
+| `<>` | Sets character-set mapping that 
corresponds to the KSC5601 character set. | ECU_KR (which is KS C 5601, ECU 
encoding, Korean)
+| `<>`   | Sets the language 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61675315
  
--- Diff: 
docs/jdbct4ref_guide/src/asciidoc/_chapters/properties_overview.adoc ---
@@ -0,0 +1,245 @@
+
+/**
+ *@@@ 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-properties]]
+= Type 4 Driver Properties
+
+[[summary-of-type-4-driver-properties]]
+== Summary of Type 4 Driver Properties
+
+Type 4 driver properties that effect client-side operations are
+summarized in the following tables. For the detailed description, click
+the link provided in the property name.
+
+NOTE: Unless otherwise noted in the brief description, the particular
+property applies to the `DataSource` object, `DriverManager` object, and
+`ConnectionPoolDataSource` object.
+
+[[client-side-properties]]
+=== Client-Side Properties
+
+*Connection-Control Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>`   | Specifies the registered 
DataSource or ConnectionPoolDataSource name. (Can be set only on the 
DriverManager object.) | None.
+| `<>`   | Sets the time limit that a 
connection can be attempted before the connection disconnects. | 60 (seconds)
+| `<>`   | Sets a time limit that the 
driver waits for a reply from the database server. | 0 (No network timeout is 
specified. 
+|===
+
+*Pooling Management Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>` | Sets the initial connection 
pool size when connection pooling is used with the Type 4 driver. (Ignored for
+connections made through the ConnectionPoolDataSource object.) | -1 (Do 
not create an initial connection pool.)
+| `<>` | Sets the number of seconds that 
a physical connection can remain unused in the pool before the connection is 
closed. | 0 (Specifies no limit.)
+| `<>` | Sets the maximum number of 
physical connections that the pool can contain. | -1 (Disables connection 
pooling.) 
+| `<>` | Sets the total number of 
PreparedStatement objects that the connection pool should cache. | 0 (Disables 
statement pooling.)
+| `<>` | Limits the number of physical 
connections that can be in the free connection pool. | -1 (The minPoolSize 
value is ignored.)
+|===
+
+
+*Operations on CLOB and BLOB Data*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>` | Specifies the LOB table for 
using BLOB columns. | None.
+| `<>` | Specifies the LOB table for 
using CLOB columns. | None.
+| `<>` | Sets the number of data 
locators to be reserved for a process that stores data in a LOB table. | 100 
+|===
+
+
+<<<
+*Internationalization Properties*
+[cols="25%,55%,30%",options="header" ]
+|===
+| Property Name  | Description | Default Value
+| `<>`   | Sets character-set mapping that 
corresponds to the ISO88591 character set. | ISO88591_1
+| `<>` | Sets character-set mapping that 
corresponds to the KANJI character set. | SJIS (which is shift-JIS, Japanese)
+| `<>` | Sets character-set mapping that 
corresponds to the KSC5601 character set. | ECU_KR (which is KS C 5601, ECU 
encoding, Korean)
+| `<>`   | Sets the language 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61673431
  
--- 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
+<>.
+
+
+[[blobtablename]]
+== blobTableName Property
+
+See <>.
+
+
+[[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
+<>.
+
+```
+Data type: String
+
+Default: none
+```
+
+*Example*
+
+Specifying the catalog Seabase:
+
+```
+catalog=Seabase
+```
+
+
+[[clobtablename]]
+== clobTableName Property
+
+See <>.
+
+
+<<<
+[[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
+<>.
+
+```
+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
+<>.
+
+```
+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 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61673429
  
--- 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
+<>.
+
+
+[[blobtablename]]
+== blobTableName Property
+
+See <>.
+
+
+[[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
+<>.
+
+```
+Data type: String
+
+Default: none
+```
+
+*Example*
+
+Specifying the catalog Seabase:
+
+```
+catalog=Seabase
+```
+
+
+[[clobtablename]]
+== clobTableName Property
+
+See <>.
+
+
+<<<
+[[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
+<>.
+
+```
+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
+<>.
+
+```
+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 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61673433
  
--- 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
+<>.
+
+
+[[blobtablename]]
+== blobTableName Property
+
+See <>.
+
+
+[[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
+<>.
+
+```
+Data type: String
+
+Default: none
+```
+
+*Example*
+
+Specifying the catalog Seabase:
+
+```
+catalog=Seabase
+```
+
+
+[[clobtablename]]
+== clobTableName Property
+
+See <>.
+
+
+<<<
+[[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
+<>.
+
+```
+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
+<>.
+
+```
+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 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61673413
  
--- 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
+<>.
+
+
+[[blobtablename]]
+== blobTableName Property
+
+See <>.
+
+
+[[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
+<>.
+
+```
+Data type: String
+
+Default: none
+```
+
+*Example*
+
+Specifying the catalog Seabase:
+
+```
+catalog=Seabase
+```
+
+
+[[clobtablename]]
+== clobTableName Property
+
+See <>.
+
+
+<<<
+[[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
+<>.
+
+```
+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
+<>.
+
+```
+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 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61673404
  
--- 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
+<>.
+
+
+[[blobtablename]]
+== blobTableName Property
+
+See <>.
+
+
+[[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
+<>.
+
+```
+Data type: String
+
+Default: none
+```
+
+*Example*
+
+Specifying the catalog Seabase:
+
+```
+catalog=Seabase
+```
+
+
+[[clobtablename]]
+== clobTableName Property
+
+See <>.
+
+
+<<<
+[[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
+<>.
+
+```
+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
+<>.
+
+```
+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 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

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
+<>.
+
+
+[[blobtablename]]
+== blobTableName Property
+
+See <>.
+
+
+[[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
+<>.
+
+```
+Data type: String
+
+Default: none
+```
+
+*Example*
+
+Specifying the catalog Seabase:
+
+```
+catalog=Seabase
+```
+
+
+[[clobtablename]]
+== clobTableName Property
+
+See <>.
+
+
+<<<
+[[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
+<>.
+
+```
+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
+<>.
+
+```
+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 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61673384
  
--- 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
+<>.
+
+
+[[blobtablename]]
+== blobTableName Property
+
+See <>.
+
+
+[[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
+<>.
+
+```
+Data type: String
+
+Default: none
+```
+
+*Example*
+
+Specifying the catalog Seabase:
+
+```
+catalog=Seabase
--- 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.
---

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61673378
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/introduction.adoc ---
@@ -0,0 +1,53 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[introduction]]
+= Introduction
+
+This document describes how to use the {project-name} JDBC Type 4
+Driver. This driver provides Java applications running on a foreign
+platform with JDBC access to {project-name} SQL databases on the
+{project-name}.
+
+*Supported Java Releases:* The Type 4 driver requires Java enabled
+platforms that support JDK 1.4.1 or higher.
+
+
+[[type-4-driver-api-package]]
+== Type 4 Driver API Package
+
+The Type 4 driver package, `org.trafodion.t4jdbc`, is shipped with the
+driver software. For class and method descriptions, see the
+_{project-name} JDBC Type 4 Driver API Reference_.
+
+The {project-name} JDBC Type 4 Driver (hereafter, Type 4 driver)
+implements JDBC technology that conforms to the standard JDBC 3.0 Data
+Access API.
+
+To obtain detailed information on the standard JDBC API, download the
+JDBC API documentation: http://docs.oracle.com/en/java/.
--- End diff --

This is the latest link I can find to Java documentation. Please suggest an 
alternative.


---
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.
---

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61673374
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/introduction.adoc ---
@@ -0,0 +1,53 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[introduction]]
+= Introduction
+
+This document describes how to use the {project-name} JDBC Type 4
+Driver. This driver provides Java applications running on a foreign
+platform with JDBC access to {project-name} SQL databases on the
+{project-name}.
+
+*Supported Java Releases:* The Type 4 driver requires Java enabled
+platforms that support JDK 1.4.1 or higher.
+
+
+[[type-4-driver-api-package]]
+== Type 4 Driver API Package
+
+The Type 4 driver package, `org.trafodion.t4jdbc`, is shipped with the
--- 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.
---

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61673285
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/compliance.adoc ---
@@ -0,0 +1,386 @@
+
+/**
+ *@@@ 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-compliance]]
+= Type 4 Driver Compliance
+
+[[compliance-overview]]
+== Compliance Overview
+
+The Type 4 driver conforms where applicable to the JDBC
+3.0 API specification. However, this driver differs from the JDBC
+standard in some ways. This subsection describes the JDBC methods that
+are not supported, the methods and features that deviate from the
+specification, and features that are {project-name} extensions to the JDBC 
standard.
+JDBC features that conform to the specification are not described in this 
subsection.
+
+In addition, this chapter lists features of {project-name} SQL that are 
not supported by the {project-name} JDBC Type 4 driver, other
+unsupported features, and restrictions.
+
+[[unsupported-features]]
+== Unsupported Features
+
+These methods in the java.sql package throw an SQLException with the
+message `Unsupported feature - `:
+
+[cols="65%,35%", options="header"]
+|===
+| Method   | Comments
+| `CallableStatement.getArray(int parameterIndex)` +
+`CallableStatement.getArray(String parameterName)` +
+`CallableStatement.getBlob(int parameterIndex)` +
+`CallableStatement.getBlob(String parameterName)` +
+`CallableStatement.getClob(int parameterIndex)` +
+`CallableStatement.getClob(String parameterName)` +
+`CallableStatement.getObject(int parameterIndex, Map map)` +
+`CallableStatement.getObject(String parameterName, Map map)` +
+`CallableStatement.getRef(int parameterIndex)` +
+`CallableStatement.getRef(String parameterName)` +
+`CallableStatement.getURL(int parameterIndex)` +
+`CallableStatement.getURL(String parameterName)` +
+`CallableStatement.executeBatch()` | The particular `CallableStatement` 
method is not supported.
+| `Connection.releaseSavepoint(Savepoint savepoint)` +
+`Connection.rollback(Savepoint savepoint)` +
+`Connection.setSavepoint()` +
+`Connection.setSavepoint(String name)` | The particular `Connection` 
methods are not supported.
+| `PreparedStatement.setArray(int parameterIndex, Array x)` +
+`PreparedStatement.setRef(int parameterIndex, Ref x)` +
+`PreparedStatement.setURL(int parameterIndex, URL x)` | The particular 
`PreparedStatement` methods are not supported.
+| `ResultSet.getArray(int columnIndex)` +
+`ResultSet.getArray(String columnName)` +
+`ResultSet.getObject(int columnIndex, Map map)` +
+`ResultSet.getObject(String columnName, Map map)` +
+`ResultSet.getRef(int columnIndex)ResultSet.getRef(String columnName)` +
+`ResultSet.getURL(int columnIndex)` +
+`ResultSet.getURL(String columnName)` +
+`ResultSet.updateArray(int columnIndex)` +
+`ResultSet.updateArray(String columnName)` +
+`ResultSet.updateRef(int columnIndex)` +
+`ResultSet.updateRef(String columnName) | The particular `ResultSet` 
methods are not supported.
+| `Statement.getQueryTimeout()` +
+`Statement.setQueryTimeout()` | The particular `Statement` methods are not 
supported.
+|===
+
+The following methods in the java.sql package throw an SQLException with
+the message `Auto generated keys not supported`:
+
+[cols="65%,35%", options="header" ]
+|===
+| Method   | Comments
+| `Connection.prepareStatement(String sql, int autoGeneratedKeys)` +
+`Connection.prepareStatement(String sql, int[] columnIndexes)` +
+`Connection.prepareStatement(String sql, String[] columnNames)` | 
Automatically generated keys are not supported.
+| `Statement.executeUpdate(String sql, int autoGeneratedKeys)` +
+`Statement.executeUpdate(String sql, int[] 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61673257
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/compliance.adoc ---
@@ -0,0 +1,386 @@
+
+/**
+ *@@@ 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-compliance]]
+= Type 4 Driver Compliance
+
+[[compliance-overview]]
+== Compliance Overview
+
+The Type 4 driver conforms where applicable to the JDBC
+3.0 API specification. However, this driver differs from the JDBC
+standard in some ways. This subsection describes the JDBC methods that
+are not supported, the methods and features that deviate from the
+specification, and features that are {project-name} extensions to the JDBC 
standard.
+JDBC features that conform to the specification are not described in this 
subsection.
+
+In addition, this chapter lists features of {project-name} SQL that are 
not supported by the {project-name} JDBC Type 4 driver, other
+unsupported features, and restrictions.
+
+[[unsupported-features]]
+== Unsupported Features
+
+These methods in the java.sql package throw an SQLException with the
+message `Unsupported feature - `:
+
+[cols="65%,35%", options="header"]
+|===
+| Method   | Comments
+| `CallableStatement.getArray(int parameterIndex)` +
+`CallableStatement.getArray(String parameterName)` +
+`CallableStatement.getBlob(int parameterIndex)` +
+`CallableStatement.getBlob(String parameterName)` +
+`CallableStatement.getClob(int parameterIndex)` +
+`CallableStatement.getClob(String parameterName)` +
+`CallableStatement.getObject(int parameterIndex, Map map)` +
+`CallableStatement.getObject(String parameterName, Map map)` +
+`CallableStatement.getRef(int parameterIndex)` +
+`CallableStatement.getRef(String parameterName)` +
+`CallableStatement.getURL(int parameterIndex)` +
+`CallableStatement.getURL(String parameterName)` +
+`CallableStatement.executeBatch()` | The particular `CallableStatement` 
method is not supported.
+| `Connection.releaseSavepoint(Savepoint savepoint)` +
+`Connection.rollback(Savepoint savepoint)` +
+`Connection.setSavepoint()` +
+`Connection.setSavepoint(String name)` | The particular `Connection` 
methods are not supported.
+| `PreparedStatement.setArray(int parameterIndex, Array x)` +
+`PreparedStatement.setRef(int parameterIndex, Ref x)` +
+`PreparedStatement.setURL(int parameterIndex, URL x)` | The particular 
`PreparedStatement` methods are not supported.
+| `ResultSet.getArray(int columnIndex)` +
+`ResultSet.getArray(String columnName)` +
+`ResultSet.getObject(int columnIndex, Map map)` +
+`ResultSet.getObject(String columnName, Map map)` +
+`ResultSet.getRef(int columnIndex)ResultSet.getRef(String columnName)` +
+`ResultSet.getURL(int columnIndex)` +
+`ResultSet.getURL(String columnName)` +
+`ResultSet.updateArray(int columnIndex)` +
+`ResultSet.updateArray(String columnName)` +
+`ResultSet.updateRef(int columnIndex)` +
+`ResultSet.updateRef(String columnName) | The particular `ResultSet` 
methods are not supported.
+| `Statement.getQueryTimeout()` +
+`Statement.setQueryTimeout()` | The particular `Statement` methods are not 
supported.
+|===
+
+The following methods in the java.sql package throw an SQLException with
+the message `Auto generated keys not supported`:
+
+[cols="65%,35%", options="header" ]
+|===
+| Method   | Comments
+| `Connection.prepareStatement(String sql, int autoGeneratedKeys)` +
+`Connection.prepareStatement(String sql, int[] columnIndexes)` +
+`Connection.prepareStatement(String sql, String[] columnNames)` | 
Automatically generated keys are not supported.
+| `Statement.executeUpdate(String sql, int autoGeneratedKeys)` +
+`Statement.executeUpdate(String sql, int[] 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61673245
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/compliance.adoc ---
@@ -0,0 +1,386 @@
+
+/**
+ *@@@ 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-compliance]]
+= Type 4 Driver Compliance
+
+[[compliance-overview]]
+== Compliance Overview
+
+The Type 4 driver conforms where applicable to the JDBC
+3.0 API specification. However, this driver differs from the JDBC
+standard in some ways. This subsection describes the JDBC methods that
+are not supported, the methods and features that deviate from the
+specification, and features that are {project-name} extensions to the JDBC 
standard.
+JDBC features that conform to the specification are not described in this 
subsection.
+
+In addition, this chapter lists features of {project-name} SQL that are 
not supported by the {project-name} JDBC Type 4 driver, other
+unsupported features, and restrictions.
+
+[[unsupported-features]]
+== Unsupported Features
+
+These methods in the java.sql package throw an SQLException with the
+message `Unsupported feature - `:
+
+[cols="65%,35%", options="header"]
+|===
+| Method   | Comments
+| `CallableStatement.getArray(int parameterIndex)` +
+`CallableStatement.getArray(String parameterName)` +
+`CallableStatement.getBlob(int parameterIndex)` +
+`CallableStatement.getBlob(String parameterName)` +
+`CallableStatement.getClob(int parameterIndex)` +
+`CallableStatement.getClob(String parameterName)` +
+`CallableStatement.getObject(int parameterIndex, Map map)` +
+`CallableStatement.getObject(String parameterName, Map map)` +
+`CallableStatement.getRef(int parameterIndex)` +
+`CallableStatement.getRef(String parameterName)` +
+`CallableStatement.getURL(int parameterIndex)` +
+`CallableStatement.getURL(String parameterName)` +
+`CallableStatement.executeBatch()` | The particular `CallableStatement` 
method is not supported.
+| `Connection.releaseSavepoint(Savepoint savepoint)` +
+`Connection.rollback(Savepoint savepoint)` +
+`Connection.setSavepoint()` +
+`Connection.setSavepoint(String name)` | The particular `Connection` 
methods are not supported.
+| `PreparedStatement.setArray(int parameterIndex, Array x)` +
+`PreparedStatement.setRef(int parameterIndex, Ref x)` +
+`PreparedStatement.setURL(int parameterIndex, URL x)` | The particular 
`PreparedStatement` methods are not supported.
+| `ResultSet.getArray(int columnIndex)` +
+`ResultSet.getArray(String columnName)` +
+`ResultSet.getObject(int columnIndex, Map map)` +
+`ResultSet.getObject(String columnName, Map map)` +
+`ResultSet.getRef(int columnIndex)ResultSet.getRef(String columnName)` +
+`ResultSet.getURL(int columnIndex)` +
+`ResultSet.getURL(String columnName)` +
+`ResultSet.updateArray(int columnIndex)` +
+`ResultSet.updateArray(String columnName)` +
+`ResultSet.updateRef(int columnIndex)` +
+`ResultSet.updateRef(String columnName) | The particular `ResultSet` 
methods are not supported.
+| `Statement.getQueryTimeout()` +
+`Statement.setQueryTimeout()` | The particular `Statement` methods are not 
supported.
+|===
+
+The following methods in the java.sql package throw an SQLException with
+the message `Auto generated keys not supported`:
+
+[cols="65%,35%", options="header" ]
+|===
+| Method   | Comments
+| `Connection.prepareStatement(String sql, int autoGeneratedKeys)` +
+`Connection.prepareStatement(String sql, int[] columnIndexes)` +
+`Connection.prepareStatement(String sql, String[] columnNames)` | 
Automatically generated keys are not supported.
+| `Statement.executeUpdate(String sql, int autoGeneratedKeys)` +
+`Statement.executeUpdate(String sql, int[] 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61673207
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/accessing.adoc ---
@@ -0,0 +1,910 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[accessing-project-name-sql-databases]]
+= Accessing {project-name} SQL Databases
+
+[[data-sources]]
+== Data Sources
+
+The term *data source* logically refers to a database or other data
+storage entity. A JDBC (client) data source is physically a Java object 
that
+contains properties such as the URL of the physical database, the
+catalog to use when connecting to this database, and the schema to use
+when connecting to this database. The JDBC data source also contains
+methods for obtaining a JDBC connection to the underlying database.
+
+[[jdbc-data-source-client-side]]
+=== JDBC Data Source (client-side)
+
+All JDBC data source classes implement either the `javax.sql.DataSource`
+interface or the `javax.sql.ConnectionPoolDataSource` interface. The Type
+4 driver data source classes are `org.trafodion.t4jdbc.HPT4DataSource` and
+`org.trafodion.t4jdbc.HPT4ConnectionPoolDataSource`. (These classes are
+defined by the JDBC 3.0 specification.)
+
+Typically, a user or system administrator uses a tool to create a data
+source, and then registers the data source by using a JNDI service
+provider. At run time, a user application typically retrieves the data
+source through JNDI, and uses the data source's methods to establish a
+connection to the underlying database.
+
+A DataSource object maps to an instance of a database. In the Type 4
+driver product, the DataSource object acts as an interface between the
+application code and the database and enables connection with an DCS
+data source.
+
+[[security]]
+== Security
+
+Clients connect to the {project-name} platform with a valid user name
+and ID, using standard JDBC 3.0 APIs. An application can make multiple
+connections using different user IDs, and creating different Connection
+objects.
+
+The Type 4 driver provides for user name and password authentication.
+The password is encrypted with a proprietary algorithm provided by DCS.
+
+NOTE: There is no secure wire communication such as SSL provided for the
+communication between Type 4 driver and the {project-name} platform.
+
+<<<
+[[connection-by-using-the-datasource-interface]]
+== Connection by Using the DataSource Interface
+
+The `javax.sql.DataSource` interface is the preferred way to establish a
+connection to the database because this interface enhances the application
+portability. Portability is achieved by allowing the application to use a
+logical name for a data source instead of providing driver-specific 
information
+in the application. A logical name is mapped to a `javax.sql.DataSource`
+object through a naming service that uses the Java Naming and Directory
+Interface (JNDI). Using this DataSource method is particularly recommended
+for application servers.
+
+When an application requests a connection by using the `getConnection` 
method
+in the `DataSource`, then the method returns a `Connection` object.
+
+A `DataSource` object is a factory for `Connection` objects. An object that
+implements the `DataSource` interface is typically registered with a JNDI
+service provider.
+
+[[overview-of-tasks-to-deploy-datasource-objects]]
+=== Overview of Tasks to Deploy DataSource Objects
+
+Before an application can connect to a `DataSource` object, typically
+the system administrator deploys the `DataSource` object so that
+the application programmers can start using it.
+
+Data source properties are usually set by a system administrator using
+a GUI tool as part of the installation of the data 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61673153
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/accessing.adoc ---
@@ -0,0 +1,910 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[accessing-project-name-sql-databases]]
+= Accessing {project-name} SQL Databases
+
+[[data-sources]]
+== Data Sources
+
+The term *data source* logically refers to a database or other data
+storage entity. A JDBC (client) data source is physically a Java object 
that
+contains properties such as the URL of the physical database, the
+catalog to use when connecting to this database, and the schema to use
+when connecting to this database. The JDBC data source also contains
+methods for obtaining a JDBC connection to the underlying database.
+
+[[jdbc-data-source-client-side]]
+=== JDBC Data Source (client-side)
+
+All JDBC data source classes implement either the `javax.sql.DataSource`
+interface or the `javax.sql.ConnectionPoolDataSource` interface. The Type
+4 driver data source classes are `org.trafodion.t4jdbc.HPT4DataSource` and
+`org.trafodion.t4jdbc.HPT4ConnectionPoolDataSource`. (These classes are
+defined by the JDBC 3.0 specification.)
+
+Typically, a user or system administrator uses a tool to create a data
+source, and then registers the data source by using a JNDI service
+provider. At run time, a user application typically retrieves the data
+source through JNDI, and uses the data source's methods to establish a
+connection to the underlying database.
+
+A DataSource object maps to an instance of a database. In the Type 4
+driver product, the DataSource object acts as an interface between the
+application code and the database and enables connection with an DCS
+data source.
+
+[[security]]
+== Security
+
+Clients connect to the {project-name} platform with a valid user name
+and ID, using standard JDBC 3.0 APIs. An application can make multiple
+connections using different user IDs, and creating different Connection
+objects.
+
+The Type 4 driver provides for user name and password authentication.
+The password is encrypted with a proprietary algorithm provided by DCS.
+
+NOTE: There is no secure wire communication such as SSL provided for the
+communication between Type 4 driver and the {project-name} platform.
+
+<<<
+[[connection-by-using-the-datasource-interface]]
+== Connection by Using the DataSource Interface
+
+The `javax.sql.DataSource` interface is the preferred way to establish a
+connection to the database because this interface enhances the application
+portability. Portability is achieved by allowing the application to use a
+logical name for a data source instead of providing driver-specific 
information
+in the application. A logical name is mapped to a `javax.sql.DataSource`
+object through a naming service that uses the Java Naming and Directory
+Interface (JNDI). Using this DataSource method is particularly recommended
+for application servers.
+
+When an application requests a connection by using the `getConnection` 
method
+in the `DataSource`, then the method returns a `Connection` object.
+
+A `DataSource` object is a factory for `Connection` objects. An object that
+implements the `DataSource` interface is typically registered with a JNDI
+service provider.
+
+[[overview-of-tasks-to-deploy-datasource-objects]]
+=== Overview of Tasks to Deploy DataSource Objects
+
+Before an application can connect to a `DataSource` object, typically
+the system administrator deploys the `DataSource` object so that
+the application programmers can start using it.
+
+Data source properties are usually set by a system administrator using
+a GUI tool as part of the installation of the data 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61673132
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/accessing.adoc ---
@@ -0,0 +1,910 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[accessing-project-name-sql-databases]]
+= Accessing {project-name} SQL Databases
+
+[[data-sources]]
+== Data Sources
+
+The term *data source* logically refers to a database or other data
+storage entity. A JDBC (client) data source is physically a Java object 
that
+contains properties such as the URL of the physical database, the
+catalog to use when connecting to this database, and the schema to use
+when connecting to this database. The JDBC data source also contains
+methods for obtaining a JDBC connection to the underlying database.
+
+[[jdbc-data-source-client-side]]
+=== JDBC Data Source (client-side)
+
+All JDBC data source classes implement either the `javax.sql.DataSource`
+interface or the `javax.sql.ConnectionPoolDataSource` interface. The Type
+4 driver data source classes are `org.trafodion.t4jdbc.HPT4DataSource` and
+`org.trafodion.t4jdbc.HPT4ConnectionPoolDataSource`. (These classes are
+defined by the JDBC 3.0 specification.)
+
+Typically, a user or system administrator uses a tool to create a data
+source, and then registers the data source by using a JNDI service
+provider. At run time, a user application typically retrieves the data
+source through JNDI, and uses the data source's methods to establish a
+connection to the underlying database.
+
+A DataSource object maps to an instance of a database. In the Type 4
+driver product, the DataSource object acts as an interface between the
+application code and the database and enables connection with an DCS
+data source.
+
+[[security]]
+== Security
+
+Clients connect to the {project-name} platform with a valid user name
+and ID, using standard JDBC 3.0 APIs. An application can make multiple
+connections using different user IDs, and creating different Connection
+objects.
+
+The Type 4 driver provides for user name and password authentication.
+The password is encrypted with a proprietary algorithm provided by DCS.
+
+NOTE: There is no secure wire communication such as SSL provided for the
+communication between Type 4 driver and the {project-name} platform.
+
+<<<
+[[connection-by-using-the-datasource-interface]]
+== Connection by Using the DataSource Interface
+
+The `javax.sql.DataSource` interface is the preferred way to establish a
+connection to the database because this interface enhances the application
+portability. Portability is achieved by allowing the application to use a
+logical name for a data source instead of providing driver-specific 
information
+in the application. A logical name is mapped to a `javax.sql.DataSource`
+object through a naming service that uses the Java Naming and Directory
+Interface (JNDI). Using this DataSource method is particularly recommended
+for application servers.
+
+When an application requests a connection by using the `getConnection` 
method
+in the `DataSource`, then the method returns a `Connection` object.
+
+A `DataSource` object is a factory for `Connection` objects. An object that
+implements the `DataSource` interface is typically registered with a JNDI
+service provider.
+
+[[overview-of-tasks-to-deploy-datasource-objects]]
+=== Overview of Tasks to Deploy DataSource Objects
+
+Before an application can connect to a `DataSource` object, typically
+the system administrator deploys the `DataSource` object so that
+the application programmers can start using it.
+
+Data source properties are usually set by a system administrator using
+a GUI tool as part of the installation of the data 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61673129
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/accessing.adoc ---
@@ -0,0 +1,910 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[accessing-project-name-sql-databases]]
+= Accessing {project-name} SQL Databases
+
+[[data-sources]]
+== Data Sources
+
+The term *data source* logically refers to a database or other data
+storage entity. A JDBC (client) data source is physically a Java object 
that
+contains properties such as the URL of the physical database, the
+catalog to use when connecting to this database, and the schema to use
+when connecting to this database. The JDBC data source also contains
+methods for obtaining a JDBC connection to the underlying database.
+
+[[jdbc-data-source-client-side]]
+=== JDBC Data Source (client-side)
+
+All JDBC data source classes implement either the `javax.sql.DataSource`
+interface or the `javax.sql.ConnectionPoolDataSource` interface. The Type
+4 driver data source classes are `org.trafodion.t4jdbc.HPT4DataSource` and
+`org.trafodion.t4jdbc.HPT4ConnectionPoolDataSource`. (These classes are
+defined by the JDBC 3.0 specification.)
+
+Typically, a user or system administrator uses a tool to create a data
+source, and then registers the data source by using a JNDI service
+provider. At run time, a user application typically retrieves the data
+source through JNDI, and uses the data source's methods to establish a
+connection to the underlying database.
+
+A DataSource object maps to an instance of a database. In the Type 4
+driver product, the DataSource object acts as an interface between the
+application code and the database and enables connection with an DCS
+data source.
+
+[[security]]
+== Security
+
+Clients connect to the {project-name} platform with a valid user name
+and ID, using standard JDBC 3.0 APIs. An application can make multiple
+connections using different user IDs, and creating different Connection
+objects.
+
+The Type 4 driver provides for user name and password authentication.
+The password is encrypted with a proprietary algorithm provided by DCS.
+
+NOTE: There is no secure wire communication such as SSL provided for the
+communication between Type 4 driver and the {project-name} platform.
+
+<<<
+[[connection-by-using-the-datasource-interface]]
+== Connection by Using the DataSource Interface
+
+The `javax.sql.DataSource` interface is the preferred way to establish a
+connection to the database because this interface enhances the application
+portability. Portability is achieved by allowing the application to use a
+logical name for a data source instead of providing driver-specific 
information
+in the application. A logical name is mapped to a `javax.sql.DataSource`
+object through a naming service that uses the Java Naming and Directory
+Interface (JNDI). Using this DataSource method is particularly recommended
+for application servers.
+
+When an application requests a connection by using the `getConnection` 
method
+in the `DataSource`, then the method returns a `Connection` object.
+
+A `DataSource` object is a factory for `Connection` objects. An object that
+implements the `DataSource` interface is typically registered with a JNDI
+service provider.
+
+[[overview-of-tasks-to-deploy-datasource-objects]]
+=== Overview of Tasks to Deploy DataSource Objects
+
+Before an application can connect to a `DataSource` object, typically
+the system administrator deploys the `DataSource` object so that
+the application programmers can start using it.
+
+Data source properties are usually set by a system administrator using
+a GUI tool as part of the installation of the data 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61673116
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/accessing.adoc ---
@@ -0,0 +1,910 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[accessing-project-name-sql-databases]]
+= Accessing {project-name} SQL Databases
+
+[[data-sources]]
+== Data Sources
+
+The term *data source* logically refers to a database or other data
+storage entity. A JDBC (client) data source is physically a Java object 
that
+contains properties such as the URL of the physical database, the
+catalog to use when connecting to this database, and the schema to use
+when connecting to this database. The JDBC data source also contains
+methods for obtaining a JDBC connection to the underlying database.
+
+[[jdbc-data-source-client-side]]
+=== JDBC Data Source (client-side)
+
+All JDBC data source classes implement either the `javax.sql.DataSource`
+interface or the `javax.sql.ConnectionPoolDataSource` interface. The Type
+4 driver data source classes are `org.trafodion.t4jdbc.HPT4DataSource` and
+`org.trafodion.t4jdbc.HPT4ConnectionPoolDataSource`. (These classes are
+defined by the JDBC 3.0 specification.)
+
+Typically, a user or system administrator uses a tool to create a data
+source, and then registers the data source by using a JNDI service
+provider. At run time, a user application typically retrieves the data
+source through JNDI, and uses the data source's methods to establish a
+connection to the underlying database.
+
+A DataSource object maps to an instance of a database. In the Type 4
+driver product, the DataSource object acts as an interface between the
+application code and the database and enables connection with an DCS
+data source.
+
+[[security]]
+== Security
+
+Clients connect to the {project-name} platform with a valid user name
+and ID, using standard JDBC 3.0 APIs. An application can make multiple
+connections using different user IDs, and creating different Connection
+objects.
+
+The Type 4 driver provides for user name and password authentication.
+The password is encrypted with a proprietary algorithm provided by DCS.
+
+NOTE: There is no secure wire communication such as SSL provided for the
+communication between Type 4 driver and the {project-name} platform.
+
+<<<
+[[connection-by-using-the-datasource-interface]]
+== Connection by Using the DataSource Interface
+
+The `javax.sql.DataSource` interface is the preferred way to establish a
+connection to the database because this interface enhances the application
+portability. Portability is achieved by allowing the application to use a
+logical name for a data source instead of providing driver-specific 
information
+in the application. A logical name is mapped to a `javax.sql.DataSource`
+object through a naming service that uses the Java Naming and Directory
+Interface (JNDI). Using this DataSource method is particularly recommended
+for application servers.
+
+When an application requests a connection by using the `getConnection` 
method
+in the `DataSource`, then the method returns a `Connection` object.
+
+A `DataSource` object is a factory for `Connection` objects. An object that
+implements the `DataSource` interface is typically registered with a JNDI
+service provider.
+
+[[overview-of-tasks-to-deploy-datasource-objects]]
+=== Overview of Tasks to Deploy DataSource Objects
+
+Before an application can connect to a `DataSource` object, typically
+the system administrator deploys the `DataSource` object so that
+the application programmers can start using it.
+
+Data source properties are usually set by a system administrator using
+a GUI tool as part of the installation of the data 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61673121
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/accessing.adoc ---
@@ -0,0 +1,910 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[accessing-project-name-sql-databases]]
+= Accessing {project-name} SQL Databases
+
+[[data-sources]]
+== Data Sources
+
+The term *data source* logically refers to a database or other data
+storage entity. A JDBC (client) data source is physically a Java object 
that
+contains properties such as the URL of the physical database, the
+catalog to use when connecting to this database, and the schema to use
+when connecting to this database. The JDBC data source also contains
+methods for obtaining a JDBC connection to the underlying database.
+
+[[jdbc-data-source-client-side]]
+=== JDBC Data Source (client-side)
+
+All JDBC data source classes implement either the `javax.sql.DataSource`
+interface or the `javax.sql.ConnectionPoolDataSource` interface. The Type
+4 driver data source classes are `org.trafodion.t4jdbc.HPT4DataSource` and
+`org.trafodion.t4jdbc.HPT4ConnectionPoolDataSource`. (These classes are
+defined by the JDBC 3.0 specification.)
+
+Typically, a user or system administrator uses a tool to create a data
+source, and then registers the data source by using a JNDI service
+provider. At run time, a user application typically retrieves the data
+source through JNDI, and uses the data source's methods to establish a
+connection to the underlying database.
+
+A DataSource object maps to an instance of a database. In the Type 4
+driver product, the DataSource object acts as an interface between the
+application code and the database and enables connection with an DCS
+data source.
+
+[[security]]
+== Security
+
+Clients connect to the {project-name} platform with a valid user name
+and ID, using standard JDBC 3.0 APIs. An application can make multiple
+connections using different user IDs, and creating different Connection
+objects.
+
+The Type 4 driver provides for user name and password authentication.
+The password is encrypted with a proprietary algorithm provided by DCS.
+
+NOTE: There is no secure wire communication such as SSL provided for the
+communication between Type 4 driver and the {project-name} platform.
+
+<<<
+[[connection-by-using-the-datasource-interface]]
+== Connection by Using the DataSource Interface
+
+The `javax.sql.DataSource` interface is the preferred way to establish a
+connection to the database because this interface enhances the application
+portability. Portability is achieved by allowing the application to use a
+logical name for a data source instead of providing driver-specific 
information
+in the application. A logical name is mapped to a `javax.sql.DataSource`
+object through a naming service that uses the Java Naming and Directory
+Interface (JNDI). Using this DataSource method is particularly recommended
+for application servers.
+
+When an application requests a connection by using the `getConnection` 
method
+in the `DataSource`, then the method returns a `Connection` object.
+
+A `DataSource` object is a factory for `Connection` objects. An object that
+implements the `DataSource` interface is typically registered with a JNDI
+service provider.
+
+[[overview-of-tasks-to-deploy-datasource-objects]]
+=== Overview of Tasks to Deploy DataSource Objects
+
+Before an application can connect to a `DataSource` object, typically
+the system administrator deploys the `DataSource` object so that
+the application programmers can start using it.
+
+Data source properties are usually set by a system administrator using
+a GUI tool as part of the installation of the data 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61673106
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/accessing.adoc ---
@@ -0,0 +1,910 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[accessing-project-name-sql-databases]]
+= Accessing {project-name} SQL Databases
+
+[[data-sources]]
+== Data Sources
+
+The term *data source* logically refers to a database or other data
+storage entity. A JDBC (client) data source is physically a Java object 
that
+contains properties such as the URL of the physical database, the
+catalog to use when connecting to this database, and the schema to use
+when connecting to this database. The JDBC data source also contains
+methods for obtaining a JDBC connection to the underlying database.
+
+[[jdbc-data-source-client-side]]
+=== JDBC Data Source (client-side)
+
+All JDBC data source classes implement either the `javax.sql.DataSource`
+interface or the `javax.sql.ConnectionPoolDataSource` interface. The Type
+4 driver data source classes are `org.trafodion.t4jdbc.HPT4DataSource` and
+`org.trafodion.t4jdbc.HPT4ConnectionPoolDataSource`. (These classes are
+defined by the JDBC 3.0 specification.)
+
+Typically, a user or system administrator uses a tool to create a data
+source, and then registers the data source by using a JNDI service
+provider. At run time, a user application typically retrieves the data
+source through JNDI, and uses the data source's methods to establish a
+connection to the underlying database.
+
+A DataSource object maps to an instance of a database. In the Type 4
+driver product, the DataSource object acts as an interface between the
+application code and the database and enables connection with an DCS
+data source.
+
+[[security]]
+== Security
+
+Clients connect to the {project-name} platform with a valid user name
+and ID, using standard JDBC 3.0 APIs. An application can make multiple
+connections using different user IDs, and creating different Connection
+objects.
+
+The Type 4 driver provides for user name and password authentication.
+The password is encrypted with a proprietary algorithm provided by DCS.
+
+NOTE: There is no secure wire communication such as SSL provided for the
+communication between Type 4 driver and the {project-name} platform.
+
+<<<
+[[connection-by-using-the-datasource-interface]]
+== Connection by Using the DataSource Interface
+
+The `javax.sql.DataSource` interface is the preferred way to establish a
+connection to the database because this interface enhances the application
+portability. Portability is achieved by allowing the application to use a
+logical name for a data source instead of providing driver-specific 
information
+in the application. A logical name is mapped to a `javax.sql.DataSource`
+object through a naming service that uses the Java Naming and Directory
+Interface (JNDI). Using this DataSource method is particularly recommended
+for application servers.
+
+When an application requests a connection by using the `getConnection` 
method
+in the `DataSource`, then the method returns a `Connection` object.
+
+A `DataSource` object is a factory for `Connection` objects. An object that
+implements the `DataSource` interface is typically registered with a JNDI
+service provider.
+
+[[overview-of-tasks-to-deploy-datasource-objects]]
+=== Overview of Tasks to Deploy DataSource Objects
+
+Before an application can connect to a `DataSource` object, typically
+the system administrator deploys the `DataSource` object so that
+the application programmers can start using it.
+
+Data source properties are usually set by a system administrator using
+a GUI tool as part of the installation of the data 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61673096
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/accessing.adoc ---
@@ -0,0 +1,910 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[accessing-project-name-sql-databases]]
+= Accessing {project-name} SQL Databases
+
+[[data-sources]]
+== Data Sources
+
+The term *data source* logically refers to a database or other data
+storage entity. A JDBC (client) data source is physically a Java object 
that
+contains properties such as the URL of the physical database, the
+catalog to use when connecting to this database, and the schema to use
+when connecting to this database. The JDBC data source also contains
+methods for obtaining a JDBC connection to the underlying database.
+
+[[jdbc-data-source-client-side]]
+=== JDBC Data Source (client-side)
+
+All JDBC data source classes implement either the `javax.sql.DataSource`
+interface or the `javax.sql.ConnectionPoolDataSource` interface. The Type
+4 driver data source classes are `org.trafodion.t4jdbc.HPT4DataSource` and
+`org.trafodion.t4jdbc.HPT4ConnectionPoolDataSource`. (These classes are
+defined by the JDBC 3.0 specification.)
+
+Typically, a user or system administrator uses a tool to create a data
+source, and then registers the data source by using a JNDI service
+provider. At run time, a user application typically retrieves the data
+source through JNDI, and uses the data source's methods to establish a
+connection to the underlying database.
+
+A DataSource object maps to an instance of a database. In the Type 4
+driver product, the DataSource object acts as an interface between the
+application code and the database and enables connection with an DCS
+data source.
+
+[[security]]
+== Security
+
+Clients connect to the {project-name} platform with a valid user name
+and ID, using standard JDBC 3.0 APIs. An application can make multiple
+connections using different user IDs, and creating different Connection
+objects.
+
+The Type 4 driver provides for user name and password authentication.
+The password is encrypted with a proprietary algorithm provided by DCS.
+
+NOTE: There is no secure wire communication such as SSL provided for the
+communication between Type 4 driver and the {project-name} platform.
+
+<<<
+[[connection-by-using-the-datasource-interface]]
+== Connection by Using the DataSource Interface
+
+The `javax.sql.DataSource` interface is the preferred way to establish a
+connection to the database because this interface enhances the application
+portability. Portability is achieved by allowing the application to use a
+logical name for a data source instead of providing driver-specific 
information
+in the application. A logical name is mapped to a `javax.sql.DataSource`
+object through a naming service that uses the Java Naming and Directory
+Interface (JNDI). Using this DataSource method is particularly recommended
+for application servers.
+
+When an application requests a connection by using the `getConnection` 
method
+in the `DataSource`, then the method returns a `Connection` object.
+
+A `DataSource` object is a factory for `Connection` objects. An object that
+implements the `DataSource` interface is typically registered with a JNDI
+service provider.
+
+[[overview-of-tasks-to-deploy-datasource-objects]]
+=== Overview of Tasks to Deploy DataSource Objects
+
+Before an application can connect to a `DataSource` object, typically
+the system administrator deploys the `DataSource` object so that
+the application programmers can start using it.
+
+Data source properties are usually set by a system administrator using
+a GUI tool as part of the installation of the data 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61673086
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/accessing.adoc ---
@@ -0,0 +1,910 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[accessing-project-name-sql-databases]]
+= Accessing {project-name} SQL Databases
+
+[[data-sources]]
+== Data Sources
+
+The term *data source* logically refers to a database or other data
+storage entity. A JDBC (client) data source is physically a Java object 
that
+contains properties such as the URL of the physical database, the
+catalog to use when connecting to this database, and the schema to use
+when connecting to this database. The JDBC data source also contains
+methods for obtaining a JDBC connection to the underlying database.
+
+[[jdbc-data-source-client-side]]
+=== JDBC Data Source (client-side)
+
+All JDBC data source classes implement either the `javax.sql.DataSource`
+interface or the `javax.sql.ConnectionPoolDataSource` interface. The Type
+4 driver data source classes are `org.trafodion.t4jdbc.HPT4DataSource` and
+`org.trafodion.t4jdbc.HPT4ConnectionPoolDataSource`. (These classes are
+defined by the JDBC 3.0 specification.)
+
+Typically, a user or system administrator uses a tool to create a data
+source, and then registers the data source by using a JNDI service
+provider. At run time, a user application typically retrieves the data
+source through JNDI, and uses the data source's methods to establish a
+connection to the underlying database.
+
+A DataSource object maps to an instance of a database. In the Type 4
+driver product, the DataSource object acts as an interface between the
+application code and the database and enables connection with an DCS
+data source.
+
+[[security]]
+== Security
+
+Clients connect to the {project-name} platform with a valid user name
+and ID, using standard JDBC 3.0 APIs. An application can make multiple
+connections using different user IDs, and creating different Connection
+objects.
+
+The Type 4 driver provides for user name and password authentication.
+The password is encrypted with a proprietary algorithm provided by DCS.
+
+NOTE: There is no secure wire communication such as SSL provided for the
+communication between Type 4 driver and the {project-name} platform.
+
+<<<
+[[connection-by-using-the-datasource-interface]]
+== Connection by Using the DataSource Interface
+
+The `javax.sql.DataSource` interface is the preferred way to establish a
+connection to the database because this interface enhances the application
+portability. Portability is achieved by allowing the application to use a
+logical name for a data source instead of providing driver-specific 
information
+in the application. A logical name is mapped to a `javax.sql.DataSource`
+object through a naming service that uses the Java Naming and Directory
+Interface (JNDI). Using this DataSource method is particularly recommended
+for application servers.
+
+When an application requests a connection by using the `getConnection` 
method
+in the `DataSource`, then the method returns a `Connection` object.
+
+A `DataSource` object is a factory for `Connection` objects. An object that
+implements the `DataSource` interface is typically registered with a JNDI
+service provider.
+
+[[overview-of-tasks-to-deploy-datasource-objects]]
+=== Overview of Tasks to Deploy DataSource Objects
+
+Before an application can connect to a `DataSource` object, typically
+the system administrator deploys the `DataSource` object so that
+the application programmers can start using it.
+
+Data source properties are usually set by a system administrator using
+a GUI tool as part of the installation of the data 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61673073
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/accessing.adoc ---
@@ -0,0 +1,910 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[accessing-project-name-sql-databases]]
+= Accessing {project-name} SQL Databases
+
+[[data-sources]]
+== Data Sources
+
+The term *data source* logically refers to a database or other data
+storage entity. A JDBC (client) data source is physically a Java object 
that
+contains properties such as the URL of the physical database, the
+catalog to use when connecting to this database, and the schema to use
+when connecting to this database. The JDBC data source also contains
+methods for obtaining a JDBC connection to the underlying database.
+
+[[jdbc-data-source-client-side]]
+=== JDBC Data Source (client-side)
+
+All JDBC data source classes implement either the `javax.sql.DataSource`
+interface or the `javax.sql.ConnectionPoolDataSource` interface. The Type
+4 driver data source classes are `org.trafodion.t4jdbc.HPT4DataSource` and
+`org.trafodion.t4jdbc.HPT4ConnectionPoolDataSource`. (These classes are
+defined by the JDBC 3.0 specification.)
+
+Typically, a user or system administrator uses a tool to create a data
+source, and then registers the data source by using a JNDI service
+provider. At run time, a user application typically retrieves the data
+source through JNDI, and uses the data source's methods to establish a
+connection to the underlying database.
+
+A DataSource object maps to an instance of a database. In the Type 4
+driver product, the DataSource object acts as an interface between the
+application code and the database and enables connection with an DCS
+data source.
+
+[[security]]
+== Security
+
+Clients connect to the {project-name} platform with a valid user name
+and ID, using standard JDBC 3.0 APIs. An application can make multiple
+connections using different user IDs, and creating different Connection
+objects.
+
+The Type 4 driver provides for user name and password authentication.
+The password is encrypted with a proprietary algorithm provided by DCS.
+
+NOTE: There is no secure wire communication such as SSL provided for the
+communication between Type 4 driver and the {project-name} platform.
+
+<<<
+[[connection-by-using-the-datasource-interface]]
+== Connection by Using the DataSource Interface
+
+The `javax.sql.DataSource` interface is the preferred way to establish a
+connection to the database because this interface enhances the application
+portability. Portability is achieved by allowing the application to use a
+logical name for a data source instead of providing driver-specific 
information
+in the application. A logical name is mapped to a `javax.sql.DataSource`
+object through a naming service that uses the Java Naming and Directory
+Interface (JNDI). Using this DataSource method is particularly recommended
+for application servers.
+
+When an application requests a connection by using the `getConnection` 
method
+in the `DataSource`, then the method returns a `Connection` object.
+
+A `DataSource` object is a factory for `Connection` objects. An object that
+implements the `DataSource` interface is typically registered with a JNDI
+service provider.
+
+[[overview-of-tasks-to-deploy-datasource-objects]]
+=== Overview of Tasks to Deploy DataSource Objects
+
+Before an application can connect to a `DataSource` object, typically
+the system administrator deploys the `DataSource` object so that
+the application programmers can start using it.
+
+Data source properties are usually set by a system administrator using
+a GUI tool as part of the installation of the data 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61673063
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/accessing.adoc ---
@@ -0,0 +1,910 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[accessing-project-name-sql-databases]]
+= Accessing {project-name} SQL Databases
+
+[[data-sources]]
+== Data Sources
+
+The term *data source* logically refers to a database or other data
+storage entity. A JDBC (client) data source is physically a Java object 
that
+contains properties such as the URL of the physical database, the
+catalog to use when connecting to this database, and the schema to use
+when connecting to this database. The JDBC data source also contains
+methods for obtaining a JDBC connection to the underlying database.
+
+[[jdbc-data-source-client-side]]
+=== JDBC Data Source (client-side)
+
+All JDBC data source classes implement either the `javax.sql.DataSource`
+interface or the `javax.sql.ConnectionPoolDataSource` interface. The Type
+4 driver data source classes are `org.trafodion.t4jdbc.HPT4DataSource` and
+`org.trafodion.t4jdbc.HPT4ConnectionPoolDataSource`. (These classes are
+defined by the JDBC 3.0 specification.)
+
+Typically, a user or system administrator uses a tool to create a data
+source, and then registers the data source by using a JNDI service
+provider. At run time, a user application typically retrieves the data
+source through JNDI, and uses the data source's methods to establish a
+connection to the underlying database.
+
+A DataSource object maps to an instance of a database. In the Type 4
+driver product, the DataSource object acts as an interface between the
+application code and the database and enables connection with an DCS
+data source.
+
+[[security]]
+== Security
+
+Clients connect to the {project-name} platform with a valid user name
+and ID, using standard JDBC 3.0 APIs. An application can make multiple
+connections using different user IDs, and creating different Connection
+objects.
+
+The Type 4 driver provides for user name and password authentication.
+The password is encrypted with a proprietary algorithm provided by DCS.
+
+NOTE: There is no secure wire communication such as SSL provided for the
+communication between Type 4 driver and the {project-name} platform.
+
+<<<
+[[connection-by-using-the-datasource-interface]]
+== Connection by Using the DataSource Interface
+
+The `javax.sql.DataSource` interface is the preferred way to establish a
+connection to the database because this interface enhances the application
+portability. Portability is achieved by allowing the application to use a
+logical name for a data source instead of providing driver-specific 
information
+in the application. A logical name is mapped to a `javax.sql.DataSource`
+object through a naming service that uses the Java Naming and Directory
+Interface (JNDI). Using this DataSource method is particularly recommended
+for application servers.
+
+When an application requests a connection by using the `getConnection` 
method
+in the `DataSource`, then the method returns a `Connection` object.
+
+A `DataSource` object is a factory for `Connection` objects. An object that
+implements the `DataSource` interface is typically registered with a JNDI
+service provider.
+
+[[overview-of-tasks-to-deploy-datasource-objects]]
+=== Overview of Tasks to Deploy DataSource Objects
+
+Before an application can connect to a `DataSource` object, typically
+the system administrator deploys the `DataSource` object so that
+the application programmers can start using it.
+
+Data source properties are usually set by a system administrator using
+a GUI tool as part of the installation of the data 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61673045
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/accessing.adoc ---
@@ -0,0 +1,910 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[accessing-project-name-sql-databases]]
+= Accessing {project-name} SQL Databases
+
+[[data-sources]]
+== Data Sources
+
+The term *data source* logically refers to a database or other data
+storage entity. A JDBC (client) data source is physically a Java object 
that
+contains properties such as the URL of the physical database, the
+catalog to use when connecting to this database, and the schema to use
+when connecting to this database. The JDBC data source also contains
+methods for obtaining a JDBC connection to the underlying database.
+
+[[jdbc-data-source-client-side]]
+=== JDBC Data Source (client-side)
+
+All JDBC data source classes implement either the `javax.sql.DataSource`
+interface or the `javax.sql.ConnectionPoolDataSource` interface. The Type
+4 driver data source classes are `org.trafodion.t4jdbc.HPT4DataSource` and
+`org.trafodion.t4jdbc.HPT4ConnectionPoolDataSource`. (These classes are
+defined by the JDBC 3.0 specification.)
+
+Typically, a user or system administrator uses a tool to create a data
+source, and then registers the data source by using a JNDI service
+provider. At run time, a user application typically retrieves the data
+source through JNDI, and uses the data source's methods to establish a
+connection to the underlying database.
+
+A DataSource object maps to an instance of a database. In the Type 4
+driver product, the DataSource object acts as an interface between the
+application code and the database and enables connection with an DCS
+data source.
+
+[[security]]
+== Security
+
+Clients connect to the {project-name} platform with a valid user name
+and ID, using standard JDBC 3.0 APIs. An application can make multiple
+connections using different user IDs, and creating different Connection
+objects.
+
+The Type 4 driver provides for user name and password authentication.
+The password is encrypted with a proprietary algorithm provided by DCS.
+
+NOTE: There is no secure wire communication such as SSL provided for the
+communication between Type 4 driver and the {project-name} platform.
+
+<<<
+[[connection-by-using-the-datasource-interface]]
+== Connection by Using the DataSource Interface
+
+The `javax.sql.DataSource` interface is the preferred way to establish a
+connection to the database because this interface enhances the application
+portability. Portability is achieved by allowing the application to use a
+logical name for a data source instead of providing driver-specific 
information
+in the application. A logical name is mapped to a `javax.sql.DataSource`
+object through a naming service that uses the Java Naming and Directory
+Interface (JNDI). Using this DataSource method is particularly recommended
+for application servers.
+
+When an application requests a connection by using the `getConnection` 
method
+in the `DataSource`, then the method returns a `Connection` object.
+
+A `DataSource` object is a factory for `Connection` objects. An object that
+implements the `DataSource` interface is typically registered with a JNDI
+service provider.
+
+[[overview-of-tasks-to-deploy-datasource-objects]]
+=== Overview of Tasks to Deploy DataSource Objects
+
+Before an application can connect to a `DataSource` object, typically
+the system administrator deploys the `DataSource` object so that
+the application programmers can start using it.
+
+Data source properties are usually set by a system administrator using
+a GUI tool as part of the installation of the data 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61673050
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/accessing.adoc ---
@@ -0,0 +1,910 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[accessing-project-name-sql-databases]]
+= Accessing {project-name} SQL Databases
+
+[[data-sources]]
+== Data Sources
+
+The term *data source* logically refers to a database or other data
+storage entity. A JDBC (client) data source is physically a Java object 
that
+contains properties such as the URL of the physical database, the
+catalog to use when connecting to this database, and the schema to use
+when connecting to this database. The JDBC data source also contains
+methods for obtaining a JDBC connection to the underlying database.
+
+[[jdbc-data-source-client-side]]
+=== JDBC Data Source (client-side)
+
+All JDBC data source classes implement either the `javax.sql.DataSource`
+interface or the `javax.sql.ConnectionPoolDataSource` interface. The Type
+4 driver data source classes are `org.trafodion.t4jdbc.HPT4DataSource` and
+`org.trafodion.t4jdbc.HPT4ConnectionPoolDataSource`. (These classes are
+defined by the JDBC 3.0 specification.)
+
+Typically, a user or system administrator uses a tool to create a data
+source, and then registers the data source by using a JNDI service
+provider. At run time, a user application typically retrieves the data
+source through JNDI, and uses the data source's methods to establish a
+connection to the underlying database.
+
+A DataSource object maps to an instance of a database. In the Type 4
+driver product, the DataSource object acts as an interface between the
+application code and the database and enables connection with an DCS
+data source.
+
+[[security]]
+== Security
+
+Clients connect to the {project-name} platform with a valid user name
+and ID, using standard JDBC 3.0 APIs. An application can make multiple
+connections using different user IDs, and creating different Connection
+objects.
+
+The Type 4 driver provides for user name and password authentication.
+The password is encrypted with a proprietary algorithm provided by DCS.
+
+NOTE: There is no secure wire communication such as SSL provided for the
+communication between Type 4 driver and the {project-name} platform.
+
+<<<
+[[connection-by-using-the-datasource-interface]]
+== Connection by Using the DataSource Interface
+
+The `javax.sql.DataSource` interface is the preferred way to establish a
+connection to the database because this interface enhances the application
+portability. Portability is achieved by allowing the application to use a
+logical name for a data source instead of providing driver-specific 
information
+in the application. A logical name is mapped to a `javax.sql.DataSource`
+object through a naming service that uses the Java Naming and Directory
+Interface (JNDI). Using this DataSource method is particularly recommended
+for application servers.
+
+When an application requests a connection by using the `getConnection` 
method
+in the `DataSource`, then the method returns a `Connection` object.
+
+A `DataSource` object is a factory for `Connection` objects. An object that
+implements the `DataSource` interface is typically registered with a JNDI
+service provider.
+
+[[overview-of-tasks-to-deploy-datasource-objects]]
+=== Overview of Tasks to Deploy DataSource Objects
+
+Before an application can connect to a `DataSource` object, typically
+the system administrator deploys the `DataSource` object so that
+the application programmers can start using it.
+
+Data source properties are usually set by a system administrator using
+a GUI tool as part of the installation of the data 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61673018
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/accessing.adoc ---
@@ -0,0 +1,910 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[accessing-project-name-sql-databases]]
+= Accessing {project-name} SQL Databases
+
+[[data-sources]]
+== Data Sources
+
+The term *data source* logically refers to a database or other data
+storage entity. A JDBC (client) data source is physically a Java object 
that
+contains properties such as the URL of the physical database, the
+catalog to use when connecting to this database, and the schema to use
+when connecting to this database. The JDBC data source also contains
+methods for obtaining a JDBC connection to the underlying database.
+
+[[jdbc-data-source-client-side]]
+=== JDBC Data Source (client-side)
+
+All JDBC data source classes implement either the `javax.sql.DataSource`
+interface or the `javax.sql.ConnectionPoolDataSource` interface. The Type
+4 driver data source classes are `org.trafodion.t4jdbc.HPT4DataSource` and
+`org.trafodion.t4jdbc.HPT4ConnectionPoolDataSource`. (These classes are
+defined by the JDBC 3.0 specification.)
+
+Typically, a user or system administrator uses a tool to create a data
+source, and then registers the data source by using a JNDI service
+provider. At run time, a user application typically retrieves the data
+source through JNDI, and uses the data source's methods to establish a
+connection to the underlying database.
+
+A DataSource object maps to an instance of a database. In the Type 4
+driver product, the DataSource object acts as an interface between the
+application code and the database and enables connection with an DCS
+data source.
+
+[[security]]
+== Security
+
+Clients connect to the {project-name} platform with a valid user name
+and ID, using standard JDBC 3.0 APIs. An application can make multiple
+connections using different user IDs, and creating different Connection
+objects.
+
+The Type 4 driver provides for user name and password authentication.
+The password is encrypted with a proprietary algorithm provided by DCS.
+
+NOTE: There is no secure wire communication such as SSL provided for the
+communication between Type 4 driver and the {project-name} platform.
+
+<<<
+[[connection-by-using-the-datasource-interface]]
+== Connection by Using the DataSource Interface
+
+The `javax.sql.DataSource` interface is the preferred way to establish a
+connection to the database because this interface enhances the application
+portability. Portability is achieved by allowing the application to use a
+logical name for a data source instead of providing driver-specific 
information
+in the application. A logical name is mapped to a `javax.sql.DataSource`
+object through a naming service that uses the Java Naming and Directory
+Interface (JNDI). Using this DataSource method is particularly recommended
+for application servers.
+
+When an application requests a connection by using the `getConnection` 
method
+in the `DataSource`, then the method returns a `Connection` object.
+
+A `DataSource` object is a factory for `Connection` objects. An object that
+implements the `DataSource` interface is typically registered with a JNDI
+service provider.
+
+[[overview-of-tasks-to-deploy-datasource-objects]]
+=== Overview of Tasks to Deploy DataSource Objects
+
+Before an application can connect to a `DataSource` object, typically
+the system administrator deploys the `DataSource` object so that
+the application programmers can start using it.
+
+Data source properties are usually set by a system administrator using
+a GUI tool as part of the installation of the data 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61670108
  
--- 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
+<>.
+
+
+[[blobtablename]]
+== blobTableName Property
+
+See <>.
+
+
+[[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
+<>.
+
+```
+Data type: String
+
+Default: none
+```
+
+*Example*
+
+Specifying the catalog Seabase:
+
+```
+catalog=Seabase
+```
+
+
+[[clobtablename]]
+== clobTableName Property
+
+See <>.
+
+
+<<<
+[[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
+<>.
+
+```
+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
+<>.
+
+```
+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 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61670102
  
--- 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
+<>.
+
+
+[[blobtablename]]
+== blobTableName Property
+
+See <>.
+
+
+[[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
+<>.
+
+```
+Data type: String
+
+Default: none
+```
+
+*Example*
+
+Specifying the catalog Seabase:
+
+```
+catalog=Seabase
+```
+
+
+[[clobtablename]]
+== clobTableName Property
+
+See <>.
+
+
+<<<
+[[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
+<>.
+
+```
+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
+<>.
+
+```
+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 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61670095
  
--- 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
+<>.
+
+
+[[blobtablename]]
+== blobTableName Property
+
+See <>.
+
+
+[[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
+<>.
+
+```
+Data type: String
+
+Default: none
+```
+
+*Example*
+
+Specifying the catalog Seabase:
+
+```
+catalog=Seabase
+```
+
+
+[[clobtablename]]
+== clobTableName Property
+
+See <>.
+
+
+<<<
+[[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
+<>.
+
+```
+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
+<>.
+
+```
+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 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61670015
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/introduction.adoc ---
@@ -0,0 +1,53 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[introduction]]
+= Introduction
+
+This document describes how to use the {project-name} JDBC Type 4
+Driver. This driver provides Java applications running on a foreign
+platform with JDBC access to {project-name} SQL databases on the
+{project-name}.
+
+*Supported Java Releases:* The Type 4 driver requires Java enabled
+platforms that support JDK 1.4.1 or higher.
+
+
+[[type-4-driver-api-package]]
+== Type 4 Driver API Package
+
+The Type 4 driver package, `org.trafodion.t4jdbc`, is shipped with the
+driver software. For class and method descriptions, see the
+_{project-name} JDBC Type 4 Driver API Reference_.
+
+The {project-name} JDBC Type 4 Driver (hereafter, Type 4 driver)
+implements JDBC technology that conforms to the standard JDBC 3.0 Data
+Access API.
+
+To obtain detailed information on the standard JDBC API, download the
+JDBC API documentation: http://docs.oracle.com/en/java/.
--- End diff --

might need to fix the link


---
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.
---

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61669998
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/introduction.adoc ---
@@ -0,0 +1,53 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[introduction]]
+= Introduction
+
+This document describes how to use the {project-name} JDBC Type 4
+Driver. This driver provides Java applications running on a foreign
+platform with JDBC access to {project-name} SQL databases on the
+{project-name}.
+
+*Supported Java Releases:* The Type 4 driver requires Java enabled
+platforms that support JDK 1.4.1 or higher.
+
+
+[[type-4-driver-api-package]]
+== Type 4 Driver API Package
+
+The Type 4 driver package, `org.trafodion.t4jdbc`, is shipped with the
--- End diff --

jdbc.t4


---
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.
---

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61669988
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/compliance.adoc ---
@@ -0,0 +1,386 @@
+
+/**
+ *@@@ 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-compliance]]
+= Type 4 Driver Compliance
+
+[[compliance-overview]]
+== Compliance Overview
+
+The Type 4 driver conforms where applicable to the JDBC
+3.0 API specification. However, this driver differs from the JDBC
+standard in some ways. This subsection describes the JDBC methods that
+are not supported, the methods and features that deviate from the
+specification, and features that are {project-name} extensions to the JDBC 
standard.
+JDBC features that conform to the specification are not described in this 
subsection.
+
+In addition, this chapter lists features of {project-name} SQL that are 
not supported by the {project-name} JDBC Type 4 driver, other
+unsupported features, and restrictions.
+
+[[unsupported-features]]
+== Unsupported Features
+
+These methods in the java.sql package throw an SQLException with the
+message `Unsupported feature - `:
+
+[cols="65%,35%", options="header"]
+|===
+| Method   | Comments
+| `CallableStatement.getArray(int parameterIndex)` +
+`CallableStatement.getArray(String parameterName)` +
+`CallableStatement.getBlob(int parameterIndex)` +
+`CallableStatement.getBlob(String parameterName)` +
+`CallableStatement.getClob(int parameterIndex)` +
+`CallableStatement.getClob(String parameterName)` +
+`CallableStatement.getObject(int parameterIndex, Map map)` +
+`CallableStatement.getObject(String parameterName, Map map)` +
+`CallableStatement.getRef(int parameterIndex)` +
+`CallableStatement.getRef(String parameterName)` +
+`CallableStatement.getURL(int parameterIndex)` +
+`CallableStatement.getURL(String parameterName)` +
+`CallableStatement.executeBatch()` | The particular `CallableStatement` 
method is not supported.
+| `Connection.releaseSavepoint(Savepoint savepoint)` +
+`Connection.rollback(Savepoint savepoint)` +
+`Connection.setSavepoint()` +
+`Connection.setSavepoint(String name)` | The particular `Connection` 
methods are not supported.
+| `PreparedStatement.setArray(int parameterIndex, Array x)` +
+`PreparedStatement.setRef(int parameterIndex, Ref x)` +
+`PreparedStatement.setURL(int parameterIndex, URL x)` | The particular 
`PreparedStatement` methods are not supported.
+| `ResultSet.getArray(int columnIndex)` +
+`ResultSet.getArray(String columnName)` +
+`ResultSet.getObject(int columnIndex, Map map)` +
+`ResultSet.getObject(String columnName, Map map)` +
+`ResultSet.getRef(int columnIndex)ResultSet.getRef(String columnName)` +
+`ResultSet.getURL(int columnIndex)` +
+`ResultSet.getURL(String columnName)` +
+`ResultSet.updateArray(int columnIndex)` +
+`ResultSet.updateArray(String columnName)` +
+`ResultSet.updateRef(int columnIndex)` +
+`ResultSet.updateRef(String columnName) | The particular `ResultSet` 
methods are not supported.
+| `Statement.getQueryTimeout()` +
+`Statement.setQueryTimeout()` | The particular `Statement` methods are not 
supported.
+|===
+
+The following methods in the java.sql package throw an SQLException with
+the message `Auto generated keys not supported`:
+
+[cols="65%,35%", options="header" ]
+|===
+| Method   | Comments
+| `Connection.prepareStatement(String sql, int autoGeneratedKeys)` +
+`Connection.prepareStatement(String sql, int[] columnIndexes)` +
+`Connection.prepareStatement(String sql, String[] columnNames)` | 
Automatically generated keys are not supported.
+| `Statement.executeUpdate(String sql, int autoGeneratedKeys)` +
+`Statement.executeUpdate(String sql, int[] 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61669973
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/compliance.adoc ---
@@ -0,0 +1,386 @@
+
+/**
+ *@@@ 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-compliance]]
+= Type 4 Driver Compliance
+
+[[compliance-overview]]
+== Compliance Overview
+
+The Type 4 driver conforms where applicable to the JDBC
+3.0 API specification. However, this driver differs from the JDBC
+standard in some ways. This subsection describes the JDBC methods that
+are not supported, the methods and features that deviate from the
+specification, and features that are {project-name} extensions to the JDBC 
standard.
+JDBC features that conform to the specification are not described in this 
subsection.
+
+In addition, this chapter lists features of {project-name} SQL that are 
not supported by the {project-name} JDBC Type 4 driver, other
+unsupported features, and restrictions.
+
+[[unsupported-features]]
+== Unsupported Features
+
+These methods in the java.sql package throw an SQLException with the
+message `Unsupported feature - `:
+
+[cols="65%,35%", options="header"]
+|===
+| Method   | Comments
+| `CallableStatement.getArray(int parameterIndex)` +
+`CallableStatement.getArray(String parameterName)` +
+`CallableStatement.getBlob(int parameterIndex)` +
+`CallableStatement.getBlob(String parameterName)` +
+`CallableStatement.getClob(int parameterIndex)` +
+`CallableStatement.getClob(String parameterName)` +
+`CallableStatement.getObject(int parameterIndex, Map map)` +
+`CallableStatement.getObject(String parameterName, Map map)` +
+`CallableStatement.getRef(int parameterIndex)` +
+`CallableStatement.getRef(String parameterName)` +
+`CallableStatement.getURL(int parameterIndex)` +
+`CallableStatement.getURL(String parameterName)` +
+`CallableStatement.executeBatch()` | The particular `CallableStatement` 
method is not supported.
+| `Connection.releaseSavepoint(Savepoint savepoint)` +
+`Connection.rollback(Savepoint savepoint)` +
+`Connection.setSavepoint()` +
+`Connection.setSavepoint(String name)` | The particular `Connection` 
methods are not supported.
+| `PreparedStatement.setArray(int parameterIndex, Array x)` +
+`PreparedStatement.setRef(int parameterIndex, Ref x)` +
+`PreparedStatement.setURL(int parameterIndex, URL x)` | The particular 
`PreparedStatement` methods are not supported.
+| `ResultSet.getArray(int columnIndex)` +
+`ResultSet.getArray(String columnName)` +
+`ResultSet.getObject(int columnIndex, Map map)` +
+`ResultSet.getObject(String columnName, Map map)` +
+`ResultSet.getRef(int columnIndex)ResultSet.getRef(String columnName)` +
+`ResultSet.getURL(int columnIndex)` +
+`ResultSet.getURL(String columnName)` +
+`ResultSet.updateArray(int columnIndex)` +
+`ResultSet.updateArray(String columnName)` +
+`ResultSet.updateRef(int columnIndex)` +
+`ResultSet.updateRef(String columnName) | The particular `ResultSet` 
methods are not supported.
+| `Statement.getQueryTimeout()` +
+`Statement.setQueryTimeout()` | The particular `Statement` methods are not 
supported.
+|===
+
+The following methods in the java.sql package throw an SQLException with
+the message `Auto generated keys not supported`:
+
+[cols="65%,35%", options="header" ]
+|===
+| Method   | Comments
+| `Connection.prepareStatement(String sql, int autoGeneratedKeys)` +
+`Connection.prepareStatement(String sql, int[] columnIndexes)` +
+`Connection.prepareStatement(String sql, String[] columnNames)` | 
Automatically generated keys are not supported.
+| `Statement.executeUpdate(String sql, int autoGeneratedKeys)` +
+`Statement.executeUpdate(String sql, int[] 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61669923
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/compliance.adoc ---
@@ -0,0 +1,386 @@
+
+/**
+ *@@@ 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-compliance]]
+= Type 4 Driver Compliance
+
+[[compliance-overview]]
+== Compliance Overview
+
+The Type 4 driver conforms where applicable to the JDBC
+3.0 API specification. However, this driver differs from the JDBC
+standard in some ways. This subsection describes the JDBC methods that
+are not supported, the methods and features that deviate from the
+specification, and features that are {project-name} extensions to the JDBC 
standard.
+JDBC features that conform to the specification are not described in this 
subsection.
+
+In addition, this chapter lists features of {project-name} SQL that are 
not supported by the {project-name} JDBC Type 4 driver, other
+unsupported features, and restrictions.
+
+[[unsupported-features]]
+== Unsupported Features
+
+These methods in the java.sql package throw an SQLException with the
+message `Unsupported feature - `:
+
+[cols="65%,35%", options="header"]
+|===
+| Method   | Comments
+| `CallableStatement.getArray(int parameterIndex)` +
+`CallableStatement.getArray(String parameterName)` +
+`CallableStatement.getBlob(int parameterIndex)` +
+`CallableStatement.getBlob(String parameterName)` +
+`CallableStatement.getClob(int parameterIndex)` +
+`CallableStatement.getClob(String parameterName)` +
+`CallableStatement.getObject(int parameterIndex, Map map)` +
+`CallableStatement.getObject(String parameterName, Map map)` +
+`CallableStatement.getRef(int parameterIndex)` +
+`CallableStatement.getRef(String parameterName)` +
+`CallableStatement.getURL(int parameterIndex)` +
+`CallableStatement.getURL(String parameterName)` +
+`CallableStatement.executeBatch()` | The particular `CallableStatement` 
method is not supported.
+| `Connection.releaseSavepoint(Savepoint savepoint)` +
+`Connection.rollback(Savepoint savepoint)` +
+`Connection.setSavepoint()` +
+`Connection.setSavepoint(String name)` | The particular `Connection` 
methods are not supported.
+| `PreparedStatement.setArray(int parameterIndex, Array x)` +
+`PreparedStatement.setRef(int parameterIndex, Ref x)` +
+`PreparedStatement.setURL(int parameterIndex, URL x)` | The particular 
`PreparedStatement` methods are not supported.
+| `ResultSet.getArray(int columnIndex)` +
+`ResultSet.getArray(String columnName)` +
+`ResultSet.getObject(int columnIndex, Map map)` +
+`ResultSet.getObject(String columnName, Map map)` +
+`ResultSet.getRef(int columnIndex)ResultSet.getRef(String columnName)` +
+`ResultSet.getURL(int columnIndex)` +
+`ResultSet.getURL(String columnName)` +
+`ResultSet.updateArray(int columnIndex)` +
+`ResultSet.updateArray(String columnName)` +
+`ResultSet.updateRef(int columnIndex)` +
+`ResultSet.updateRef(String columnName) | The particular `ResultSet` 
methods are not supported.
+| `Statement.getQueryTimeout()` +
+`Statement.setQueryTimeout()` | The particular `Statement` methods are not 
supported.
+|===
+
+The following methods in the java.sql package throw an SQLException with
+the message `Auto generated keys not supported`:
+
+[cols="65%,35%", options="header" ]
+|===
+| Method   | Comments
+| `Connection.prepareStatement(String sql, int autoGeneratedKeys)` +
+`Connection.prepareStatement(String sql, int[] columnIndexes)` +
+`Connection.prepareStatement(String sql, String[] columnNames)` | 
Automatically generated keys are not supported.
+| `Statement.executeUpdate(String sql, int autoGeneratedKeys)` +
+`Statement.executeUpdate(String sql, int[] 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61665457
  
--- Diff: 
docs/jdbct4ref_guide/src/asciidoc/_chapters/avoiding_mismatch.adoc ---
@@ -0,0 +1,106 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[avoiding-driver-server-version-mismatch]]
+= Avoiding Driver-Server Version Mismatch
+
+The {project-name} JDBC type 4 driver described in this
+document can connect only with an version-equivalent platform
+(server). It cannot connect with an earlier version platform.
+
+To make a connection with the {project-name} platform, JDBC clients,
+through the driver, connect with the {project-name} database
+connectivity service (DCS) on the {project-name} platform. In some
+situations, {project-name} JDBC clients need to make connections to
+older-version platforms (servers) from the same client boxes.
+To make a connection, the driver version
+must be compatible with the {project-name} platform version.
+
+NOTE: The DCS release version and {project-name} platform release
+version are always the same.
+
+
+[[compatible-versions]]
+== Compatible Versions
+
+Ensure that you install the driver version that is compatible with the
+{project-name} platform version.
+
+
+[cols=",",options="header" ]
+|===
+| Driver version  | Compatible versions of the {project-name} platform
+| {project-name} Release 2.0 driver  | All versions up to, but not 
including, {project-name} Release 2.2
+| {project-name} Release 2.1 driver  | All versions up to, but not 
including, {project-name} Release 2.2
+| {project-name} Release 2.2 driver  | {project-name} Release 2.2 and 
later versions
+|===
+
+If a compatible version is not installed, you can obtain the software to
+download from the {project-name} download site.
+

+[[considerations-for-mixed-version-jdbc-clients-connecting-to-project-name-platforms]]
+== Considerations for Mixed-Version JDBC Clients Connecting to 
{project-name} Platforms
+
+On the client platform, you can install multiple versions of the
+{project-name} JDBC type 4 driver to connect to {project-name}
+platforms of different platform versions.
+
+* Assuming you have installed the Release 2.2 {project-name} JDBC type
+4 driver on your workstation and set up the client environment, the 2.2
+driver's classes are set your java CLASSPATH.
+* To connect to a Release 2.1 or 2.0 server ({project-name} platform)
+from the same client machine, you must load the 2.1 driver by making
+sure that it is in your java CLASSPATH.
+* Connecting to both a 2.1 and 2.2 server from the same application at
+the same time is not possible.
+* A given application must use either the 2.2 driver or the 2.1 driver
+when launched. The only way to switch is to reload the application when
+pointing to a new CLASSPATH that contains a different driver.
+
+[[version-mismatch-error-message]]
+== Version Mismatch Error Message
+
+If an {project-name} JDBC client attempts to connect to an invalid DCS
+version, the driver returns the error:
+
+```
+SQLCODE: 29162
+SQLSTATE S1000
+
+Error text:
+
+Unexpected programming exception has been found: . Check
+the server event log on node  for details.
+```
+
+*  is the error text from the server.
+*  is the location of the log file.
+
+Additional error text returned only by a Release 2.2 server, but displayed 
by any version driver:
--- End diff --

Delete all of this till end of T7969...


---
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 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61665441
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/accessing.adoc ---
@@ -0,0 +1,910 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[accessing-project-name-sql-databases]]
+= Accessing {project-name} SQL Databases
+
+[[data-sources]]
+== Data Sources
+
+The term *data source* logically refers to a database or other data
+storage entity. A JDBC (client) data source is physically a Java object 
that
+contains properties such as the URL of the physical database, the
+catalog to use when connecting to this database, and the schema to use
+when connecting to this database. The JDBC data source also contains
+methods for obtaining a JDBC connection to the underlying database.
+
+[[jdbc-data-source-client-side]]
+=== JDBC Data Source (client-side)
+
+All JDBC data source classes implement either the `javax.sql.DataSource`
+interface or the `javax.sql.ConnectionPoolDataSource` interface. The Type
+4 driver data source classes are `org.trafodion.t4jdbc.HPT4DataSource` and
+`org.trafodion.t4jdbc.HPT4ConnectionPoolDataSource`. (These classes are
+defined by the JDBC 3.0 specification.)
+
+Typically, a user or system administrator uses a tool to create a data
+source, and then registers the data source by using a JNDI service
+provider. At run time, a user application typically retrieves the data
+source through JNDI, and uses the data source's methods to establish a
+connection to the underlying database.
+
+A DataSource object maps to an instance of a database. In the Type 4
+driver product, the DataSource object acts as an interface between the
+application code and the database and enables connection with an DCS
+data source.
+
+[[security]]
+== Security
+
+Clients connect to the {project-name} platform with a valid user name
+and ID, using standard JDBC 3.0 APIs. An application can make multiple
+connections using different user IDs, and creating different Connection
+objects.
+
+The Type 4 driver provides for user name and password authentication.
+The password is encrypted with a proprietary algorithm provided by DCS.
+
+NOTE: There is no secure wire communication such as SSL provided for the
+communication between Type 4 driver and the {project-name} platform.
+
+<<<
+[[connection-by-using-the-datasource-interface]]
+== Connection by Using the DataSource Interface
+
+The `javax.sql.DataSource` interface is the preferred way to establish a
+connection to the database because this interface enhances the application
+portability. Portability is achieved by allowing the application to use a
+logical name for a data source instead of providing driver-specific 
information
+in the application. A logical name is mapped to a `javax.sql.DataSource`
+object through a naming service that uses the Java Naming and Directory
+Interface (JNDI). Using this DataSource method is particularly recommended
+for application servers.
+
+When an application requests a connection by using the `getConnection` 
method
+in the `DataSource`, then the method returns a `Connection` object.
+
+A `DataSource` object is a factory for `Connection` objects. An object that
+implements the `DataSource` interface is typically registered with a JNDI
+service provider.
+
+[[overview-of-tasks-to-deploy-datasource-objects]]
+=== Overview of Tasks to Deploy DataSource Objects
+
+Before an application can connect to a `DataSource` object, typically
+the system administrator deploys the `DataSource` object so that
+the application programmers can start using it.
+
+Data source properties are usually set by a system administrator using
+a GUI tool as part of the installation of the data 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61665392
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/accessing.adoc ---
@@ -0,0 +1,910 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[accessing-project-name-sql-databases]]
+= Accessing {project-name} SQL Databases
+
+[[data-sources]]
+== Data Sources
+
+The term *data source* logically refers to a database or other data
+storage entity. A JDBC (client) data source is physically a Java object 
that
+contains properties such as the URL of the physical database, the
+catalog to use when connecting to this database, and the schema to use
+when connecting to this database. The JDBC data source also contains
+methods for obtaining a JDBC connection to the underlying database.
+
+[[jdbc-data-source-client-side]]
+=== JDBC Data Source (client-side)
+
+All JDBC data source classes implement either the `javax.sql.DataSource`
+interface or the `javax.sql.ConnectionPoolDataSource` interface. The Type
+4 driver data source classes are `org.trafodion.t4jdbc.HPT4DataSource` and
+`org.trafodion.t4jdbc.HPT4ConnectionPoolDataSource`. (These classes are
+defined by the JDBC 3.0 specification.)
+
+Typically, a user or system administrator uses a tool to create a data
+source, and then registers the data source by using a JNDI service
+provider. At run time, a user application typically retrieves the data
+source through JNDI, and uses the data source's methods to establish a
+connection to the underlying database.
+
+A DataSource object maps to an instance of a database. In the Type 4
+driver product, the DataSource object acts as an interface between the
+application code and the database and enables connection with an DCS
+data source.
+
+[[security]]
+== Security
+
+Clients connect to the {project-name} platform with a valid user name
+and ID, using standard JDBC 3.0 APIs. An application can make multiple
+connections using different user IDs, and creating different Connection
+objects.
+
+The Type 4 driver provides for user name and password authentication.
+The password is encrypted with a proprietary algorithm provided by DCS.
+
+NOTE: There is no secure wire communication such as SSL provided for the
+communication between Type 4 driver and the {project-name} platform.
+
+<<<
+[[connection-by-using-the-datasource-interface]]
+== Connection by Using the DataSource Interface
+
+The `javax.sql.DataSource` interface is the preferred way to establish a
+connection to the database because this interface enhances the application
+portability. Portability is achieved by allowing the application to use a
+logical name for a data source instead of providing driver-specific 
information
+in the application. A logical name is mapped to a `javax.sql.DataSource`
+object through a naming service that uses the Java Naming and Directory
+Interface (JNDI). Using this DataSource method is particularly recommended
+for application servers.
+
+When an application requests a connection by using the `getConnection` 
method
+in the `DataSource`, then the method returns a `Connection` object.
+
+A `DataSource` object is a factory for `Connection` objects. An object that
+implements the `DataSource` interface is typically registered with a JNDI
+service provider.
+
+[[overview-of-tasks-to-deploy-datasource-objects]]
+=== Overview of Tasks to Deploy DataSource Objects
+
+Before an application can connect to a `DataSource` object, typically
+the system administrator deploys the `DataSource` object so that
+the application programmers can start using it.
+
+Data source properties are usually set by a system administrator using
+a GUI tool as part of the installation of the data 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61665276
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/accessing.adoc ---
@@ -0,0 +1,910 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[accessing-project-name-sql-databases]]
+= Accessing {project-name} SQL Databases
+
+[[data-sources]]
+== Data Sources
+
+The term *data source* logically refers to a database or other data
+storage entity. A JDBC (client) data source is physically a Java object 
that
+contains properties such as the URL of the physical database, the
+catalog to use when connecting to this database, and the schema to use
+when connecting to this database. The JDBC data source also contains
+methods for obtaining a JDBC connection to the underlying database.
+
+[[jdbc-data-source-client-side]]
+=== JDBC Data Source (client-side)
+
+All JDBC data source classes implement either the `javax.sql.DataSource`
+interface or the `javax.sql.ConnectionPoolDataSource` interface. The Type
+4 driver data source classes are `org.trafodion.t4jdbc.HPT4DataSource` and
+`org.trafodion.t4jdbc.HPT4ConnectionPoolDataSource`. (These classes are
+defined by the JDBC 3.0 specification.)
+
+Typically, a user or system administrator uses a tool to create a data
+source, and then registers the data source by using a JNDI service
+provider. At run time, a user application typically retrieves the data
+source through JNDI, and uses the data source's methods to establish a
+connection to the underlying database.
+
+A DataSource object maps to an instance of a database. In the Type 4
+driver product, the DataSource object acts as an interface between the
+application code and the database and enables connection with an DCS
+data source.
+
+[[security]]
+== Security
+
+Clients connect to the {project-name} platform with a valid user name
+and ID, using standard JDBC 3.0 APIs. An application can make multiple
+connections using different user IDs, and creating different Connection
+objects.
+
+The Type 4 driver provides for user name and password authentication.
+The password is encrypted with a proprietary algorithm provided by DCS.
+
+NOTE: There is no secure wire communication such as SSL provided for the
+communication between Type 4 driver and the {project-name} platform.
+
+<<<
+[[connection-by-using-the-datasource-interface]]
+== Connection by Using the DataSource Interface
+
+The `javax.sql.DataSource` interface is the preferred way to establish a
+connection to the database because this interface enhances the application
+portability. Portability is achieved by allowing the application to use a
+logical name for a data source instead of providing driver-specific 
information
+in the application. A logical name is mapped to a `javax.sql.DataSource`
+object through a naming service that uses the Java Naming and Directory
+Interface (JNDI). Using this DataSource method is particularly recommended
+for application servers.
+
+When an application requests a connection by using the `getConnection` 
method
+in the `DataSource`, then the method returns a `Connection` object.
+
+A `DataSource` object is a factory for `Connection` objects. An object that
+implements the `DataSource` interface is typically registered with a JNDI
+service provider.
+
+[[overview-of-tasks-to-deploy-datasource-objects]]
+=== Overview of Tasks to Deploy DataSource Objects
+
+Before an application can connect to a `DataSource` object, typically
+the system administrator deploys the `DataSource` object so that
+the application programmers can start using it.
+
+Data source properties are usually set by a system administrator using
+a GUI tool as part of the installation of the data 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61665243
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/accessing.adoc ---
@@ -0,0 +1,910 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[accessing-project-name-sql-databases]]
+= Accessing {project-name} SQL Databases
+
+[[data-sources]]
+== Data Sources
+
+The term *data source* logically refers to a database or other data
+storage entity. A JDBC (client) data source is physically a Java object 
that
+contains properties such as the URL of the physical database, the
+catalog to use when connecting to this database, and the schema to use
+when connecting to this database. The JDBC data source also contains
+methods for obtaining a JDBC connection to the underlying database.
+
+[[jdbc-data-source-client-side]]
+=== JDBC Data Source (client-side)
+
+All JDBC data source classes implement either the `javax.sql.DataSource`
+interface or the `javax.sql.ConnectionPoolDataSource` interface. The Type
+4 driver data source classes are `org.trafodion.t4jdbc.HPT4DataSource` and
+`org.trafodion.t4jdbc.HPT4ConnectionPoolDataSource`. (These classes are
+defined by the JDBC 3.0 specification.)
+
+Typically, a user or system administrator uses a tool to create a data
+source, and then registers the data source by using a JNDI service
+provider. At run time, a user application typically retrieves the data
+source through JNDI, and uses the data source's methods to establish a
+connection to the underlying database.
+
+A DataSource object maps to an instance of a database. In the Type 4
+driver product, the DataSource object acts as an interface between the
+application code and the database and enables connection with an DCS
+data source.
+
+[[security]]
+== Security
+
+Clients connect to the {project-name} platform with a valid user name
+and ID, using standard JDBC 3.0 APIs. An application can make multiple
+connections using different user IDs, and creating different Connection
+objects.
+
+The Type 4 driver provides for user name and password authentication.
+The password is encrypted with a proprietary algorithm provided by DCS.
+
+NOTE: There is no secure wire communication such as SSL provided for the
+communication between Type 4 driver and the {project-name} platform.
+
+<<<
+[[connection-by-using-the-datasource-interface]]
+== Connection by Using the DataSource Interface
+
+The `javax.sql.DataSource` interface is the preferred way to establish a
+connection to the database because this interface enhances the application
+portability. Portability is achieved by allowing the application to use a
+logical name for a data source instead of providing driver-specific 
information
+in the application. A logical name is mapped to a `javax.sql.DataSource`
+object through a naming service that uses the Java Naming and Directory
+Interface (JNDI). Using this DataSource method is particularly recommended
+for application servers.
+
+When an application requests a connection by using the `getConnection` 
method
+in the `DataSource`, then the method returns a `Connection` object.
+
+A `DataSource` object is a factory for `Connection` objects. An object that
+implements the `DataSource` interface is typically registered with a JNDI
+service provider.
+
+[[overview-of-tasks-to-deploy-datasource-objects]]
+=== Overview of Tasks to Deploy DataSource Objects
+
+Before an application can connect to a `DataSource` object, typically
+the system administrator deploys the `DataSource` object so that
+the application programmers can start using it.
+
+Data source properties are usually set by a system administrator using
+a GUI tool as part of the installation of the data 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61665223
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/accessing.adoc ---
@@ -0,0 +1,910 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[accessing-project-name-sql-databases]]
+= Accessing {project-name} SQL Databases
+
+[[data-sources]]
+== Data Sources
+
+The term *data source* logically refers to a database or other data
+storage entity. A JDBC (client) data source is physically a Java object 
that
+contains properties such as the URL of the physical database, the
+catalog to use when connecting to this database, and the schema to use
+when connecting to this database. The JDBC data source also contains
+methods for obtaining a JDBC connection to the underlying database.
+
+[[jdbc-data-source-client-side]]
+=== JDBC Data Source (client-side)
+
+All JDBC data source classes implement either the `javax.sql.DataSource`
+interface or the `javax.sql.ConnectionPoolDataSource` interface. The Type
+4 driver data source classes are `org.trafodion.t4jdbc.HPT4DataSource` and
+`org.trafodion.t4jdbc.HPT4ConnectionPoolDataSource`. (These classes are
+defined by the JDBC 3.0 specification.)
+
+Typically, a user or system administrator uses a tool to create a data
+source, and then registers the data source by using a JNDI service
+provider. At run time, a user application typically retrieves the data
+source through JNDI, and uses the data source's methods to establish a
+connection to the underlying database.
+
+A DataSource object maps to an instance of a database. In the Type 4
+driver product, the DataSource object acts as an interface between the
+application code and the database and enables connection with an DCS
+data source.
+
+[[security]]
+== Security
+
+Clients connect to the {project-name} platform with a valid user name
+and ID, using standard JDBC 3.0 APIs. An application can make multiple
+connections using different user IDs, and creating different Connection
+objects.
+
+The Type 4 driver provides for user name and password authentication.
+The password is encrypted with a proprietary algorithm provided by DCS.
+
+NOTE: There is no secure wire communication such as SSL provided for the
+communication between Type 4 driver and the {project-name} platform.
+
+<<<
+[[connection-by-using-the-datasource-interface]]
+== Connection by Using the DataSource Interface
+
+The `javax.sql.DataSource` interface is the preferred way to establish a
+connection to the database because this interface enhances the application
+portability. Portability is achieved by allowing the application to use a
+logical name for a data source instead of providing driver-specific 
information
+in the application. A logical name is mapped to a `javax.sql.DataSource`
+object through a naming service that uses the Java Naming and Directory
+Interface (JNDI). Using this DataSource method is particularly recommended
+for application servers.
+
+When an application requests a connection by using the `getConnection` 
method
+in the `DataSource`, then the method returns a `Connection` object.
+
+A `DataSource` object is a factory for `Connection` objects. An object that
+implements the `DataSource` interface is typically registered with a JNDI
+service provider.
+
+[[overview-of-tasks-to-deploy-datasource-objects]]
+=== Overview of Tasks to Deploy DataSource Objects
+
+Before an application can connect to a `DataSource` object, typically
+the system administrator deploys the `DataSource` object so that
+the application programmers can start using it.
+
+Data source properties are usually set by a system administrator using
+a GUI tool as part of the installation of the data 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61665226
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/accessing.adoc ---
@@ -0,0 +1,910 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[accessing-project-name-sql-databases]]
+= Accessing {project-name} SQL Databases
+
+[[data-sources]]
+== Data Sources
+
+The term *data source* logically refers to a database or other data
+storage entity. A JDBC (client) data source is physically a Java object 
that
+contains properties such as the URL of the physical database, the
+catalog to use when connecting to this database, and the schema to use
+when connecting to this database. The JDBC data source also contains
+methods for obtaining a JDBC connection to the underlying database.
+
+[[jdbc-data-source-client-side]]
+=== JDBC Data Source (client-side)
+
+All JDBC data source classes implement either the `javax.sql.DataSource`
+interface or the `javax.sql.ConnectionPoolDataSource` interface. The Type
+4 driver data source classes are `org.trafodion.t4jdbc.HPT4DataSource` and
+`org.trafodion.t4jdbc.HPT4ConnectionPoolDataSource`. (These classes are
+defined by the JDBC 3.0 specification.)
+
+Typically, a user or system administrator uses a tool to create a data
+source, and then registers the data source by using a JNDI service
+provider. At run time, a user application typically retrieves the data
+source through JNDI, and uses the data source's methods to establish a
+connection to the underlying database.
+
+A DataSource object maps to an instance of a database. In the Type 4
+driver product, the DataSource object acts as an interface between the
+application code and the database and enables connection with an DCS
+data source.
+
+[[security]]
+== Security
+
+Clients connect to the {project-name} platform with a valid user name
+and ID, using standard JDBC 3.0 APIs. An application can make multiple
+connections using different user IDs, and creating different Connection
+objects.
+
+The Type 4 driver provides for user name and password authentication.
+The password is encrypted with a proprietary algorithm provided by DCS.
+
+NOTE: There is no secure wire communication such as SSL provided for the
+communication between Type 4 driver and the {project-name} platform.
+
+<<<
+[[connection-by-using-the-datasource-interface]]
+== Connection by Using the DataSource Interface
+
+The `javax.sql.DataSource` interface is the preferred way to establish a
+connection to the database because this interface enhances the application
+portability. Portability is achieved by allowing the application to use a
+logical name for a data source instead of providing driver-specific 
information
+in the application. A logical name is mapped to a `javax.sql.DataSource`
+object through a naming service that uses the Java Naming and Directory
+Interface (JNDI). Using this DataSource method is particularly recommended
+for application servers.
+
+When an application requests a connection by using the `getConnection` 
method
+in the `DataSource`, then the method returns a `Connection` object.
+
+A `DataSource` object is a factory for `Connection` objects. An object that
+implements the `DataSource` interface is typically registered with a JNDI
+service provider.
+
+[[overview-of-tasks-to-deploy-datasource-objects]]
+=== Overview of Tasks to Deploy DataSource Objects
+
+Before an application can connect to a `DataSource` object, typically
+the system administrator deploys the `DataSource` object so that
+the application programmers can start using it.
+
+Data source properties are usually set by a system administrator using
+a GUI tool as part of the installation of the data 

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61665164
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/accessing.adoc ---
@@ -0,0 +1,910 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[accessing-project-name-sql-databases]]
+= Accessing {project-name} SQL Databases
+
+[[data-sources]]
+== Data Sources
+
+The term *data source* logically refers to a database or other data
+storage entity. A JDBC (client) data source is physically a Java object 
that
+contains properties such as the URL of the physical database, the
+catalog to use when connecting to this database, and the schema to use
+when connecting to this database. The JDBC data source also contains
+methods for obtaining a JDBC connection to the underlying database.
+
+[[jdbc-data-source-client-side]]
+=== JDBC Data Source (client-side)
+
+All JDBC data source classes implement either the `javax.sql.DataSource`
+interface or the `javax.sql.ConnectionPoolDataSource` interface. The Type
+4 driver data source classes are `org.trafodion.t4jdbc.HPT4DataSource` and
+`org.trafodion.t4jdbc.HPT4ConnectionPoolDataSource`. (These classes are
+defined by the JDBC 3.0 specification.)
+
+Typically, a user or system administrator uses a tool to create a data
+source, and then registers the data source by using a JNDI service
+provider. At run time, a user application typically retrieves the data
+source through JNDI, and uses the data source's methods to establish a
+connection to the underlying database.
+
+A DataSource object maps to an instance of a database. In the Type 4
+driver product, the DataSource object acts as an interface between the
+application code and the database and enables connection with an DCS
+data source.
+
+[[security]]
+== Security
+
+Clients connect to the {project-name} platform with a valid user name
+and ID, using standard JDBC 3.0 APIs. An application can make multiple
+connections using different user IDs, and creating different Connection
+objects.
+
+The Type 4 driver provides for user name and password authentication.
+The password is encrypted with a proprietary algorithm provided by DCS.
--- End diff --

This sentence can be "The password is encrypted" and remove the remaining 
text...


---
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.
---

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61665152
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/accessing.adoc ---
@@ -0,0 +1,910 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[accessing-project-name-sql-databases]]
+= Accessing {project-name} SQL Databases
+
+[[data-sources]]
+== Data Sources
+
+The term *data source* logically refers to a database or other data
+storage entity. A JDBC (client) data source is physically a Java object 
that
+contains properties such as the URL of the physical database, the
+catalog to use when connecting to this database, and the schema to use
+when connecting to this database. The JDBC data source also contains
+methods for obtaining a JDBC connection to the underlying database.
+
+[[jdbc-data-source-client-side]]
+=== JDBC Data Source (client-side)
+
+All JDBC data source classes implement either the `javax.sql.DataSource`
+interface or the `javax.sql.ConnectionPoolDataSource` interface. The Type
+4 driver data source classes are `org.trafodion.t4jdbc.HPT4DataSource` and
+`org.trafodion.t4jdbc.HPT4ConnectionPoolDataSource`. (These classes are
+defined by the JDBC 3.0 specification.)
+
+Typically, a user or system administrator uses a tool to create a data
+source, and then registers the data source by using a JNDI service
+provider. At run time, a user application typically retrieves the data
+source through JNDI, and uses the data source's methods to establish a
+connection to the underlying database.
+
+A DataSource object maps to an instance of a database. In the Type 4
+driver product, the DataSource object acts as an interface between the
+application code and the database and enables connection with an DCS
+data source.
+
+[[security]]
+== Security
+
+Clients connect to the {project-name} platform with a valid user name
+and ID, using standard JDBC 3.0 APIs. An application can make multiple
--- End diff --

Change ID to password 


---
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.
---

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[hegdean]

Github user hegdean commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61665112
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/accessing.adoc ---
@@ -0,0 +1,910 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[accessing-project-name-sql-databases]]
+= Accessing {project-name} SQL Databases
+
+[[data-sources]]
+== Data Sources
+
+The term *data source* logically refers to a database or other data
+storage entity. A JDBC (client) data source is physically a Java object 
that
+contains properties such as the URL of the physical database, the
+catalog to use when connecting to this database, and the schema to use
+when connecting to this database. The JDBC data source also contains
+methods for obtaining a JDBC connection to the underlying database.
+
+[[jdbc-data-source-client-side]]
+=== JDBC Data Source (client-side)
+
+All JDBC data source classes implement either the `javax.sql.DataSource`
+interface or the `javax.sql.ConnectionPoolDataSource` interface. The Type
+4 driver data source classes are `org.trafodion.t4jdbc.HPT4DataSource` and
--- End diff --

This should be org.trafodion.jdbc.t4 instead of org.trafodion.t4jdbc


---
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.
---

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61660766
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/accessing.adoc ---
@@ -0,0 +1,910 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[accessing-project-name-sql-databases]]
+= Accessing {project-name} SQL Databases
+
+[[data-sources]]
+== Data Sources
+
+The term *data source* logically refers to a database or other data
+storage entity. A JDBC (client) data source is physically a Java object 
that
+contains properties such as the URL of the physical database, the
+catalog to use when connecting to this database, and the schema to use
+when connecting to this database. The JDBC data source also contains
+methods for obtaining a JDBC connection to the underlying database.
+
+[[jdbc-data-source-client-side]]
+=== JDBC Data Source (client-side)
+
+All JDBC data source classes implement either the `javax.sql.DataSource`
+interface or the `javax.sql.ConnectionPoolDataSource` interface. The Type
+4 driver data source classes are `org.trafodion.t4jdbc.HPT4DataSource` and
+`org.trafodion.t4jdbc.HPT4ConnectionPoolDataSource`. (These classes are
+defined by the JDBC 3.0 specification.)
--- End diff --

Yes, that's my understanding. No one has had time to do the larger change 
to change the class names.


---
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.
---

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[gtapper]

Github user gtapper commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61660717
  
--- Diff: docs/jdbct4ref_guide/pom.xml ---
@@ -0,0 +1,297 @@
+
+http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
+  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd;>
+ 
+  4.0.0
+  org.apache.trafodion
+  jdbct4-ref-guide
+  ${env.TRAFODION_VER}
+  pom
+  Trafodion JDBC Type 4 Programmer's Reference Guide
+  This document describes how to use the JDBC Type 4 
Driver.
+  http://trafodion.incubator.apache.org
+  2015
+
+  
+org.apache.trafodion
+trafodion
+1.3.0
--- End diff --

Document versions are driven from env.TRAFODION_VERSION. The value here is
required but doesn't have a meaning that I'm aware of.

On Fri, Apr 29, 2016 at 5:27 PM, DaveBirdsall 
wrote:

> In docs/jdbct4ref_guide/pom.xml
> 

> :
>
> > +* @@@ END COPYRIGHT @@@
> > +-->
> > +  4.0.0
> > +  org.apache.trafodion
> > +  jdbct4-ref-guide
> > +  ${env.TRAFODION_VER}
> > +  pom
> > +  Trafodion JDBC Type 4 Programmer's Reference Guide
> > +  This document describes how to use the JDBC Type 4 
Driver.
> > +  http://trafodion.incubator.apache.org
> > +  2015
> > +
> > +  
> > +org.apache.trafodion
> > +trafodion
> > +1.3.0
>
> So, this is the 1.3.0 version? Is there also a 2.0,0 version?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly or view it on GitHub
> 

>



-- 
Thanks,

Gunnar
*If you think you can you can, if you think you can't you're right.*



---
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.
---

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[DaveBirdsall]

Github user DaveBirdsall commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61657816
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/accessing.adoc ---
@@ -0,0 +1,910 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[accessing-project-name-sql-databases]]
+= Accessing {project-name} SQL Databases
+
+[[data-sources]]
+== Data Sources
+
+The term *data source* logically refers to a database or other data
+storage entity. A JDBC (client) data source is physically a Java object 
that
+contains properties such as the URL of the physical database, the
+catalog to use when connecting to this database, and the schema to use
+when connecting to this database. The JDBC data source also contains
+methods for obtaining a JDBC connection to the underlying database.
+
+[[jdbc-data-source-client-side]]
+=== JDBC Data Source (client-side)
+
+All JDBC data source classes implement either the `javax.sql.DataSource`
+interface or the `javax.sql.ConnectionPoolDataSource` interface. The Type
+4 driver data source classes are `org.trafodion.t4jdbc.HPT4DataSource` and
+`org.trafodion.t4jdbc.HPT4ConnectionPoolDataSource`. (These classes are
+defined by the JDBC 3.0 specification.)
+
+Typically, a user or system administrator uses a tool to create a data
+source, and then registers the data source by using a JNDI service
+provider. At run time, a user application typically retrieves the data
+source through JNDI, and uses the data source's methods to establish a
+connection to the underlying database.
+
+A DataSource object maps to an instance of a database. In the Type 4
+driver product, the DataSource object acts as an interface between the
+application code and the database and enables connection with an DCS
--- End diff --

"an DCS" should be "a DCS". Have we defined DCS yet? If not we should spell 
it out.


---
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.
---

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[DaveBirdsall]

Github user DaveBirdsall commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61657710
  
--- Diff: docs/jdbct4ref_guide/src/asciidoc/_chapters/accessing.adoc ---
@@ -0,0 +1,910 @@
+
+/**
+ *@@@ 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 @@@
+ */
+
+
+[[accessing-project-name-sql-databases]]
+= Accessing {project-name} SQL Databases
+
+[[data-sources]]
+== Data Sources
+
+The term *data source* logically refers to a database or other data
+storage entity. A JDBC (client) data source is physically a Java object 
that
+contains properties such as the URL of the physical database, the
+catalog to use when connecting to this database, and the schema to use
+when connecting to this database. The JDBC data source also contains
+methods for obtaining a JDBC connection to the underlying database.
+
+[[jdbc-data-source-client-side]]
+=== JDBC Data Source (client-side)
+
+All JDBC data source classes implement either the `javax.sql.DataSource`
+interface or the `javax.sql.ConnectionPoolDataSource` interface. The Type
+4 driver data source classes are `org.trafodion.t4jdbc.HPT4DataSource` and
+`org.trafodion.t4jdbc.HPT4ConnectionPoolDataSource`. (These classes are
+defined by the JDBC 3.0 specification.)
--- End diff --

We still use "HP" in the class name... hmmm...


---
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.
---

[GitHub] incubator-trafodion pull request: Trafodion 1949: New JDBC Type 4 ...

[DaveBirdsall]

Github user DaveBirdsall commented on a diff in the pull request:

https://github.com/apache/incubator-trafodion/pull/457#discussion_r61657384
  
--- Diff: docs/jdbct4ref_guide/pom.xml ---
@@ -0,0 +1,297 @@
+
+http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
+  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd;>
+ 
+  4.0.0
+  org.apache.trafodion
+  jdbct4-ref-guide
+  ${env.TRAFODION_VER}
+  pom
+  Trafodion JDBC Type 4 Programmer's Reference Guide
+  This document describes how to use the JDBC Type 4 
Driver.
+  http://trafodion.incubator.apache.org
+  2015
+
+  
+org.apache.trafodion
+trafodion
+1.3.0
--- End diff --

So, this is the 1.3.0 version? Is there also a 2.0,0 version?


---
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.
---