From a702efd7cd6b100eb2135bde0c58fc2b7ca27b72 Mon Sep 17 00:00:00 2001 From: Gavin King Date: Tue, 29 Mar 2005 02:25:45 +0000 Subject: [PATCH] rename result- to return- git-svn-id: https://svn.jboss.org/repos/hibernate/trunk/Hibernate3/doc@6232 1b8cb986-b30d-0410-93ca-fae66ebed9b2 --- reference/en/modules/query_sql.xml | 44 +++++++++++++++--------------- 1 file changed, 22 insertions(+), 22 deletions(-) diff --git a/reference/en/modules/query_sql.xml b/reference/en/modules/query_sql.xml index 8d9fbf93fe..9d293f80e2 100644 --- a/reference/en/modules/query_sql.xml +++ b/reference/en/modules/query_sql.xml @@ -138,18 +138,18 @@ List loggedCats = sess.createSQLQuery(sql) - Using property-result to explicitly specify column/alias names + Using return-property to explicitly specify column/alias names - With <property-result> you can explicitly tell Hibernate what columns + With <return-property> you can explicitly tell Hibernate what columns to use as opposed to use {}-syntax to let Hibernate inject its own aliases. - - - + + + SELECT person.NAME AS myName, person.AGE AS myAge, @@ -158,16 +158,16 @@ List loggedCats = sess.createSQLQuery(sql) ]]> - <property-result> also works with multiple columns. This solves a limitation with + <return-property> also works with multiple columns. This solves a limitation with the {}-syntax which can not allow fine grained control of multi-column properties. - - - - - + + + + + SELECT EMPLOYEE AS {emp.employee}, EMPLOYER AS {emp.employer}, STARTDATE AS {emp.startDate}, ENDDATE AS {emp.endDate}, @@ -178,7 +178,7 @@ List loggedCats = sess.createSQLQuery(sql) ]]> - Notice that in this example we used <property-result> in combination + Notice that in this example we used <return-property> in combination with the {}-syntax for injection. Allowing users to choose how they want to refer column and properties. @@ -215,16 +215,16 @@ BEGIN - - - - - - - - - - + + + + + + + + + + { ? = call selectAllEmployments() } ]]>