From 790259abd49893f24b68330aa6879d9731300df9 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Mon, 26 Nov 2001 19:07:11 +0000 Subject: [PATCH] More tag cleanups. --- doc/src/sgml/jdbc.sgml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/src/sgml/jdbc.sgml b/doc/src/sgml/jdbc.sgml index dc9b3847c2..fc3106ad3e 100644 --- a/doc/src/sgml/jdbc.sgml +++ b/doc/src/sgml/jdbc.sgml @@ -1,5 +1,5 @@ @@ -584,7 +584,7 @@ st.close(); need to understand the limitations of each method. The bytea datatype is not well suited for storing very large amounts of binary data. While a column of type - bytea can hold upto 1Gig of binary data, it would + bytea can hold upto 1Gig of binary data, it would require a huge amount of memory (RAM) to process such a large value. The Large Object method for storing binary data is better suited to storing very large values, @@ -623,7 +623,7 @@ st.close(); To use the Large Object functionality you can use either the LargeObject API - provided by the PostgreSQL + provided by the PostgreSQL JDBC Driver, or by using the getBLOB() and setBLOB() methods. @@ -644,7 +644,7 @@ st.close(); and setBLOB() methods may no longer interact with Large Objects and will instead work on bytea datatypes. So it is recommended that you - use the LargeObject API + use the LargeObject API if you intend to use Large Objects. @@ -2492,7 +2492,7 @@ public void unlink(int oid) throws SQLException - The PostgreSQL JDBC Driver + The PostgreSQL JDBC Driver is thread safe. Consequently, if your application uses multiple threads then you do not have to worry about complex algorithms to ensure that only one