Author: mtylenda
Date: Sat Jun 6 09:23:51 2009
New Revision: 782216
URL: http://svn.apache.org/viewvc?rev=782216&view=rev
Log:
OPENJPA-1127: Typos in user manual
Modified:
openjpa/branches/1.3.x/openjpa-project/src/doc/manual/jpa_overview_query.xml
openjpa/branches/1.3.x/openjpa-project/src/doc/manual/ref_guide_caching.xml
openjpa/branches/1.3.x/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml
openjpa/branches/1.3.x/openjpa-project/src/doc/manual/supported_databases.xml
Modified:
openjpa/branches/1.3.x/openjpa-project/src/doc/manual/jpa_overview_query.xml
URL:
http://svn.apache.org/viewvc/openjpa/branches/1.3.x/openjpa-project/src/doc/manual/jpa_overview_query.xml?rev=782216&r1=782215&r2=782216&view=diff
==============================================================================
---
openjpa/branches/1.3.x/openjpa-project/src/doc/manual/jpa_overview_query.xml
(original)
+++
openjpa/branches/1.3.x/openjpa-project/src/doc/manual/jpa_overview_query.xml
Sat Jun 6 09:23:51 2009
@@ -646,7 +646,7 @@
</title>
<para>
JPQL provides support for hints which are name/value pairs used to control
locking and optimization keywords in sql.
-The following example shows how to use the JPA hint api to set the
<classname>ReadLockMode</classname> and <classname>ResultCount</classname> in
the OpenJPA fetch plan. This will result in the sql keywords OPTIMIZE FOR 2
ROWS and UPDATE to be emitted into the sql provided that a pessimistic
LockManager is being used.
+The following example shows how to use the JPA hint api to set the
<classname>ReadLockMode</classname> and <classname>ResultCount</classname> in
the OpenJPA fetch plan. This will result in the sql keywords OPTIMIZE FOR 2
ROWS and FOR UPDATE to be emitted into the sql provided that a pessimistic
LockManager is being used.
</para>
<example id="jpa_query_hint1">
<title>
@@ -2463,10 +2463,10 @@
</title>
<para>
<itemizedlist><listitem><para>functions_returning_strings ::=
-CONCAT(string_primar y, string_primary) | SUBSTRING(string_primar y,
+CONCAT(string_primary, string_primary) | SUBSTRING(string_primary,
simple_arithmetic_expression, simple_arithmetic_expression) |
TRIM([[trim_specification] [trim_character] FROM] string_primary) |
-LOWER(string_primar y) | UPPER(string_primar y)
+LOWER(string_primary) | UPPER(string_primary)
</para>
</listitem>
<listitem>
@@ -2476,8 +2476,8 @@
</listitem>
<listitem>
<para>
-functions_returning_numerics ::= LENGTH(string_primar y) | LOCATE(string_primar
-y, string_primar y[, simple_arithmetic_expression])
+functions_returning_numerics ::= LENGTH(string_primary) |
+LOCATE(string_primary, string_primary[, simple_arithmetic_expression])
</para>
</listitem>
</itemizedlist>
Modified:
openjpa/branches/1.3.x/openjpa-project/src/doc/manual/ref_guide_caching.xml
URL:
http://svn.apache.org/viewvc/openjpa/branches/1.3.x/openjpa-project/src/doc/manual/ref_guide_caching.xml?rev=782216&r1=782215&r2=782216&view=diff
==============================================================================
--- openjpa/branches/1.3.x/openjpa-project/src/doc/manual/ref_guide_caching.xml
(original)
+++ openjpa/branches/1.3.x/openjpa-project/src/doc/manual/ref_guide_caching.xml
Sat Jun 6 09:23:51 2009
@@ -117,7 +117,7 @@
are loaded from the datastore.
</para>
<para>
-OpenJPA's data cache can in both single-JVM and multi-JVM environments.
+OpenJPA's data cache can operate in both single-JVM and multi-JVM environments.
Multi-JVM caching is achieved through the use of the distributed event
notification framework described in <xref linkend="ref_guide_event"/>, or
through custom integrations with a third-party distributed cache.
Modified:
openjpa/branches/1.3.x/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml
URL:
http://svn.apache.org/viewvc/openjpa/branches/1.3.x/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml?rev=782216&r1=782215&r2=782216&view=diff
==============================================================================
--- openjpa/branches/1.3.x/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml
(original)
+++ openjpa/branches/1.3.x/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml
Sat Jun 6 09:23:51 2009
@@ -2098,7 +2098,7 @@
</indexterm>
<literal>StoreLargeNumbersAsStrings</literal>: When true, the dictionary
prefers to store Java fields of
-type <classname>BigInteger</classname> and <classname>BigDecimal</classname>)
+type <classname>BigInteger</classname> and <classname>BigDecimal</classname>
as string values in the database. Likewise, the dictionary will instruct
the mapping tool to map these Java types to character columns.
Because some databases have limitations on the number of digits that can
Modified:
openjpa/branches/1.3.x/openjpa-project/src/doc/manual/supported_databases.xml
URL:
http://svn.apache.org/viewvc/openjpa/branches/1.3.x/openjpa-project/src/doc/manual/supported_databases.xml?rev=782216&r1=782215&r2=782216&view=diff
==============================================================================
---
openjpa/branches/1.3.x/openjpa-project/src/doc/manual/supported_databases.xml
(original)
+++
openjpa/branches/1.3.x/openjpa-project/src/doc/manual/supported_databases.xml
Sat Jun 6 09:23:51 2009
@@ -374,8 +374,8 @@
</listitem>
<listitem>
<para>
-Interbase does not support the <literal>LOWER</literal>, <literal>SUBSTRING
-</literal>, or <literal>INSTR</literal> SQL functions>
+Interbase does not support the <literal>LOWER</literal>,
+<literal>SUBSTRING</literal>, or <literal>INSTR</literal> SQL functions.
</para>
</listitem>
</itemizedlist>
@@ -821,7 +821,7 @@
<para>
When using large result sets with MySQL there are a number of documented
limitations.
Please read the section titled "ResultSet" in the "MySQL JDBC API
Implementation Notes".
-The net of these limitations is that you will have to read all of the rows of a
+The net effect of these limitations is that you will have to read all of the
rows of a
result set (or close the connection) before you can issue any other queries on
the connection, or an exception will be thrown. Setting openjpa.FetchBatchSize
to any value greater than zero will enable streaming result sets.
