aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Eisentraut <peter_e@gmx.net>2010-08-17 04:47:04 +0000
committerPeter Eisentraut <peter_e@gmx.net>2010-08-17 04:47:04 +0000
commit7b243aa666e49431f45bec71565d8ca49b7c9ef6 (patch)
tree74564ac2603852523afb7cf836e7fe74223deb66
parent5194b9d04988ae10b94b86ba5bc1110377079241 (diff)
downloadpostgresql-7b243aa666e49431f45bec71565d8ca49b7c9ef6.tar.gz
postgresql-7b243aa666e49431f45bec71565d8ca49b7c9ef6.zip
Revert: looks like Binary Large OBject[sic] wasn't a misspelling
-rw-r--r--doc/src/sgml/lo.sgml4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/lo.sgml b/doc/src/sgml/lo.sgml
index 98959832b23..3415105cdfc 100644
--- a/doc/src/sgml/lo.sgml
+++ b/doc/src/sgml/lo.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/lo.sgml,v 1.5 2010/08/17 04:37:20 petere Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/lo.sgml,v 1.6 2010/08/17 04:47:04 petere Exp $ -->
<sect1 id="lo">
<title>lo</title>
@@ -19,7 +19,7 @@
<para>
One of the problems with the JDBC driver (and this affects the ODBC driver
also), is that the specification assumes that references to BLOBs (Binary
- Large Objects) are stored within a table, and if that entry is changed, the
+ Large OBjects) are stored within a table, and if that entry is changed, the
associated BLOB is deleted from the database.
</para>