This is an automated email from the ASF dual-hosted git repository. asf-gitbox-commits pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/cayenne.git
commit 69d35b4a7e9279f7b79bb60c65e347c8455beaef Author: Andrus Adamchik <[email protected]> AuthorDate: Sun Jun 28 15:18:58 2026 -0400 cleanup --- cayenne/src/main/java/org/apache/cayenne/query/ProcedureQuery.java | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/cayenne/src/main/java/org/apache/cayenne/query/ProcedureQuery.java b/cayenne/src/main/java/org/apache/cayenne/query/ProcedureQuery.java index df9a063b0..d7643213c 100644 --- a/cayenne/src/main/java/org/apache/cayenne/query/ProcedureQuery.java +++ b/cayenne/src/main/java/org/apache/cayenne/query/ProcedureQuery.java @@ -45,7 +45,7 @@ import java.util.Map; * {@link org.apache.cayenne.access.DataContext#performQuery(Query)} makes sense only if * the stored procedure returns a single result set (or alternatively returns a result via * OUT parameters and no other result sets). It is still OK if data modification occurs as - * a side effect. However if the query returns more then one result set, a more generic + * a side effect. However, if the query returns more then one result set, a more generic * form should be used: * {@link org.apache.cayenne.access.DataContext#performGenericQuery(Query)}. * </p> @@ -141,13 +141,13 @@ public class ProcedureQuery extends AbstractQuery implements ParameterizedQuery * <p> * <i>Note that if a procedure returns ResultSet in an OUT parameter, it is returned * prior to any other result sets (though in practice database engines usually support - * only one mechanism for returning result sets. </i> + * only one mechanism for returning result sets).</i> * </p> * * @since 5.0 */ public List<ProcedureColumn[]> getResultDescriptors() { - return resultDescriptors != null ? resultDescriptors : Collections.<ProcedureColumn[]>emptyList(); + return resultDescriptors != null ? resultDescriptors : Collections.emptyList(); } /**
