mirror of https://github.com/apache/openjpa.git
OPENJPA-111: Minor message typo corrections.
git-svn-id: https://svn.apache.org/repos/asf/openjpa/trunk@686359 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
parent
d76c646acc
commit
cf0985e524
|
@ -38,7 +38,7 @@ pessimistic-mutate: You are attempting to directly mutate a persistent second \
|
|||
class object (such as a collection or map field) that you obtained before \
|
||||
the transaction began. After beginning a datastore transaction, you \
|
||||
must re-obtain any references to mutable second class objects from the \
|
||||
owning persistent object. Detected attmpt to mutate value of field "{0}" \
|
||||
owning persistent object. Detected attempt to mutate value of field "{0}" \
|
||||
in instance "{1}". This instance may not be locked correctly.
|
||||
not-derefed: Encountered unknown dependent instance "{0}". This error is \
|
||||
often caused by either removing a dependent instance from one dependent \
|
||||
|
@ -291,7 +291,7 @@ unbound-params: Cannot execute query; some declared parameters were not given \
|
|||
extra-params: More parameters were passed to execute() than were declared: \
|
||||
{1} parameters were specified for query execution, but only {0} \
|
||||
parameters were declared in the query.
|
||||
null-primitive-param: Parameter "{0}" was declared with a primtive type, but \
|
||||
null-primitive-param: Parameter "{0}" was declared with a primitive type, but \
|
||||
has been given a null value.
|
||||
merged-aggregate: This query on candidate type "{0}" with filter "{1}" \
|
||||
involves combining the results of multiple sub-queries. However, because \
|
||||
|
@ -342,7 +342,7 @@ bad-datastore-method: Method "{0}(StoreContext, ClassMetaData, boolean, Map, \
|
|||
the method name supplied in your MethodQL query filter. OpenJPA is \
|
||||
attempting to execute this query against the datastore; if you implemented \
|
||||
the in-memory method instead (a method with the same signature but with an \
|
||||
Object argument) and want this query to execute in-memory, supplly a \
|
||||
Object argument) and want this query to execute in-memory, supply a \
|
||||
Collection of candidates to filter.
|
||||
only-update-constants: Bulk update queries when executed in memory \
|
||||
may only update to constant values.
|
||||
|
@ -358,7 +358,7 @@ savepoint-init: This savepoint has already been initialized.
|
|||
savepoint-flush-not-supported: The configured SavepointManager does not \
|
||||
support incremental flushing when a savepoint has been set. You must \
|
||||
release your savepoints before flushing.
|
||||
callback-err: Errors occured processing listener callbacks. See the nested \
|
||||
callback-err: Errors occurred processing listener callbacks. See the nested \
|
||||
exceptions for details.
|
||||
bad-agg-listener-hint: Query hint value "{0}" ({1}) cannot be converted into \
|
||||
an aggregate listener.
|
||||
|
@ -402,4 +402,4 @@ no-interface-metadata: No metadata was found for managed interface {0}.
|
|||
fetch-configuration-stack-empty: Fetch configuration stack is empty.
|
||||
gap-query-param: Parameter {1} for query "{0}" exceeds the number of {2} \
|
||||
bound parameters with following values "{3}". This can happen if you have \
|
||||
decalred but missed to bind values for one or more parameters.
|
||||
declared but missed to bind values for one or more parameters.
|
||||
|
|
Loading…
Reference in New Issue