Author: ppoddar
Date: Fri May 21 14:14:44 2010
New Revision: 947016
URL: http://svn.apache.org/viewvc?rev=947016&view=rev
Log:
Missing error text for usage of named parameters in native SQL
Modified:
openjpa/trunk/openjpa-persistence/src/main/resources/org/apache/openjpa/persistence/localizer.properties
Modified:
openjpa/trunk/openjpa-persistence/src/main/resources/org/apache/openjpa/persistence/localizer.properties
URL:
http://svn.apache.org/viewvc/openjpa/trunk/openjpa-persistence/src/main/resources/org/apache/openjpa/persistence/localizer.properties?rev=947016&r1=947015&r2=947016&view=diff
==============================================================================
---
openjpa/trunk/openjpa-persistence/src/main/resources/org/apache/openjpa/persistence/localizer.properties
(original)
+++
openjpa/trunk/openjpa-persistence/src/main/resources/org/apache/openjpa/persistence/localizer.properties
Fri May 21 14:14:44 2010
@@ -110,6 +110,9 @@ ser-cls-query: Writing query "{1}" in cl
ser-query: Writing query "{1}".
ser-sequence: Writing sequence "{0}".
no-sql: You must provide a SQL string when creating a native query.
+no-named-params: Named parameter "{0}" is used in native SQL query "{1}". \
+ But named parameter is not allowed in native SQL query, use integer \
+ parameter ?1, ?2 etc.
bad-pos-params: Positional parameter "{0}" is invalid for native query "{1}".
\
Use only 1-based positional parameter in native queries.
bad-param-type: The parameter "{1}" in query "{0}" is set to a value of type \
