[hibernate-commits] Hibernate SVN: r18717 - in core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot: content and 1 other directory.
hibernate-commits at lists.jboss.org
hibernate-commits at lists.jboss.org
Sun Feb 7 23:56:57 EST 2010
Author: stliu
Date: 2010-02-07 23:56:55 -0500 (Sun, 07 Feb 2010)
New Revision: 18717
Removed:
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/bibliography.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/preface.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/legal_notice.pot
Modified:
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/Author_Group.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/Hibernate_Core_Reference_Guide.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/architecture.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/association_mapping.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/basic_mapping.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/batch.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/best_practices.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/collection_mapping.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/component_mapping.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/configuration.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/events.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/example_mappings.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/example_parentchild.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/example_weblog.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/filters.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/inheritance_mapping.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/performance.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/persistent_classes.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/portability.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/query_criteria.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/query_hql.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/query_sql.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/session_api.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/toolset_guide.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/transactions.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/tutorial.pot
core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/xml.pot
Log:
HHH-4728 Import work done by Red Hat translation team
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/Author_Group.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/Author_Group.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/Author_Group.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,190 +1,14 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-16 18:47+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:17\n"
+"PO-Revision-Date: 2010-01-08T04:07:17\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-#. Tag: author
-#: author_group.xml:27
-#, no-c-format
-msgid "<firstname>Gavin</firstname> <surname>King</surname>"
-msgstr ""
-
-#. Tag: author
-#: author_group.xml:31
-#, no-c-format
-msgid "<firstname>Christian</firstname> <surname>Bauer</surname>"
-msgstr ""
-
-#. Tag: author
-#: author_group.xml:35
-#, no-c-format
-msgid "<firstname>Max</firstname> <othername>Rydahl</othername> <surname>Andersen</surname>"
-msgstr ""
-
-#. Tag: author
-#: author_group.xml:40
-#, no-c-format
-msgid "<author><firstname>Emmanuel</firstname> <surname>Bernard</surname></author>"
-msgstr ""
-
-#. Tag: author
-#: author_group.xml:44
-#, no-c-format
-msgid "<firstname>Steve</firstname> <surname>Ebersole</surname>"
-msgstr ""
-
-#. Tag: othercredit
-#: author_group.xml:49
-#, no-c-format
-msgid "<firstname>James</firstname> <surname>Cobb</surname>"
-msgstr ""
-
-#. Tag: shortaffil
-#: author_group.xml:53 author_group.xml:60
-#, no-c-format
-msgid "Graphic Design"
-msgstr ""
-
-#. Tag: othercredit
-#: author_group.xml:56
-#, no-c-format
-msgid "<firstname>Cheyenne</firstname> <surname>Weaver</surname>"
-msgstr ""
-
-#. Tag: othercredit
-#: author_group.xml:69
-#, no-c-format
-msgid "<othername><![CDATA[Bernardo Antonio Buffa Colomé]]></othername> <email>kreimer at bbs.frc.utn.edu.ar</email>"
-msgstr ""
-
-#. Tag: othercredit
-#: author_group.xml:79
-#, no-c-format
-msgid "<firstname>Vincent</firstname> <surname>Ricard</surname>"
-msgstr ""
-
-#. Tag: othercredit
-#: author_group.xml:83
-#, no-c-format
-msgid "<firstname>Sebastien</firstname> <surname>Cesbron</surname>"
-msgstr ""
-
-#. Tag: othercredit
-#: author_group.xml:87
-#, no-c-format
-msgid "<firstname>Michael</firstname> <surname>Courcy</surname>"
-msgstr ""
-
-#. Tag: othercredit
-#: author_group.xml:91
-#, no-c-format
-msgid "<firstname>Vincent</firstname> <surname>Giguère</surname>"
-msgstr ""
-
-#. Tag: othercredit
-#: author_group.xml:95
-#, no-c-format
-msgid "<firstname>Baptiste</firstname> <surname>Mathus</surname>"
-msgstr ""
-
-#. Tag: othercredit
-#: author_group.xml:99
-#, no-c-format
-msgid "<othercredit><firstname>Emmanuel</firstname> <surname>Bernard</surname></othercredit>"
-msgstr ""
-
-#. Tag: othercredit
-#: author_group.xml:103
-#, no-c-format
-msgid "<firstname>Anthony</firstname> <surname>Patricio</surname>"
-msgstr ""
-
-#. Tag: othercredit
-#: author_group.xml:113
-#, no-c-format
-msgid "<firstname>Alvaro</firstname> <surname>Netto</surname> <email>alvaronetto at cetip.com.br</email>"
-msgstr ""
-
-#. Tag: othercredit
-#: author_group.xml:118
-#, no-c-format
-msgid "<firstname>Anderson</firstname> <surname>Braulio</surname> <email>andersonbraulio at gmail.com</email>"
-msgstr ""
-
-#. Tag: othercredit
-#: author_group.xml:123
-#, no-c-format
-msgid "<firstname>Daniel Vieira</firstname> <surname>Costa</surname> <email>danielvc at gmail.com</email>"
-msgstr ""
-
-#. Tag: othercredit
-#: author_group.xml:128
-#, no-c-format
-msgid "<firstname>Francisco</firstname> <surname>gamarra</surname> <email>francisco.gamarra at gmail.com</email>"
-msgstr ""
-
-#. Tag: othercredit
-#: author_group.xml:133
-#, no-c-format
-msgid "<firstname>Gamarra</firstname> <email>mauricio.gamarra at gmail.com</email>"
-msgstr ""
-
-#. Tag: othercredit
-#: author_group.xml:137
-#, no-c-format
-msgid "<firstname>Luiz Carlos</firstname> <surname>Rodrigues</surname> <email>luizcarlos_rodrigues at yahoo.com.br</email>"
-msgstr ""
-
-#. Tag: othercredit
-#: author_group.xml:142
-#, no-c-format
-msgid "<firstname>Marcel</firstname> <surname>Castelo</surname> <email>marcel.castelo at gmail.com</email>"
-msgstr ""
-
-#. Tag: othercredit
-#: author_group.xml:147
-#, no-c-format
-msgid "<firstname>Paulo</firstname> <surname>César</surname> <email>paulocol at gmail.com</email>"
-msgstr ""
-
-#. Tag: othercredit
-#: author_group.xml:152
-#, no-c-format
-msgid "<firstname>Pablo L.</firstname> <surname>de Miranda</surname> <email>pablolmiranda at gmail.com</email>"
-msgstr ""
-
-#. Tag: othercredit
-#: author_group.xml:157
-#, no-c-format
-msgid "<firstname>Renato</firstname> <surname>Deggau</surname> <email>rdeggau at gmail.com</email>"
-msgstr ""
-
-#. Tag: othercredit
-#: author_group.xml:162
-#, no-c-format
-msgid "<firstname>Rogério</firstname> <surname>Araújo</surname> <email>rgildoaraujo at yahoo.com.br</email>"
-msgstr ""
-
-#. Tag: othercredit
-#: author_group.xml:167
-#, no-c-format
-msgid "<firstname>Wanderson</firstname> <surname>Siqueira</surname> <email>wandersonxs at gmail.com</email>"
-msgstr ""
-
-#. Tag: othercredit
-#: author_group.xml:178
-#, no-c-format
-msgid "<firstname>Cao</firstname> <surname>Xiaogang</surname> <affiliation> <orgname>RedSaga</orgname> </affiliation> <contrib>Translation Lead</contrib> <email>caoxg at yahoo.com</email>"
-msgstr ""
-
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/Hibernate_Core_Reference_Guide.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/Hibernate_Core_Reference_Guide.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/Hibernate_Core_Reference_Guide.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,34 +1,14 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-24 02:10+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:17\n"
+"PO-Revision-Date: 2010-01-08T04:07:17\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-#. Tag: title
-#: Hibernate_Reference.xml:35
-#, no-c-format
-msgid "HIBERNATE - Relational Persistence for Idiomatic Java"
-msgstr ""
-
-#. Tag: subtitle
-#: Hibernate_Reference.xml:36
-#, no-c-format
-msgid "Hibernate Reference Documentation"
-msgstr ""
-
-#. Tag: holder
-#: Hibernate_Reference.xml:51
-#, no-c-format
-msgid "©rightHolder;"
-msgstr ""
-
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/architecture.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/architecture.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/architecture.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,327 +1,273 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-10 21:02+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:17\n"
+"PO-Revision-Date: 2010-01-08T04:07:17\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
-#: architecture.xml:30
#, no-c-format
msgid "Architecture"
msgstr ""
#. Tag: title
-#: architecture.xml:33
#, no-c-format
msgid "Overview"
msgstr ""
#. Tag: para
-#: architecture.xml:35
#, no-c-format
msgid "The diagram below provides a high-level view of the Hibernate architecture:"
msgstr ""
#. Tag: para
-#: architecture.xml:50
#, no-c-format
msgid "We do not have the scope in this document to provide a more detailed view of all the runtime architectures available; Hibernate is flexible and supports several different approaches. We will, however, show the two extremes: \"minimal\" architecture and \"comprehensive\" architecture."
msgstr ""
#. Tag: para
-#: architecture.xml:56
#, no-c-format
msgid "This next diagram illustrates how Hibernate utilizes database and configuration data to provide persistence services, and persistent objects, to the application."
msgstr ""
#. Tag: para
-#: architecture.xml:61
#, no-c-format
msgid "The \"minimal\" architecture has the application provide its own JDBC connections and manage its own transactions. This approach uses a minimal subset of Hibernate's APIs:"
msgstr ""
#. Tag: para
-#: architecture.xml:78
#, no-c-format
msgid "The \"comprehensive\" architecture abstracts the application away from the underlying JDBC/JTA APIs and allows Hibernate to manage the details."
msgstr ""
#. Tag: para
-#: architecture.xml:92
#, no-c-format
msgid "Here are some definitions of the objects depicted in the diagrams:"
msgstr ""
#. Tag: term
-#: architecture.xml:97
#, no-c-format
msgid "SessionFactory (<literal>org.hibernate.SessionFactory</literal>)"
msgstr ""
#. Tag: para
-#: architecture.xml:99
#, no-c-format
msgid "A threadsafe, immutable cache of compiled mappings for a single database. A factory for <literal>Session</literal> and a client of <literal>ConnectionProvider</literal>, <literal>SessionFactory</literal> can hold an optional (second-level) cache of data that is reusable between transactions at a process, or cluster, level."
msgstr ""
#. Tag: term
-#: architecture.xml:109
#, no-c-format
msgid "Session (<literal>org.hibernate.Session</literal>)"
msgstr ""
#. Tag: para
-#: architecture.xml:111
#, no-c-format
msgid "A single-threaded, short-lived object representing a conversation between the application and the persistent store. It wraps a JDBC connection and is a factory for <literal>Transaction</literal>. <literal>Session</literal> holds a mandatory first-level cache of persistent objects that are used when navigating the object graph or looking up objects by identifier."
msgstr ""
#. Tag: term
-#: architecture.xml:121
#, no-c-format
msgid "Persistent objects and collections"
msgstr ""
#. Tag: para
-#: architecture.xml:123
#, no-c-format
msgid "Short-lived, single threaded objects containing persistent state and business function. These can be ordinary JavaBeans/POJOs. They are associated with exactly one <literal>Session</literal>. Once the <literal>Session</literal> is closed, they will be detached and free to use in any application layer (for example, directly as data transfer objects to and from presentation)."
msgstr ""
#. Tag: term
-#: architecture.xml:133
#, no-c-format
msgid "Transient and detached objects and collections"
msgstr ""
#. Tag: para
-#: architecture.xml:135
#, no-c-format
msgid "Instances of persistent classes that are not currently associated with a <literal>Session</literal>. They may have been instantiated by the application and not yet persisted, or they may have been instantiated by a closed <literal>Session</literal>."
msgstr ""
#. Tag: term
-#: architecture.xml:144
#, no-c-format
msgid "Transaction (<literal>org.hibernate.Transaction</literal>)"
msgstr ""
#. Tag: para
-#: architecture.xml:146
#, no-c-format
msgid "(Optional) A single-threaded, short-lived object used by the application to specify atomic units of work. It abstracts the application from the underlying JDBC, JTA or CORBA transaction. A <literal>Session</literal> might span several <literal>Transaction</literal>s in some cases. However, transaction demarcation, either using the underlying API or <literal>Transaction</literal>, is never optional."
msgstr ""
#. Tag: term
-#: architecture.xml:157
#, no-c-format
msgid "ConnectionProvider (<literal>org.hibernate.connection.ConnectionProvider</literal>)"
msgstr ""
#. Tag: para
-#: architecture.xml:159
#, no-c-format
msgid "(Optional) A factory for, and pool of, JDBC connections. It abstracts the application from underlying <literal>Datasource</literal> or <literal>DriverManager</literal>. It is not exposed to application, but it can be extended and/or implemented by the developer."
msgstr ""
#. Tag: term
-#: architecture.xml:167
#, no-c-format
msgid "TransactionFactory (<literal>org.hibernate.TransactionFactory</literal>)"
msgstr ""
#. Tag: para
-#: architecture.xml:169
#, no-c-format
msgid "(Optional) A factory for <literal>Transaction</literal> instances. It is not exposed to the application, but it can be extended and/or implemented by the developer."
msgstr ""
-#. Tag: emphasis
-#: architecture.xml:176
+#. Tag: term
#, no-c-format
-msgid "Extension Interfaces"
+msgid "<emphasis>Extension Interfaces</emphasis>"
msgstr ""
#. Tag: para
-#: architecture.xml:178
#, no-c-format
msgid "Hibernate offers a range of optional extension interfaces you can implement to customize the behavior of your persistence layer. See the API documentation for details."
msgstr ""
#. Tag: para
-#: architecture.xml:187
#, no-c-format
msgid "Given a \"minimal\" architecture, the application bypasses the <literal>Transaction</literal>/<literal>TransactionFactory</literal> and/or <literal>ConnectionProvider</literal> APIs to communicate with JTA or JDBC directly."
msgstr ""
#. Tag: title
-#: architecture.xml:195
#, no-c-format
msgid "Instance states"
msgstr ""
#. Tag: para
-#: architecture.xml:196
#, no-c-format
msgid "An instance of a persistent class can be in one of three different states. These states are defined in relation to a <emphasis>persistence context</emphasis>. The Hibernate <literal>Session</literal> object is the persistence context. The three different states are as follows:"
msgstr ""
#. Tag: term
-#: architecture.xml:204
#, no-c-format
msgid "transient"
msgstr ""
#. Tag: para
-#: architecture.xml:206
#, no-c-format
msgid "The instance is not associated with any persistence context. It has no persistent identity or primary key value."
msgstr ""
#. Tag: term
-#: architecture.xml:214
#, no-c-format
msgid "persistent"
msgstr ""
#. Tag: para
-#: architecture.xml:216
#, no-c-format
msgid "The instance is currently associated with a persistence context. It has a persistent identity (primary key value) and can have a corresponding row in the database. For a particular persistence context, Hibernate <emphasis>guarantees</emphasis> that persistent identity is equivalent to Java identity in relation to the in-memory location of the object."
msgstr ""
#. Tag: term
-#: architecture.xml:228
#, no-c-format
msgid "detached"
msgstr ""
#. Tag: para
-#: architecture.xml:230
#, no-c-format
msgid "The instance was once associated with a persistence context, but that context was closed, or the instance was serialized to another process. It has a persistent identity and can have a corresponding row in the database. For detached instances, Hibernate does not guarantee the relationship between persistent identity and Java identity."
msgstr ""
#. Tag: title
-#: architecture.xml:245
#, no-c-format
msgid "JMX Integration"
msgstr ""
#. Tag: para
-#: architecture.xml:247
#, no-c-format
msgid "JMX is the J2EE standard for the management of Java components. Hibernate can be managed via a JMX standard service. AN MBean implementation is provided in the distribution: <literal>org.hibernate.jmx.HibernateService</literal>."
msgstr ""
#. Tag: para
-#: architecture.xml:253
#, no-c-format
msgid "For an example of how to deploy Hibernate as a JMX service on the JBoss Application Server, please see the JBoss User Guide. JBoss AS also provides these benefits if you deploy using JMX:"
msgstr ""
#. Tag: para
-#: architecture.xml:261
#, no-c-format
msgid "<emphasis>Session Management</emphasis>: the Hibernate <literal>Session</literal>'s life cycle can be automatically bound to the scope of a JTA transaction. This means that you no longer have to manually open and close the <literal>Session</literal>; this becomes the job of a JBoss EJB interceptor. You also do not have to worry about transaction demarcation in your code (if you would like to write a portable persistence layer use the optional Hibernate <literal>Transaction</literal> API for this). You call the <literal>HibernateContext</literal> to access a <literal>Session</literal>."
msgstr ""
#. Tag: para
-#: architecture.xml:273
#, no-c-format
msgid "<emphasis>HAR deployment</emphasis>: the Hibernate JMX service is deployed using a JBoss service deployment descriptor in an EAR and/or SAR file, as it supports all the usual configuration options of a Hibernate <literal>SessionFactory</literal>. However, you still need to name all your mapping files in the deployment descriptor. If you use the optional HAR deployment, JBoss will automatically detect all mapping files in your HAR file."
msgstr ""
#. Tag: para
-#: architecture.xml:284
#, no-c-format
msgid "Consult the JBoss AS user guide for more information about these options."
msgstr ""
#. Tag: para
-#: architecture.xml:288
#, no-c-format
-msgid "Another feature available as a JMX service is runtime Hibernate statistics. See <xref linkend=\"configuration-optional-statistics\"/> for more information."
+msgid "Another feature available as a JMX service is runtime Hibernate statistics. See <xref linkend=\"configuration-optional-statistics\" /> for more information."
msgstr ""
#. Tag: title
-#: architecture.xml:295
#, no-c-format
msgid "JCA Support"
msgstr ""
#. Tag: para
-#: architecture.xml:296
#, no-c-format
msgid "Hibernate can also be configured as a JCA connector. Please see the website for more information. Please note, however, that at this stage Hibernate JCA support is under development."
msgstr ""
#. Tag: title
-#: architecture.xml:303
#, no-c-format
msgid "Contextual sessions"
msgstr ""
#. Tag: para
-#: architecture.xml:304
#, no-c-format
msgid "Most applications using Hibernate need some form of \"contextual\" session, where a given session is in effect throughout the scope of a given context. However, across applications the definition of what constitutes a context is typically different; different contexts define different scopes to the notion of current. Applications using Hibernate prior to version 3.0 tended to utilize either home-grown <literal>ThreadLocal</literal>-based contextual sessions, helper classes such as <literal>HibernateUtil</literal>, or utilized third-party frameworks, such as Spring or Pico, which provided proxy/interception-based contextual sessions."
msgstr ""
#. Tag: para
-#: architecture.xml:313
#, no-c-format
msgid "Starting with version 3.0.1, Hibernate added the <literal>SessionFactory.getCurrentSession()</literal> method. Initially, this assumed usage of <literal>JTA</literal> transactions, where the <literal>JTA</literal> transaction defined both the scope and context of a current session. Given the maturity of the numerous stand-alone <literal>JTA TransactionManager</literal> implementations, most, if not all, applications should be using <literal>JTA</literal> transaction management, whether or not they are deployed into a <literal>J2EE</literal> container. Based on that, the <literal>JTA</literal>-based contextual sessions are all you need to use."
msgstr ""
#. Tag: para
-#: architecture.xml:323
#, no-c-format
msgid "However, as of version 3.1, the processing behind <literal>SessionFactory.getCurrentSession()</literal> is now pluggable. To that end, a new extension interface, <literal>org.hibernate.context.CurrentSessionContext</literal>, and a new configuration parameter, <literal>hibernate.current_session_context_class</literal>, have been added to allow pluggability of the scope and context of defining current sessions."
msgstr ""
#. Tag: para
-#: architecture.xml:330
#, no-c-format
msgid "See the Javadocs for the <literal>org.hibernate.context.CurrentSessionContext</literal> interface for a detailed discussion of its contract. It defines a single method, <literal>currentSession()</literal>, by which the implementation is responsible for tracking the current contextual session. Out-of-the-box, Hibernate comes with three implementations of this interface:"
msgstr ""
#. Tag: para
-#: architecture.xml:340
#, no-c-format
msgid "<literal>org.hibernate.context.JTASessionContext</literal>: current sessions are tracked and scoped by a <literal>JTA</literal> transaction. The processing here is exactly the same as in the older JTA-only approach. See the Javadocs for details."
msgstr ""
#. Tag: para
-#: architecture.xml:348
#, no-c-format
msgid "<literal>org.hibernate.context.ThreadLocalSessionContext</literal>:current sessions are tracked by thread of execution. See the Javadocs for details."
msgstr ""
#. Tag: para
-#: architecture.xml:354
#, no-c-format
msgid "<literal>org.hibernate.context.ManagedSessionContext</literal>: current sessions are tracked by thread of execution. However, you are responsible to bind and unbind a <literal>Session</literal> instance with static methods on this class: it does not open, flush, or close a <literal>Session</literal>."
msgstr ""
#. Tag: para
-#: architecture.xml:363
#, no-c-format
-msgid "The first two implementations provide a \"one session - one database transaction\" programming model. This is also also known and used as <emphasis>session-per-request</emphasis>. The beginning and end of a Hibernate session is defined by the duration of a database transaction. If you use programmatic transaction demarcation in plain JSE without JTA, you are advised to use the Hibernate <literal>Transaction</literal> API to hide the underlying transaction system from your code. If you use JTA, you can utilize the JTA interfaces to demarcate transactions. If you execute in an EJB container that supports CMT, transaction boundaries are defined declaratively and you do not need any transaction or session demarcation operations in your code. Refer to <xref linkend=\"transactions\"/> for more information and code examples."
+msgid "The first two implementations provide a \"one session - one database transaction\" programming model. This is also also known and used as <emphasis>session-per-request</emphasis>. The beginning and end of a Hibernate session is defined by the duration of a database transaction. If you use programmatic transaction demarcation in plain JSE without JTA, you are advised to use the Hibernate <literal>Transaction</literal> API to hide the underlying transaction system from your code. If you use JTA, you can utilize the JTA interfaces to demarcate transactions. If you execute in an EJB container that supports CMT, transaction boundaries are defined declaratively and you do not need any transaction or session demarcation operations in your code. Refer to <xref linkend=\"transactions\" /> for more information and code examples."
msgstr ""
#. Tag: para
-#: architecture.xml:375
#, no-c-format
msgid "The <literal>hibernate.current_session_context_class</literal> configuration parameter defines which <literal>org.hibernate.context.CurrentSessionContext</literal> implementation should be used. For backwards compatibility, if this configuration parameter is not set but a <literal>org.hibernate.transaction.TransactionManagerLookup</literal> is configured, Hibernate will use the <literal>org.hibernate.context.JTASessionContext</literal>. Typically, the value of this parameter would just name the implementation class to use. For the three out-of-the-box implementations, however, there are three corresponding short names: \"jta\", \"thread\", and \"managed\"."
msgstr ""
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/association_mapping.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/association_mapping.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/association_mapping.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,743 +1,198 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-10 21:02+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:17\n"
+"PO-Revision-Date: 2010-01-08T04:07:17\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
-#: association_mapping.xml:30
#, no-c-format
msgid "Association Mappings"
msgstr ""
#. Tag: title
-#: association_mapping.xml:33
#, no-c-format
msgid "Introduction"
msgstr ""
#. Tag: para
-#: association_mapping.xml:35
#, no-c-format
msgid "Association mappings are often the most difficult thing to implement correctly. In this section we examine some canonical cases one by one, starting with unidirectional mappings and then bidirectional cases. We will use <literal>Person</literal> and <literal>Address</literal> in all the examples."
msgstr ""
#. Tag: para
-#: association_mapping.xml:43
#, no-c-format
msgid "Associations will be classified by multiplicity and whether or not they map to an intervening join table."
msgstr ""
#. Tag: para
-#: association_mapping.xml:48
#, no-c-format
msgid "Nullable foreign keys are not considered to be good practice in traditional data modelling, so our examples do not use nullable foreign keys. This is not a requirement of Hibernate, and the mappings will work if you drop the nullability constraints."
msgstr ""
#. Tag: title
-#: association_mapping.xml:58
#, no-c-format
msgid "Unidirectional associations"
msgstr ""
#. Tag: title
-#: association_mapping.xml:61 association_mapping.xml:132
#, no-c-format
msgid "Many-to-one"
msgstr ""
#. Tag: para
-#: association_mapping.xml:63
#, no-c-format
msgid "A <emphasis>unidirectional many-to-one association</emphasis> is the most common kind of unidirectional association."
msgstr ""
-#. Tag: programlisting
-#: association_mapping.xml:68
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Person\">\n"
- " <id name=\"id\" column=\"personId\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <many-to-one name=\"address\" \n"
- " column=\"addressId\"\n"
- " not-null=\"true\"/>\n"
- "</class>\n"
- "\n"
- "<class name=\"Address\">\n"
- " <id name=\"id\" column=\"addressId\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- "</class>]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: association_mapping.xml:69 association_mapping.xml:185
-#, no-c-format
-msgid ""
- "<![CDATA[\n"
- "create table Person ( personId bigint not null primary key, addressId bigint not null )\n"
- "create table Address ( addressId bigint not null primary key )\n"
- " ]]>"
-msgstr ""
-
#. Tag: title
-#: association_mapping.xml:74 association_mapping.xml:145 association_mapping.xml:210
#, no-c-format
msgid "One-to-one"
msgstr ""
#. Tag: para
-#: association_mapping.xml:76
#, no-c-format
msgid "A <emphasis>unidirectional one-to-one association on a foreign key</emphasis> is almost identical. The only difference is the column unique constraint."
msgstr ""
-#. Tag: programlisting
-#: association_mapping.xml:81
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Person\">\n"
- " <id name=\"id\" column=\"personId\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <many-to-one name=\"address\" \n"
- " column=\"addressId\" \n"
- " unique=\"true\"\n"
- " not-null=\"true\"/>\n"
- "</class>\n"
- "\n"
- "<class name=\"Address\">\n"
- " <id name=\"id\" column=\"addressId\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- "</class>]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: association_mapping.xml:82 association_mapping.xml:218
-#, no-c-format
-msgid ""
- "<![CDATA[\n"
- "create table Person ( personId bigint not null primary key, addressId bigint not null unique )\n"
- "create table Address ( addressId bigint not null primary key )\n"
- " ]]>"
-msgstr ""
-
#. Tag: para
-#: association_mapping.xml:84
#, no-c-format
msgid "A <emphasis>unidirectional one-to-one association on a primary key</emphasis> usually uses a special id generator In this example, however, we have reversed the direction of the association:"
msgstr ""
-#. Tag: programlisting
-#: association_mapping.xml:90
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Person\">\n"
- " <id name=\"id\" column=\"personId\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- "</class>\n"
- "\n"
- "<class name=\"Address\">\n"
- " <id name=\"id\" column=\"personId\">\n"
- " <generator class=\"foreign\">\n"
- " <param name=\"property\">person</param>\n"
- " </generator>\n"
- " </id>\n"
- " <one-to-one name=\"person\" constrained=\"true\"/>\n"
- "</class>]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: association_mapping.xml:91 association_mapping.xml:226
-#, no-c-format
-msgid ""
- "<![CDATA[\n"
- "create table Person ( personId bigint not null primary key )\n"
- "create table Address ( personId bigint not null primary key )\n"
- " ]]>"
-msgstr ""
-
#. Tag: title
-#: association_mapping.xml:96 association_mapping.xml:118
#, no-c-format
msgid "One-to-many"
msgstr ""
#. Tag: para
-#: association_mapping.xml:98
#, no-c-format
msgid "A <emphasis>unidirectional one-to-many association on a foreign key</emphasis> is an unusual case, and is not recommended."
msgstr ""
-#. Tag: programlisting
-#: association_mapping.xml:103
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Person\">\n"
- " <id name=\"id\" column=\"personId\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <set name=\"addresses\">\n"
- " <key column=\"personId\" \n"
- " not-null=\"true\"/>\n"
- " <one-to-many class=\"Address\"/>\n"
- " </set>\n"
- "</class>\n"
- "\n"
- "<class name=\"Address\">\n"
- " <id name=\"id\" column=\"addressId\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- "</class>]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: association_mapping.xml:104
-#, no-c-format
-msgid ""
- "<![CDATA[\n"
- "create table Person ( personId bigint not null primary key )\n"
- "create table Address ( addressId bigint not null primary key, personId bigint not null )\n"
- " ]]>"
-msgstr ""
-
#. Tag: para
-#: association_mapping.xml:106
#, no-c-format
msgid "You should instead use a join table for this kind of association."
msgstr ""
#. Tag: title
-#: association_mapping.xml:115
#, no-c-format
msgid "Unidirectional associations with join tables"
msgstr ""
#. Tag: para
-#: association_mapping.xml:120
#, no-c-format
msgid "A <emphasis>unidirectional one-to-many association on a join table</emphasis> is the preferred option. Specifying <literal>unique=\"true\"</literal>, changes the multiplicity from many-to-many to one-to-many."
msgstr ""
-#. Tag: programlisting
-#: association_mapping.xml:126
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Person\">\n"
- " <id name=\"id\" column=\"personId\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <set name=\"addresses\" table=\"PersonAddress\">\n"
- " <key column=\"personId\"/>\n"
- " <many-to-many column=\"addressId\"\n"
- " unique=\"true\"\n"
- " class=\"Address\"/>\n"
- " </set>\n"
- "</class>\n"
- "\n"
- "<class name=\"Address\">\n"
- " <id name=\"id\" column=\"addressId\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- "</class>]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: association_mapping.xml:127
-#, no-c-format
-msgid ""
- "<![CDATA[\n"
- "create table Person ( personId bigint not null primary key )\n"
- "create table PersonAddress ( personId not null, addressId bigint not null primary key )\n"
- "create table Address ( addressId bigint not null primary key )\n"
- " ]]>"
-msgstr ""
-
#. Tag: para
-#: association_mapping.xml:134
#, no-c-format
msgid "A <emphasis>unidirectional many-to-one association on a join table</emphasis> is common when the association is optional. For example:"
msgstr ""
-#. Tag: programlisting
-#: association_mapping.xml:139
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Person\">\n"
- " <id name=\"id\" column=\"personId\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <join table=\"PersonAddress\" \n"
- " optional=\"true\">\n"
- " <key column=\"personId\" unique=\"true\"/>\n"
- " <many-to-one name=\"address\"\n"
- " column=\"addressId\" \n"
- " not-null=\"true\"/>\n"
- " </join>\n"
- "</class>\n"
- "\n"
- "<class name=\"Address\">\n"
- " <id name=\"id\" column=\"addressId\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- "</class>]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: association_mapping.xml:140
-#, no-c-format
-msgid ""
- "<![CDATA[\n"
- "create table Person ( personId bigint not null primary key )\n"
- "create table PersonAddress ( personId bigint not null primary key, addressId bigint not null )\n"
- "create table Address ( addressId bigint not null primary key )\n"
- " ]]>"
-msgstr ""
-
#. Tag: para
-#: association_mapping.xml:147
#, no-c-format
msgid "A <emphasis>unidirectional one-to-one association on a join table</emphasis> is possible, but extremely unusual."
msgstr ""
-#. Tag: programlisting
-#: association_mapping.xml:152
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Person\">\n"
- " <id name=\"id\" column=\"personId\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <join table=\"PersonAddress\" \n"
- " optional=\"true\">\n"
- " <key column=\"personId\" \n"
- " unique=\"true\"/>\n"
- " <many-to-one name=\"address\"\n"
- " column=\"addressId\" \n"
- " not-null=\"true\"\n"
- " unique=\"true\"/>\n"
- " </join>\n"
- "</class>\n"
- "\n"
- "<class name=\"Address\">\n"
- " <id name=\"id\" column=\"addressId\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- "</class>]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: association_mapping.xml:153 association_mapping.xml:258
-#, no-c-format
-msgid ""
- "<![CDATA[\n"
- "create table Person ( personId bigint not null primary key )\n"
- "create table PersonAddress ( personId bigint not null primary key, addressId bigint not null unique )\n"
- "create table Address ( addressId bigint not null primary key )\n"
- " ]]>"
-msgstr ""
-
#. Tag: title
-#: association_mapping.xml:158 association_mapping.xml:263
#, no-c-format
msgid "Many-to-many"
msgstr ""
#. Tag: para
-#: association_mapping.xml:160
#, no-c-format
msgid "Finally, here is an example of a <emphasis>unidirectional many-to-many association</emphasis>."
msgstr ""
-#. Tag: programlisting
-#: association_mapping.xml:164
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Person\">\n"
- " <id name=\"id\" column=\"personId\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <set name=\"addresses\" table=\"PersonAddress\">\n"
- " <key column=\"personId\"/>\n"
- " <many-to-many column=\"addressId\"\n"
- " class=\"Address\"/>\n"
- " </set>\n"
- "</class>\n"
- "\n"
- "<class name=\"Address\">\n"
- " <id name=\"id\" column=\"addressId\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- "</class>]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: association_mapping.xml:165 association_mapping.xml:271
-#, no-c-format
-msgid ""
- "<![CDATA[\n"
- "create table Person ( personId bigint not null primary key )\n"
- "create table PersonAddress ( personId bigint not null, addressId bigint not null, primary key (personId, addressId) )\n"
- "create table Address ( addressId bigint not null primary key )\n"
- " ]]>"
-msgstr ""
-
#. Tag: title
-#: association_mapping.xml:172
#, no-c-format
msgid "Bidirectional associations"
msgstr ""
#. Tag: title
-#: association_mapping.xml:175 association_mapping.xml:236
#, no-c-format
msgid "one-to-many / many-to-one"
msgstr ""
#. Tag: para
-#: association_mapping.xml:177
#, no-c-format
msgid "A <emphasis>bidirectional many-to-one association</emphasis> is the most common kind of association. The following example illustrates the standard parent/child relationship."
msgstr ""
-#. Tag: programlisting
-#: association_mapping.xml:183
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Person\">\n"
- " <id name=\"id\" column=\"personId\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <many-to-one name=\"address\" \n"
- " column=\"addressId\"\n"
- " not-null=\"true\"/>\n"
- "</class>\n"
- "\n"
- "<class name=\"Address\">\n"
- " <id name=\"id\" column=\"addressId\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <set name=\"people\" inverse=\"true\">\n"
- " <key column=\"addressId\"/>\n"
- " <one-to-many class=\"Person\"/>\n"
- " </set>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: association_mapping.xml:187
#, no-c-format
msgid "If you use a <literal>List</literal>, or other indexed collection, set the <literal>key</literal> column of the foreign key to <literal>not null</literal>. Hibernate will manage the association from the collections side to maintain the index of each element, making the other side virtually inverse by setting <literal>update=\"false\"</literal> and <literal>insert=\"false\"</literal>:"
msgstr ""
-#. Tag: programlisting
-#: association_mapping.xml:195
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Person\">\n"
- " <id name=\"id\"/>\n"
- " ...\n"
- " <many-to-one name=\"address\"\n"
- " column=\"addressId\"\n"
- " not-null=\"true\"\n"
- " insert=\"false\"\n"
- " update=\"false\"/>\n"
- "</class>\n"
- "\n"
- "<class name=\"Address\">\n"
- " <id name=\"id\"/>\n"
- " ...\n"
- " <list name=\"people\">\n"
- " <key column=\"addressId\" not-null=\"true\"/>\n"
- " <list-index column=\"peopleIdx\"/>\n"
- " <one-to-many class=\"Person\"/>\n"
- " </list>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: association_mapping.xml:197
#, no-c-format
msgid "If the underlying foreign key column is <literal>NOT NULL</literal>, it is important that you define <literal>not-null=\"true\"</literal> on the <literal><key></literal> element of the collection mapping. Do not only declare <literal>not-null=\"true\"</literal> on a possible nested <literal><column></literal> element, but on the <literal><key></literal> element."
msgstr ""
#. Tag: para
-#: association_mapping.xml:212
#, no-c-format
msgid "A <emphasis>bidirectional one-to-one association on a foreign key</emphasis> is common:"
msgstr ""
-#. Tag: programlisting
-#: association_mapping.xml:217
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Person\">\n"
- " <id name=\"id\" column=\"personId\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <many-to-one name=\"address\" \n"
- " column=\"addressId\" \n"
- " unique=\"true\"\n"
- " not-null=\"true\"/>\n"
- "</class>\n"
- "\n"
- "<class name=\"Address\">\n"
- " <id name=\"id\" column=\"addressId\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <one-to-one name=\"person\" \n"
- " property-ref=\"address\"/>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: association_mapping.xml:220
#, no-c-format
msgid "A <emphasis>bidirectional one-to-one association on a primary key</emphasis> uses the special id generator:"
msgstr ""
-#. Tag: programlisting
-#: association_mapping.xml:225
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Person\">\n"
- " <id name=\"id\" column=\"personId\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <one-to-one name=\"address\"/>\n"
- "</class>\n"
- "\n"
- "<class name=\"Address\">\n"
- " <id name=\"id\" column=\"personId\">\n"
- " <generator class=\"foreign\">\n"
- " <param name=\"property\">person</param>\n"
- " </generator>\n"
- " </id>\n"
- " <one-to-one name=\"person\" \n"
- " constrained=\"true\"/>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: title
-#: association_mapping.xml:233
#, no-c-format
msgid "Bidirectional associations with join tables"
msgstr ""
#. Tag: para
-#: association_mapping.xml:238
#, no-c-format
msgid "The following is an example of a <emphasis>bidirectional one-to-many association on a join table</emphasis>. The <literal>inverse=\"true\"</literal> can go on either end of the association, on the collection, or on the join."
msgstr ""
-#. Tag: programlisting
-#: association_mapping.xml:244
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Person\">\n"
- " <id name=\"id\" column=\"personId\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <set name=\"addresses\" \n"
- " table=\"PersonAddress\">\n"
- " <key column=\"personId\"/>\n"
- " <many-to-many column=\"addressId\"\n"
- " unique=\"true\"\n"
- " class=\"Address\"/>\n"
- " </set>\n"
- "</class>\n"
- "\n"
- "<class name=\"Address\">\n"
- " <id name=\"id\" column=\"addressId\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <join table=\"PersonAddress\" \n"
- " inverse=\"true\" \n"
- " optional=\"true\">\n"
- " <key column=\"addressId\"/>\n"
- " <many-to-one name=\"person\"\n"
- " column=\"personId\"\n"
- " not-null=\"true\"/>\n"
- " </join>\n"
- "</class>]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: association_mapping.xml:245
-#, no-c-format
-msgid ""
- "<![CDATA[\n"
- "create table Person ( personId bigint not null primary key )\n"
- "create table PersonAddress ( personId bigint not null, addressId bigint not null primary key )\n"
- "create table Address ( addressId bigint not null primary key )\n"
- " ]]>"
-msgstr ""
-
#. Tag: title
-#: association_mapping.xml:250
#, no-c-format
msgid "one to one"
msgstr ""
#. Tag: para
-#: association_mapping.xml:252
#, no-c-format
msgid "A <emphasis>bidirectional one-to-one association on a join table</emphasis> is possible, but extremely unusual."
msgstr ""
-#. Tag: programlisting
-#: association_mapping.xml:257
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Person\">\n"
- " <id name=\"id\" column=\"personId\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <join table=\"PersonAddress\" \n"
- " optional=\"true\">\n"
- " <key column=\"personId\" \n"
- " unique=\"true\"/>\n"
- " <many-to-one name=\"address\"\n"
- " column=\"addressId\" \n"
- " not-null=\"true\"\n"
- " unique=\"true\"/>\n"
- " </join>\n"
- "</class>\n"
- "\n"
- "<class name=\"Address\">\n"
- " <id name=\"id\" column=\"addressId\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <join table=\"PersonAddress\" \n"
- " optional=\"true\"\n"
- " inverse=\"true\">\n"
- " <key column=\"addressId\" \n"
- " unique=\"true\"/>\n"
- " <many-to-one name=\"person\"\n"
- " column=\"personId\" \n"
- " not-null=\"true\"\n"
- " unique=\"true\"/>\n"
- " </join>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: association_mapping.xml:265
#, no-c-format
msgid "Here is an example of a <emphasis>bidirectional many-to-many association</emphasis>."
msgstr ""
-#. Tag: programlisting
-#: association_mapping.xml:269
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Person\">\n"
- " <id name=\"id\" column=\"personId\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <set name=\"addresses\" table=\"PersonAddress\">\n"
- " <key column=\"personId\"/>\n"
- " <many-to-many column=\"addressId\"\n"
- " class=\"Address\"/>\n"
- " </set>\n"
- "</class>\n"
- "\n"
- "<class name=\"Address\">\n"
- " <id name=\"id\" column=\"addressId\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <set name=\"people\" inverse=\"true\" table=\"PersonAddress\">\n"
- " <key column=\"addressId\"/>\n"
- " <many-to-many column=\"personId\"\n"
- " class=\"Person\"/>\n"
- " </set>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: title
-#: association_mapping.xml:278
#, no-c-format
msgid "More complex association mappings"
msgstr ""
#. Tag: para
-#: association_mapping.xml:280
#, no-c-format
msgid "More complex association joins are <emphasis>extremely</emphasis> rare. Hibernate handles more complex situations by using SQL fragments embedded in the mapping document. For example, if a table with historical account information data defines <literal>accountNumber</literal>, <literal>effectiveEndDate</literal> and <literal>effectiveStartDate</literal>columns, it would be mapped as follows:"
msgstr ""
-#. Tag: programlisting
-#: association_mapping.xml:289
-#, no-c-format
-msgid ""
- "<![CDATA[<properties name=\"currentAccountKey\">\n"
- " <property name=\"accountNumber\" type=\"string\" not-null=\"true\"/>\n"
- " <property name=\"currentAccount\" type=\"boolean\">\n"
- " <formula>case when effectiveEndDate is null then 1 else 0 end</formula>\n"
- " </property>\n"
- "</properties>\n"
- "<property name=\"effectiveEndDate\" type=\"date\"/>\n"
- "<property name=\"effectiveStateDate\" type=\"date\" not-null=\"true\"/>]]>"
-msgstr ""
-
#. Tag: para
-#: association_mapping.xml:291
#, no-c-format
msgid "You can then map an association to the <emphasis>current</emphasis> instance, the one with null <literal>effectiveEndDate</literal>, by using:"
msgstr ""
-#. Tag: programlisting
-#: association_mapping.xml:296
-#, no-c-format
-msgid ""
- "<![CDATA[<many-to-one name=\"currentAccountInfo\" \n"
- " property-ref=\"currentAccountKey\"\n"
- " class=\"AccountInfo\">\n"
- " <column name=\"accountNumber\"/>\n"
- " <formula>'1'</formula>\n"
- "</many-to-one>]]>"
-msgstr ""
-
#. Tag: para
-#: association_mapping.xml:298
#, no-c-format
msgid "In a more complex example, imagine that the association between <literal>Employee</literal> and <literal>Organization</literal> is maintained in an <literal>Employment</literal> table full of historical employment data. An association to the employee's <emphasis>most recent</emphasis> employer, the one with the most recent <literal>startDate</literal>, could be mapped in the following way:"
msgstr ""
-#. Tag: programlisting
-#: association_mapping.xml:306
-#, no-c-format
-msgid ""
- "<![CDATA[<join>\n"
- " <key column=\"employeeId\"/>\n"
- " <subselect>\n"
- " select employeeId, orgId \n"
- " from Employments \n"
- " group by orgId \n"
- " having startDate = max(startDate)\n"
- " </subselect>\n"
- " <many-to-one name=\"mostRecentEmployer\" \n"
- " class=\"Organization\" \n"
- " column=\"orgId\"/>\n"
- "</join>]]>"
-msgstr ""
-
#. Tag: para
-#: association_mapping.xml:308
#, no-c-format
msgid "This functionality allows a degree of creativity and flexibility, but it is more practical to handle these kinds of cases using HQL or a criteria query."
msgstr ""
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/basic_mapping.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/basic_mapping.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/basic_mapping.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,3360 +1,1924 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-10 21:02+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:18\n"
+"PO-Revision-Date: 2010-01-08T04:07:18\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
-#: basic_mapping.xml:29
#, no-c-format
msgid "Basic O/R Mapping"
msgstr ""
#. Tag: title
-#: basic_mapping.xml:32
#, no-c-format
msgid "Mapping declaration"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:34
#, no-c-format
msgid "Object/relational mappings are usually defined in an XML document. The mapping document is designed to be readable and hand-editable. The mapping language is Java-centric, meaning that mappings are constructed around persistent class declarations and not table declarations."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:41
#, no-c-format
msgid "Please note that even though many Hibernate users choose to write the XML by hand, a number of tools exist to generate the mapping document. These include XDoclet, Middlegen and AndroMDA."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:47
#, no-c-format
msgid "Here is an example mapping:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:51
-#, no-c-format
-msgid ""
- "<![CDATA[<?xml version=\"1.0\"?>\n"
- "<!DOCTYPE hibernate-mapping PUBLIC\n"
- " \"-//Hibernate/Hibernate Mapping DTD 3.0//EN\"\n"
- " \"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd\">\n"
- "\n"
- "<hibernate-mapping package=\"eg\">\n"
- "\n"
- " <class name=\"Cat\"\n"
- " table=\"cats\"\n"
- " discriminator-value=\"C\">\n"
- "\n"
- " <id name=\"id\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- "\n"
- " <discriminator column=\"subclass\"\n"
- " type=\"character\"/>\n"
- "\n"
- " <property name=\"weight\"/>\n"
- "\n"
- " <property name=\"birthdate\"\n"
- " type=\"date\"\n"
- " not-null=\"true\"\n"
- " update=\"false\"/>\n"
- "\n"
- " <property name=\"color\"\n"
- " type=\"eg.types.ColorUserType\"\n"
- " not-null=\"true\"\n"
- " update=\"false\"/>\n"
- "\n"
- " <property name=\"sex\"\n"
- " not-null=\"true\"\n"
- " update=\"false\"/>\n"
- "\n"
- " <property name=\"litterId\"\n"
- " column=\"litterId\"\n"
- " update=\"false\"/>\n"
- "\n"
- " <many-to-one name=\"mother\"\n"
- " column=\"mother_id\"\n"
- " update=\"false\"/>\n"
- "\n"
- " <set name=\"kittens\"\n"
- " inverse=\"true\"\n"
- " order-by=\"litter_id\">\n"
- " <key column=\"mother_id\"/>\n"
- " <one-to-many class=\"Cat\"/>\n"
- " </set>\n"
- "\n"
- " <subclass name=\"DomesticCat\"\n"
- " discriminator-value=\"D\">\n"
- "\n"
- " <property name=\"name\"\n"
- " type=\"string\"/>\n"
- "\n"
- " </subclass>\n"
- "\n"
- " </class>\n"
- "\n"
- " <class name=\"Dog\">\n"
- " <!-- mapping for Dog could go here -->\n"
- " </class>\n"
- "\n"
- "</hibernate-mapping>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:53
#, no-c-format
msgid "We will now discuss the content of the mapping document. We will only describe, however, the document elements and attributes that are used by Hibernate at runtime. The mapping document also contains some extra optional attributes and elements that affect the database schemas exported by the schema export tool (for example, the <literal> not-null</literal> attribute)."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:64
#, no-c-format
msgid "Doctype"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:66
#, no-c-format
msgid "All XML mappings should declare the doctype shown. The actual DTD can be found at the URL above, in the directory <literal>hibernate-x.x.x/src/org/hibernate </literal>, or in <literal>hibernate3.jar</literal>. Hibernate will always look for the DTD in its classpath first. If you experience lookups of the DTD using an Internet connection, check the DTD declaration against the contents of your classpath."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:76
#, no-c-format
msgid "EntityResolver"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:77
#, no-c-format
msgid "Hibernate will first attempt to resolve DTDs in its classpath. It does this is by registering a custom <literal>org.xml.sax.EntityResolver</literal> implementation with the SAXReader it uses to read in the xml files. This custom <literal>EntityResolver</literal> recognizes two different systemId namespaces:"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:85
#, no-c-format
msgid "a <literal>hibernate namespace</literal> is recognized whenever the resolver encounters a systemId starting with <literal>http://hibernate.sourceforge.net/</literal>. The resolver attempts to resolve these entities via the classloader which loaded the Hibernate classes."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:94
#, no-c-format
msgid "a <literal>user namespace</literal> is recognized whenever the resolver encounters a systemId using a <literal>classpath://</literal> URL protocol. The resolver will attempt to resolve these entities via (1) the current thread context classloader and (2) the classloader which loaded the Hibernate classes."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:103
#, no-c-format
msgid "The following is an example of utilizing user namespacing:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:106
-#, no-c-format
-msgid ""
- "<![CDATA[<?xml version=\"1.0\"?>\n"
- "<!DOCTYPE hibernate-mapping PUBLIC\n"
- " \"-//Hibernate/Hibernate Mapping DTD 3.0//EN\"\n"
- " \"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd\" [\n"
- " <!ENTITY types SYSTEM \"classpath://your/domain/types.xml\">\n"
- "]>\n"
- "\n"
- "<hibernate-mapping package=\"your.domain\">\n"
- " <class name=\"MyEntity\">\n"
- " <id name=\"id\" type=\"my-custom-id-type\">\n"
- " ...\n"
- " </id>\n"
- " <class>\n"
- " &types;\n"
- "</hibernate-mapping>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:107
#, no-c-format
-msgid "Where <literal>types.xml</literal> is a resource in the <literal>your.domain</literal> package and contains a custom <link linkend=\"mapping-types-custom\">typedef</link>."
+msgid "Where <literal>types.xml</literal> is a resource in the <literal>your.domain</literal> package and contains a custom typedef (see <xref linkend=\"mapping-types-custom\" />)."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:115
#, no-c-format
msgid "Hibernate-mapping"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:117
#, no-c-format
msgid "This element has several optional attributes. The <literal>schema</literal> and <literal>catalog</literal> attributes specify that tables referred to in this mapping belong to the named schema and/or catalog. If they are specified, tablenames will be qualified by the given schema and catalog names. If they are missing, tablenames will be unqualified. The <literal>default-cascade</literal> attribute specifies what cascade style should be assumed for properties and collections that do not specify a <literal>cascade</literal> attribute. By default, the <literal>auto-import</literal> attribute allows you to use unqualified class names in the query language."
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:138
-#, no-c-format
-msgid ""
- "<![CDATA[<hibernate-mapping\n"
- " schema=\"schemaName\"\n"
- " catalog=\"catalogName\"\n"
- " default-cascade=\"cascade_style\"\n"
- " default-access=\"field|property|ClassName\"\n"
- " default-lazy=\"true|false\"\n"
- " auto-import=\"true|false\"\n"
- " package=\"package.name\"\n"
- " />]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:141
#, no-c-format
msgid "<literal>schema</literal> (optional): the name of a database schema."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:146
#, no-c-format
msgid "<literal>catalog</literal> (optional): the name of a database catalog."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:151
#, no-c-format
msgid "<literal>default-cascade</literal> (optional - defaults to <literal>none</literal>): a default cascade style."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:157
#, no-c-format
msgid "<literal>default-access</literal> (optional - defaults to <literal>property</literal>): the strategy Hibernate should use for accessing all properties. It can be a custom implementation of <literal>PropertyAccessor</literal>."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:164
#, no-c-format
msgid "<literal>default-lazy</literal> (optional - defaults to <literal>true</literal>): the default value for unspecified <literal>lazy</literal> attributes of class and collection mappings."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:171
#, no-c-format
msgid "<literal>auto-import</literal> (optional - defaults to <literal>true</literal>): specifies whether we can use unqualified class names of classes in this mapping in the query language."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:178
#, no-c-format
msgid "<literal>package</literal> (optional): specifies a package prefix to use for unqualified class names in the mapping document."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:186
#, no-c-format
msgid "If you have two persistent classes with the same unqualified name, you should set <literal>auto-import=\"false\"</literal>. An exception will result if you attempt to assign two classes to the same \"imported\" name."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:192
#, no-c-format
msgid "The <literal>hibernate-mapping</literal> element allows you to nest several persistent <literal><class></literal> mappings, as shown above. It is, however, good practice (and expected by some tools) to map only a single persistent class, or a single class hierarchy, in one mapping file and name it after the persistent superclass. For example, <literal>Cat.hbm.xml</literal>, <literal>Dog.hbm.xml</literal>, or if using inheritance, <literal>Animal.hbm.xml</literal>."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:205
#, no-c-format
msgid "Class"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:207
#, no-c-format
msgid "You can declare a persistent class using the <literal>class</literal> element. For example:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:235
-#, no-c-format
-msgid ""
- "<![CDATA[<class\n"
- " name=\"ClassName\"\n"
- " table=\"tableName\"\n"
- " discriminator-value=\"discriminator_value\"\n"
- " mutable=\"true|false\"\n"
- " schema=\"owner\"\n"
- " catalog=\"catalog\"\n"
- " proxy=\"ProxyInterface\"\n"
- " dynamic-update=\"true|false\"\n"
- " dynamic-insert=\"true|false\"\n"
- " select-before-update=\"true|false\"\n"
- " polymorphism=\"implicit|explicit\"\n"
- " where=\"arbitrary sql where condition\"\n"
- " persister=\"PersisterClass\"\n"
- " batch-size=\"N\"\n"
- " optimistic-lock=\"none|version|dirty|all\"\n"
- " lazy=\"true|false\"\n"
- " entity-name=\"EntityName\"\n"
- " check=\"arbitrary sql check condition\"\n"
- " rowid=\"rowid\"\n"
- " subselect=\"SQL expression\"\n"
- " abstract=\"true|false\"\n"
- " node=\"element-name\"\n"
- "/>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:238
#, no-c-format
msgid "<literal>name</literal> (optional): the fully qualified Java class name of the persistent class or interface. If this attribute is missing, it is assumed that the mapping is for a non-POJO entity."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:245
#, no-c-format
msgid "<literal>table</literal> (optional - defaults to the unqualified class name): the name of its database table."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:251
#, no-c-format
msgid "<literal>discriminator-value</literal> (optional - defaults to the class name): a value that distinguishes individual subclasses that is used for polymorphic behavior. Acceptable values include <literal>null</literal> and <literal>not null</literal>."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:258
#, no-c-format
msgid "<literal>mutable</literal> (optional - defaults to <literal>true</literal>): specifies that instances of the class are (not) mutable."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:264 basic_mapping.xml:2231
#, no-c-format
msgid "<literal>schema</literal> (optional): overrides the schema name specified by the root <literal><hibernate-mapping></literal> element."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:270 basic_mapping.xml:2237
#, no-c-format
msgid "<literal>catalog</literal> (optional): overrides the catalog name specified by the root <literal><hibernate-mapping></literal> element."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:276
#, no-c-format
msgid "<literal>proxy</literal> (optional): specifies an interface to use for lazy initializing proxies. You can specify the name of the class itself."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:282
#, no-c-format
msgid "<literal>dynamic-update</literal> (optional - defaults to <literal>false</literal>): specifies that <literal>UPDATE</literal> SQL should be generated at runtime and can contain only those columns whose values have changed."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:289
#, no-c-format
msgid "<literal>dynamic-insert</literal> (optional - defaults to <literal>false</literal>): specifies that <literal>INSERT</literal> SQL should be generated at runtime and contain only the columns whose values are not null."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:296
#, no-c-format
msgid "<literal>select-before-update</literal> (optional - defaults to <literal>false</literal>): specifies that Hibernate should <emphasis>never</emphasis> perform an SQL <literal>UPDATE</literal> unless it is certain that an object is actually modified. Only when a transient object has been associated with a new session using <literal>update()</literal>, will Hibernate perform an extra SQL <literal>SELECT</literal> to determine if an <literal>UPDATE</literal> is actually required."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:306
#, no-c-format
msgid "<literal>polymorphism</literal> (optional - defaults to <literal>implicit</literal>): determines whether implicit or explicit query polymorphism is used."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:312
#, no-c-format
msgid "<literal>where</literal> (optional): specifies an arbitrary SQL <literal>WHERE</literal> condition to be used when retrieving objects of this class."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:318
#, no-c-format
msgid "<literal>persister</literal> (optional): specifies a custom <literal>ClassPersister</literal>."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:323
#, no-c-format
msgid "<literal>batch-size</literal> (optional - defaults to <literal>1</literal>): specifies a \"batch size\" for fetching instances of this class by identifier."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:329
#, no-c-format
msgid "<literal>optimistic-lock</literal> (optional - defaults to <literal>version</literal>): determines the optimistic locking strategy."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:335
#, no-c-format
msgid "<literal>lazy</literal> (optional): lazy fetching can be disabled by setting <literal>lazy=\"false\"</literal>."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:341
#, no-c-format
-msgid "<literal>entity-name</literal> (optional - defaults to the class name): Hibernate3 allows a class to be mapped multiple times, potentially to different tables. It also allows entity mappings that are represented by Maps or XML at the Java level. In these cases, you should provide an explicit arbitrary name for the entity. See <xref linkend=\"persistent-classes-dynamicmodels\"/> and <xref linkend=\"xml\"/> for more information."
+msgid "<literal>entity-name</literal> (optional - defaults to the class name): Hibernate3 allows a class to be mapped multiple times, potentially to different tables. It also allows entity mappings that are represented by Maps or XML at the Java level. In these cases, you should provide an explicit arbitrary name for the entity. See <xref linkend=\"persistent-classes-dynamicmodels\" /> and <xref linkend=\"xml\" /> for more information."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:351
#, no-c-format
msgid "<literal>check</literal> (optional): an SQL expression used to generate a multi-row <emphasis>check</emphasis> constraint for automatic schema generation."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:357
#, no-c-format
msgid "<literal>rowid</literal> (optional): Hibernate can use ROWIDs on databases. On Oracle, for example, Hibernate can use the <literal>rowid</literal> extra column for fast updates once this option has been set to <literal>rowid</literal>. A ROWID is an implementation detail and represents the physical location of a stored tuple."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:364
#, no-c-format
msgid "<literal>subselect</literal> (optional): maps an immutable and read-only entity to a database subselect. This is useful if you want to have a view instead of a base table. See below for more information."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:371
#, no-c-format
msgid "<literal>abstract</literal> (optional): is used to mark abstract superclasses in <literal><union-subclass></literal> hierarchies."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:379
#, no-c-format
msgid "It is acceptable for the named persistent class to be an interface. You can declare implementing classes of that interface using the <literal><subclass></literal> element. You can persist any <emphasis>static</emphasis> inner class. Specify the class name using the standard form i.e. <literal>e.g.Foo$Bar</literal>."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:386
#, no-c-format
msgid "Immutable classes, <literal>mutable=\"false\"</literal>, cannot be updated or deleted by the application. This allows Hibernate to make some minor performance optimizations."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:391
#, no-c-format
msgid "The optional <literal>proxy</literal> attribute enables lazy initialization of persistent instances of the class. Hibernate will initially return CGLIB proxies that implement the named interface. The persistent object will load when a method of the proxy is invoked. See \"Initializing collections and proxies\" below."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:398
#, no-c-format
msgid "<emphasis>Implicit</emphasis> polymorphism means that instances of the class will be returned by a query that names any superclass or implemented interface or class, and that instances of any subclass of the class will be returned by a query that names the class itself. <emphasis>Explicit</emphasis> polymorphism means that class instances will be returned only by queries that explicitly name that class. Queries that name the class will return only instances of subclasses mapped inside this <literal><class></literal> declaration as a <literal><subclass></literal> or <literal><joined-subclass></literal>. For most purposes, the default <literal>polymorphism=\"implicit\"</literal> is appropriate. Explicit polymorphism is useful when two different classes are mapped to the same table This allows a \"lightweight\" class that contains a subset of the table columns."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:410
#, no-c-format
msgid "The <literal>persister</literal> attribute lets you customize the persistence strategy used for the class. You can, for example, specify your own subclass of <literal>org.hibernate.persister.EntityPersister</literal>, or you can even provide a completely new implementation of the interface <literal>org.hibernate.persister.ClassPersister</literal> that implements, for example, persistence via stored procedure calls, serialization to flat files or LDAP. See <literal>org.hibernate.test.CustomPersister</literal> for a simple example of \"persistence\" to a <literal>Hashtable</literal>."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:421
#, no-c-format
msgid "The <literal>dynamic-update</literal> and <literal>dynamic-insert</literal> settings are not inherited by subclasses, so they can also be specified on the <literal><subclass></literal> or <literal><joined-subclass></literal> elements. Although these settings can increase performance in some cases, they can actually decrease performance in others."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:429
#, no-c-format
msgid "Use of <literal>select-before-update</literal> will usually decrease performance. It is useful to prevent a database update trigger being called unnecessarily if you reattach a graph of detached instances to a <literal>Session</literal>."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:435
#, no-c-format
msgid "If you enable <literal>dynamic-update</literal>, you will have a choice of optimistic locking strategies:"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:441
#, no-c-format
msgid "<literal>version</literal>: check the version/timestamp columns"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:446
#, no-c-format
msgid "<literal>all</literal>: check all columns"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:451
#, no-c-format
msgid "<literal>dirty</literal>: check the changed columns, allowing some concurrent updates"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:456
#, no-c-format
msgid "<literal>none</literal>: do not use optimistic locking"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:461
#, no-c-format
msgid "It is <emphasis>strongly</emphasis> recommended that you use version/timestamp columns for optimistic locking with Hibernate. This strategy optimizes performance and correctly handles modifications made to detached instances (i.e. when <literal>Session.merge()</literal> is used)."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:468
#, no-c-format
msgid "There is no difference between a view and a base table for a Hibernate mapping. This is transparent at the database level, although some DBMS do not support views properly, especially with updates. Sometimes you want to use a view, but you cannot create one in the database (i.e. with a legacy schema). In this case, you can map an immutable and read-only entity to a given SQL subselect expression:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:476
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Summary\">\n"
- " <subselect>\n"
- " select item.name, max(bid.amount), count(*)\n"
- " from item\n"
- " join bid on bid.item_id = item.id\n"
- " group by item.name\n"
- " </subselect>\n"
- " <synchronize table=\"item\"/>\n"
- " <synchronize table=\"bid\"/>\n"
- " <id name=\"name\"/>\n"
- " ...\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:478
#, no-c-format
msgid "Declare the tables to synchronize this entity with, ensuring that auto-flush happens correctly and that queries against the derived entity do not return stale data. The <literal><subselect></literal> is available both as an attribute and a nested mapping element."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:488
#, no-c-format
-msgid "<title>id</title>"
+msgid "id"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:490
#, no-c-format
msgid "Mapped classes <emphasis>must</emphasis> declare the primary key column of the database table. Most classes will also have a JavaBeans-style property holding the unique identifier of an instance. The <literal><id></literal> element defines the mapping from that property to the primary key column."
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:505
-#, no-c-format
-msgid ""
- "<![CDATA[<id\n"
- " name=\"propertyName\"\n"
- " type=\"typename\"\n"
- " column=\"column_name\"\n"
- " unsaved-value=\"null|any|none|undefined|id_value\"\n"
- " access=\"field|property|ClassName\">\n"
- " node=\"element-name|@attribute-name|element/@attribute|.\"\n"
- "\n"
- " <generator class=\"generatorClass\"/>\n"
- "</id>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:508
#, no-c-format
msgid "<literal>name</literal> (optional): the name of the identifier property."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:513 basic_mapping.xml:1351
#, no-c-format
msgid "<literal>type</literal> (optional): a name that indicates the Hibernate type."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:518
#, no-c-format
msgid "<literal>column</literal> (optional - defaults to the property name): the name of the primary key column."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:524
#, no-c-format
msgid "<literal>unsaved-value</literal> (optional - defaults to a \"sensible\" value): an identifier property value that indicates an instance is newly instantiated (unsaved), distinguishing it from detached instances that were saved or loaded in a previous session."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:532
#, no-c-format
msgid "<literal>access</literal> (optional - defaults to <literal>property</literal>): the strategy Hibernate should use for accessing the property value."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:540
#, no-c-format
msgid "If the <literal>name</literal> attribute is missing, it is assumed that the class has no identifier property."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:545
#, no-c-format
msgid "The <literal>unsaved-value</literal> attribute is almost never needed in Hibernate3."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:549
#, no-c-format
msgid "There is an alternative <literal><composite-id></literal> declaration that allows access to legacy data with composite keys. Its use is strongly discouraged for anything else."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:555
#, no-c-format
msgid "Generator"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:557
#, no-c-format
msgid "The optional <literal><generator></literal> child element names a Java class used to generate unique identifiers for instances of the persistent class. If any parameters are required to configure or initialize the generator instance, they are passed using the <literal><param></literal> element."
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:564
-#, no-c-format
-msgid ""
- "<![CDATA[<id name=\"id\" type=\"long\" column=\"cat_id\">\n"
- " <generator class=\"org.hibernate.id.TableHiLoGenerator\">\n"
- " <param name=\"table\">uid_table</param>\n"
- " <param name=\"column\">next_hi_value_column</param>\n"
- " </generator>\n"
- "</id>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:566
#, no-c-format
msgid "All generators implement the interface <literal>org.hibernate.id.IdentifierGenerator</literal>. This is a very simple interface. Some applications can choose to provide their own specialized implementations, however, Hibernate provides a range of built-in implementations. The shortcut names for the built-in generators are as follows:"
msgstr ""
-#. Tag: literal
-#: basic_mapping.xml:574
+#. Tag: term
#, no-c-format
-msgid "increment"
+msgid "<literal>increment</literal>"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:576
#, no-c-format
msgid "generates identifiers of type <literal>long</literal>, <literal>short</literal> or <literal>int</literal> that are unique only when no other process is inserting data into the same table. <emphasis>Do not use in a cluster.</emphasis>"
msgstr ""
-#. Tag: literal
-#: basic_mapping.xml:585
+#. Tag: term
#, no-c-format
-msgid "identity"
+msgid "<literal>identity</literal>"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:587
#, no-c-format
msgid "supports identity columns in DB2, MySQL, MS SQL Server, Sybase and HypersonicSQL. The returned identifier is of type <literal>long</literal>, <literal>short</literal> or <literal>int</literal>."
msgstr ""
-#. Tag: literal
-#: basic_mapping.xml:595
+#. Tag: term
#, no-c-format
-msgid "sequence"
+msgid "<literal>sequence</literal>"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:597
#, no-c-format
msgid "uses a sequence in DB2, PostgreSQL, Oracle, SAP DB, McKoi or a generator in Interbase. The returned identifier is of type <literal>long</literal>, <literal>short</literal> or <literal>int</literal>"
msgstr ""
-#. Tag: literal
-#: basic_mapping.xml:605
+#. Tag: term
#, no-c-format
-msgid "hilo"
+msgid "<literal>hilo</literal>"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:607
#, no-c-format
msgid "uses a hi/lo algorithm to efficiently generate identifiers of type <literal>long</literal>, <literal>short</literal> or <literal>int</literal>, given a table and column (by default <literal>hibernate_unique_key</literal> and <literal>next_hi</literal> respectively) as a source of hi values. The hi/lo algorithm generates identifiers that are unique only for a particular database."
msgstr ""
-#. Tag: literal
-#: basic_mapping.xml:617
+#. Tag: term
#, no-c-format
-msgid "seqhilo"
+msgid "<literal>seqhilo</literal>"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:619
#, no-c-format
msgid "uses a hi/lo algorithm to efficiently generate identifiers of type <literal>long</literal>, <literal>short</literal> or <literal>int</literal>, given a named database sequence."
msgstr ""
-#. Tag: literal
-#: basic_mapping.xml:627
+#. Tag: term
#, no-c-format
-msgid "uuid"
+msgid "<literal>uuid</literal>"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:629
#, no-c-format
msgid "uses a 128-bit UUID algorithm to generate identifiers of type string that are unique within a network (the IP address is used). The UUID is encoded as a string of 32 hexadecimal digits in length."
msgstr ""
-#. Tag: literal
-#: basic_mapping.xml:637
+#. Tag: term
#, no-c-format
-msgid "guid"
+msgid "<literal>guid</literal>"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:639
#, no-c-format
msgid "uses a database-generated GUID string on MS SQL Server and MySQL."
msgstr ""
-#. Tag: literal
-#: basic_mapping.xml:645
+#. Tag: term
#, no-c-format
-msgid "native"
+msgid "<literal>native</literal>"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:647
#, no-c-format
msgid "selects <literal>identity</literal>, <literal>sequence</literal> or <literal>hilo</literal> depending upon the capabilities of the underlying database."
msgstr ""
-#. Tag: literal
-#: basic_mapping.xml:655
+#. Tag: term
#, no-c-format
-msgid "assigned"
+msgid "<literal>assigned</literal>"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:657
#, no-c-format
msgid "lets the application assign an identifier to the object before <literal>save()</literal> is called. This is the default strategy if no <literal><generator></literal> element is specified."
msgstr ""
-#. Tag: literal
-#: basic_mapping.xml:665
+#. Tag: term
#, no-c-format
-msgid "select"
+msgid "<literal>select</literal>"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:667
#, no-c-format
msgid "retrieves a primary key, assigned by a database trigger, by selecting the row by some unique key and retrieving the primary key value."
msgstr ""
-#. Tag: literal
-#: basic_mapping.xml:674
+#. Tag: term
#, no-c-format
-msgid "foreign"
+msgid "<literal>foreign</literal>"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:676
#, no-c-format
msgid "uses the identifier of another associated object. It is usually used in conjunction with a <literal><one-to-one></literal> primary key association."
msgstr ""
-#. Tag: literal
-#: basic_mapping.xml:683
+#. Tag: term
#, no-c-format
-msgid "sequence-identity"
+msgid "<literal>sequence-identity</literal>"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:685
#, no-c-format
msgid "a specialized sequence generation strategy that utilizes a database sequence for the actual value generation, but combines this with JDBC3 getGeneratedKeys to return the generated identifier value as part of the insert statement execution. This strategy is only supported on Oracle 10g drivers targeted for JDK 1.4. Comments on these insert statements are disabled due to a bug in the Oracle drivers."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:702
#, no-c-format
msgid "Hi/lo algorithm"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:703
#, no-c-format
msgid "The <literal>hilo</literal> and <literal>seqhilo</literal> generators provide two alternate implementations of the hi/lo algorithm. The first implementation requires a \"special\" database table to hold the next available \"hi\" value. Where supported, the second uses an Oracle-style sequence."
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:710
-#, no-c-format
-msgid ""
- "<![CDATA[<id name=\"id\" type=\"long\" column=\"cat_id\">\n"
- " <generator class=\"hilo\">\n"
- " <param name=\"table\">hi_value</param>\n"
- " <param name=\"column\">next_value</param>\n"
- " <param name=\"max_lo\">100</param>\n"
- " </generator>\n"
- "</id>]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: basic_mapping.xml:712
-#, no-c-format
-msgid ""
- "<![CDATA[<id name=\"id\" type=\"long\" column=\"cat_id\">\n"
- " <generator class=\"seqhilo\">\n"
- " <param name=\"sequence\">hi_value</param>\n"
- " <param name=\"max_lo\">100</param>\n"
- " </generator>\n"
- "</id>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:714
#, no-c-format
msgid "Unfortunately, you cannot use <literal>hilo</literal> when supplying your own <literal>Connection</literal> to Hibernate. When Hibernate uses an application server datasource to obtain connections enlisted with JTA, you must configure the <literal>hibernate.transaction.manager_lookup_class</literal>."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:723
#, no-c-format
msgid "UUID algorithm"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:724
#, no-c-format
msgid "The UUID contains: IP address, startup time of the JVM that is accurate to a quarter second, system time and a counter value that is unique within the JVM. It is not possible to obtain a MAC address or memory address from Java code, so this is the best option without using JNI."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:733
#, no-c-format
msgid "Identity columns and sequences"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:734
#, no-c-format
msgid "For databases that support identity columns (DB2, MySQL, Sybase, MS SQL), you can use <literal>identity</literal> key generation. For databases that support sequences (DB2, Oracle, PostgreSQL, Interbase, McKoi, SAP DB) you can use <literal>sequence</literal> style key generation. Both of these strategies require two SQL queries to insert a new object. For example:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:742
-#, no-c-format
-msgid ""
- "<![CDATA[<id name=\"id\" type=\"long\" column=\"person_id\">\n"
- " <generator class=\"sequence\">\n"
- " <param name=\"sequence\">person_id_sequence</param>\n"
- " </generator>\n"
- "</id>]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: basic_mapping.xml:744
-#, no-c-format
-msgid ""
- "<![CDATA[<id name=\"id\" type=\"long\" column=\"person_id\" unsaved-value=\"0\">\n"
- " <generator class=\"identity\"/>\n"
- "</id>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:746
#, no-c-format
msgid "For cross-platform development, the <literal>native</literal> strategy will, depending on the capabilities of the underlying database, choose from the <literal>identity</literal>, <literal>sequence</literal> and <literal>hilo</literal> strategies."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:754
#, no-c-format
msgid "Assigned identifiers"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:755
#, no-c-format
msgid "If you want the application to assign identifiers, as opposed to having Hibernate generate them, you can use the <literal>assigned</literal> generator. This special generator uses the identifier value already assigned to the object's identifier property. The generator is used when the primary key is a natural key instead of a surrogate key. This is the default behavior if you do not specify a <literal><generator></literal> element."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:764
#, no-c-format
msgid "The <literal>assigned</literal> generator makes Hibernate use <literal>unsaved-value=\"undefined\"</literal>. This forces Hibernate to go to the database to determine if an instance is transient or detached, unless there is a version or timestamp property, or you define <literal>Interceptor.isUnsaved()</literal>."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:774
#, no-c-format
msgid "Primary keys assigned by triggers"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:775
#, no-c-format
msgid "Hibernate does not generate DDL with triggers. It is for legacy schemas only."
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:779
-#, no-c-format
-msgid ""
- "<![CDATA[<id name=\"id\" type=\"long\" column=\"person_id\">\n"
- " <generator class=\"select\">\n"
- " <param name=\"key\">socialSecurityNumber</param>\n"
- " </generator>\n"
- "</id>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:781
#, no-c-format
msgid "In the above example, there is a unique valued property named <literal>socialSecurityNumber</literal>. It is defined by the class, as a natural key and a surrogate key named <literal>person_id</literal>, whose value is generated by a trigger."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:793
#, no-c-format
msgid "Enhanced identifier generators"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:795
#, no-c-format
msgid "Starting with release 3.2.3, there are 2 new generators which represent a re-thinking of 2 different aspects of identifier generation. The first aspect is database portability; the second is optimization Optimization means that you do not have to query the database for every request for a new identifier value. These two new generators are intended to take the place of some of the named generators described above, starting in 3.3.x. However, they are included in the current releases and can be referenced by FQN."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:803
#, no-c-format
msgid "The first of these new generators is <literal>org.hibernate.id.enhanced.SequenceStyleGenerator</literal> which is intended, firstly, as a replacement for the <literal>sequence</literal> generator and, secondly, as a better portability generator than <literal>native</literal>. This is because <literal>native</literal> generally chooses between <literal>identity</literal> and <literal>sequence</literal> which have largely different semantics that can cause subtle issues in applications eyeing portability. <literal>org.hibernate.id.enhanced.SequenceStyleGenerator</literal>, however, achieves portability in a different manner. It chooses between a table or a sequence in the database to store its incrementing values, depending on the capabilities of the dialect being used. The difference between this and <literal>native</literal> is that table-based and sequence-based storage have the same exact semantic. In fact, sequences are exactly what Hibernate tries to emulate with!
its table-based generators. This generator has a number of configuration parameters:"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:817
#, no-c-format
msgid "<literal>sequence_name</literal> (optional, defaults to <literal>hibernate_sequence</literal>): the name of the sequence or table to be used."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:823
#, no-c-format
msgid "<literal>initial_value</literal> (optional, defaults to <literal>1</literal>): the initial value to be retrieved from the sequence/table. In sequence creation terms, this is analogous to the clause typically named \"STARTS WITH\"."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:830
#, no-c-format
msgid "<literal>increment_size</literal> (optional - defaults to <literal>1</literal>): the value by which subsequent calls to the sequence/table should differ. In sequence creation terms, this is analogous to the clause typically named \"INCREMENT BY\"."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:837
#, no-c-format
msgid "<literal>force_table_use</literal> (optional - defaults to <literal>false</literal>): should we force the use of a table as the backing structure even though the dialect might support sequence?"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:844
#, no-c-format
msgid "<literal>value_column</literal> (optional - defaults to <literal>next_val</literal>): only relevant for table structures, it is the name of the column on the table which is used to hold the value."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:851
#, no-c-format
-msgid "<literal>optimizer</literal> (optional - defaults to <literal>none</literal>): See"
+msgid "<literal>optimizer</literal> (optional - defaults to <literal>none</literal>): See <xref linkend=\"mapping-declaration-id-enhanced-optimizers\" />"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:858
#, no-c-format
msgid "The second of these new generators is <literal>org.hibernate.id.enhanced.TableGenerator</literal>, which is intended, firstly, as a replacement for the <literal>table</literal> generator, even though it actually functions much more like <literal>org.hibernate.id.MultipleHiLoPerTableGenerator</literal>, and secondly, as a re-implementation of <literal>org.hibernate.id.MultipleHiLoPerTableGenerator</literal> that utilizes the notion of pluggable optimizers. Essentially this generator defines a table capable of holding a number of different increment values simultaneously by using multiple distinctly keyed rows. This generator has a number of configuration parameters:"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:868
#, no-c-format
msgid "<literal>table_name</literal> (optional - defaults to <literal>hibernate_sequences</literal>): the name of the table to be used."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:874
#, no-c-format
msgid "<literal>value_column_name</literal> (optional - defaults to <literal>next_val</literal>): the name of the column on the table that is used to hold the value."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:880
#, no-c-format
msgid "<literal>segment_column_name</literal> (optional - defaults to <literal>sequence_name</literal>): the name of the column on the table that is used to hold the \"segment key\". This is the value which identifies which increment value to use."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:887
#, no-c-format
msgid "<literal>segment_value</literal> (optional - defaults to <literal>default</literal>): The \"segment key\" value for the segment from which we want to pull increment values for this generator."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:894
#, no-c-format
msgid "<literal>segment_value_length</literal> (optional - defaults to <literal>255</literal>): Used for schema generation; the column size to create this segment key column."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:900
#, no-c-format
msgid "<literal>initial_value</literal> (optional - defaults to <literal>1</literal>): The initial value to be retrieved from the table."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:906
#, no-c-format
msgid "<literal>increment_size</literal> (optional - defaults to <literal>1</literal>): The value by which subsequent calls to the table should differ."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:912
#, no-c-format
-msgid "<literal>optimizer</literal> (optional - defaults to <literal></literal>): See"
+msgid "<literal>optimizer</literal> (optional - defaults to <literal></literal>): See <xref linkend=\"mapping-declaration-id-enhanced-optimizers\" />"
msgstr ""
#. Tag: title
-#: basic_mapping.xml:922
#, no-c-format
msgid "Identifier generator optimization"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:923
#, no-c-format
-msgid "For identifier generators that store values in the database, it is inefficient for them to hit the database on each and every call to generate a new identifier value. Instead, you can group a bunch of them in memory and only hit the database when you have exhausted your in-memory value group. This is the role of the pluggable optimizers. Currently only the two enhanced generators (<xref linkend=\"mapping-declaration-id-enhanced\"/> support this operation."
+msgid "For identifier generators that store values in the database, it is inefficient for them to hit the database on each and every call to generate a new identifier value. Instead, you can group a bunch of them in memory and only hit the database when you have exhausted your in-memory value group. This is the role of the pluggable optimizers. Currently only the two enhanced generators (<xref linkend=\"mapping-declaration-id-enhanced\" /> support this operation."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:931
#, no-c-format
msgid "<literal>none</literal> (generally this is the default if no optimizer was specified): this will not perform any optimizations and hit the database for each and every request."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:937
#, no-c-format
msgid "<literal>hilo</literal>: applies a hi/lo algorithm around the database retrieved values. The values from the database for this optimizer are expected to be sequential. The values retrieved from the database structure for this optimizer indicates the \"group number\". The <literal>increment_size</literal> is multiplied by that value in memory to define a group \"hi value\"."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:946
#, no-c-format
msgid "<literal>pooled</literal>: as with the case of <literal>hilo</literal>, this optimizer attempts to minimize the number of hits to the database. Here, however, we simply store the starting value for the \"next group\" into the database structure rather than a sequential value in combination with an in-memory grouping algorithm. Here, <literal>increment_size</literal> refers to the values coming from the database."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:959
#, no-c-format
msgid "composite-id"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:961
-#, no-c-format
-msgid ""
- "<![CDATA[<composite-id\n"
- " name=\"propertyName\"\n"
- " class=\"ClassName\"\n"
- " mapped=\"true|false\"\n"
- " access=\"field|property|ClassName\">\n"
- " node=\"element-name|.\"\n"
- "\n"
- " <key-property name=\"propertyName\" type=\"typename\" column=\"column_name\"/>\n"
- " <key-many-to-one name=\"propertyName class=\"ClassName\" column=\"column_name\"/>\n"
- " ......\n"
- "</composite-id>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:963
#, no-c-format
msgid "A table with a composite key can be mapped with multiple properties of the class as identifier properties. The <literal><composite-id></literal> element accepts <literal><key-property></literal> property mappings and <literal><key-many-to-one></literal> mappings as child elements."
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:970
-#, no-c-format
-msgid ""
- "<![CDATA[<composite-id>\n"
- " <key-property name=\"medicareNumber\"/>\n"
- " <key-property name=\"dependent\"/>\n"
- "</composite-id>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:972
#, no-c-format
msgid "The persistent class <emphasis>must</emphasis> override <literal>equals()</literal> and <literal>hashCode()</literal> to implement composite identifier equality. It must also implement <literal>Serializable</literal>."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:978
#, no-c-format
msgid "Unfortunately, this approach means that a persistent object is its own identifier. There is no convenient \"handle\" other than the object itself. You must instantiate an instance of the persistent class itself and populate its identifier properties before you can <literal>load()</literal> the persistent state associated with a composite key. We call this approach an <emphasis>embedded</emphasis> composite identifier, and discourage it for serious applications."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:987
#, no-c-format
msgid "A second approach is what we call a <emphasis>mapped</emphasis> composite identifier, where the identifier properties named inside the <literal><composite-id></literal> element are duplicated on both the persistent class and a separate identifier class."
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:993
-#, no-c-format
-msgid ""
- "<![CDATA[<composite-id class=\"MedicareId\" mapped=\"true\">\n"
- " <key-property name=\"medicareNumber\"/>\n"
- " <key-property name=\"dependent\"/>\n"
- "</composite-id>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:995
#, no-c-format
msgid "In this example, both the composite identifier class, <literal>MedicareId</literal>, and the entity class itself have properties named <literal>medicareNumber</literal> and <literal>dependent</literal>. The identifier class must override <literal>equals()</literal> and <literal>hashCode()</literal> and implement <literal>Serializable</literal>. The main disadvantage of this approach is code duplication."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1004
#, no-c-format
msgid "The following attributes are used to specify a mapped composite identifier:"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1010
#, no-c-format
msgid "<literal>mapped</literal> (optional - defaults to <literal>false</literal>): indicates that a mapped composite identifier is used, and that the contained property mappings refer to both the entity class and the composite identifier class."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1018
#, no-c-format
msgid "<literal>class</literal> (optional - but required for a mapped composite identifier): the class used as a composite identifier."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1025
#, no-c-format
-msgid "We will describe a third, even more convenient approach, where the composite identifier is implemented as a component class in <xref linkend=\"components-compositeid\"/>. The attributes described below apply only to this alternative approach:"
+msgid "We will describe a third, even more convenient approach, where the composite identifier is implemented as a component class in <xref linkend=\"components-compositeid\" />. The attributes described below apply only to this alternative approach:"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1033
#, no-c-format
msgid "<literal>name</literal> (optional - required for this approach): a property of component type that holds the composite identifier. Please see chapter 9 for more information."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1039 basic_mapping.xml:1260 basic_mapping.xml:1372 basic_mapping.xml:1561 basic_mapping.xml:1735 basic_mapping.xml:1905 basic_mapping.xml:2484
#, no-c-format
msgid "<literal>access</literal> (optional - defaults to <literal>property</literal>): the strategy Hibernate uses for accessing the property value."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1045
#, no-c-format
msgid "<literal>class</literal> (optional - defaults to the property type determined by reflection): the component class used as a composite identifier. Please see the next section for more information."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1052
#, no-c-format
msgid "The third approach, an <emphasis>identifier component</emphasis>, is recommended for almost all applications."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:1060
#, no-c-format
msgid "Discriminator"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1062
#, no-c-format
msgid "The <literal><discriminator></literal> element is required for polymorphic persistence using the table-per-class-hierarchy mapping strategy. It declares a discriminator column of the table. The discriminator column contains marker values that tell the persistence layer what subclass to instantiate for a particular row. A restricted set of types can be used: <literal>string</literal>, <literal>character</literal>, <literal>integer</literal>, <literal>byte</literal>, <literal>short</literal>, <literal>boolean</literal>, <literal>yes_no</literal>, <literal>true_false</literal>."
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:1080
-#, no-c-format
-msgid ""
- "<![CDATA[<discriminator\n"
- " column=\"discriminator_column\"\n"
- " type=\"discriminator_type\"\n"
- " force=\"true|false\"\n"
- " insert=\"true|false\"\n"
- " formula=\"arbitrary sql expression\"\n"
- "/>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:1083
#, no-c-format
msgid "<literal>column</literal> (optional - defaults to <literal>class</literal>): the name of the discriminator column."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1089
#, no-c-format
msgid "<literal>type</literal> (optional - defaults to <literal>string</literal>): a name that indicates the Hibernate type"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1095
#, no-c-format
msgid "<literal>force</literal> (optional - defaults to <literal>false</literal>): \"forces\" Hibernate to specify the allowed discriminator values, even when retrieving all instances of the root class."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1102
#, no-c-format
msgid "<literal>insert</literal> (optional - defaults to <literal>true</literal>): set this to <literal>false</literal> if your discriminator column is also part of a mapped composite identifier. It tells Hibernate not to include the column in SQL <literal>INSERTs</literal>."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1110
#, no-c-format
msgid "<literal>formula</literal> (optional): an arbitrary SQL expression that is executed when a type has to be evaluated. It allows content-based discrimination."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1118
#, no-c-format
msgid "Actual values of the discriminator column are specified by the <literal>discriminator-value</literal> attribute of the <literal><class></literal> and <literal><subclass></literal> elements."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1124
#, no-c-format
msgid "The <literal>force</literal> attribute is only useful if the table contains rows with \"extra\" discriminator values that are not mapped to a persistent class. This will not usually be the case."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1130
#, no-c-format
msgid "The <literal>formula</literal> attribute allows you to declare an arbitrary SQL expression that will be used to evaluate the type of a row. For example:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:1135
-#, no-c-format
-msgid ""
- "<![CDATA[<discriminator\n"
- " formula=\"case when CLASS_TYPE in ('a', 'b', 'c') then 0 else 1 end\"\n"
- " type=\"integer\"/>]]>"
-msgstr ""
-
#. Tag: title
-#: basic_mapping.xml:1140
#, no-c-format
msgid "Version (optional)"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1142
#, no-c-format
msgid "The <literal><version></literal> element is optional and indicates that the table contains versioned data. This is particularly useful if you plan to use <emphasis>long transactions</emphasis>. See below for more information:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:1158
-#, no-c-format
-msgid ""
- "<![CDATA[<version\n"
- " column=\"version_column\"\n"
- " name=\"propertyName\"\n"
- " type=\"typename\"\n"
- " access=\"field|property|ClassName\"\n"
- " unsaved-value=\"null|negative|undefined\"\n"
- " generated=\"never|always\"\n"
- " insert=\"true|false\"\n"
- " node=\"element-name|@attribute-name|element/@attribute|.\"\n"
- "/>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:1161
#, no-c-format
msgid "<literal>column</literal> (optional - defaults to the property name): the name of the column holding the version number."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1167
#, no-c-format
msgid "<literal>name</literal>: the name of a property of the persistent class."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1172
#, no-c-format
msgid "<literal>type</literal> (optional - defaults to <literal>integer</literal>): the type of the version number."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1178
#, no-c-format
msgid "<literal>access</literal> (optional - defaults to <literal>property</literal>): the strategy Hibernate uses to access the property value."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1184
#, no-c-format
msgid "<literal>unsaved-value</literal> (optional - defaults to <literal>undefined</literal>): a version property value that indicates that an instance is newly instantiated (unsaved), distinguishing it from detached instances that were saved or loaded in a previous session. <literal>Undefined</literal> specifies that the identifier property value should be used."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1193
#, no-c-format
-msgid "<literal>generated</literal> (optional - defaults to <literal>never</literal>): specifies that this version property value is generated by the database. See the discussion of <link linkend=\"mapping-generated\">generated properties</link> for more information."
+msgid "<literal>generated</literal> (optional - defaults to <literal>never</literal>): specifies that this version property value is generated by the database. See the discussion of generated properties for more information (<xref linkend=\"mapping-generated\" />)."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1200
#, no-c-format
msgid "<literal>insert</literal> (optional - defaults to <literal>true</literal>): specifies whether the version column should be included in SQL insert statements. It can be set to <literal>false</literal> if the database column is defined with a default value of <literal>0</literal>."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1210
#, no-c-format
msgid "Version numbers can be of Hibernate type <literal>long</literal>, <literal>integer</literal>, <literal>short</literal>, <literal>timestamp</literal> or <literal>calendar</literal>."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1215
#, no-c-format
msgid "A version or timestamp property should never be null for a detached instance. Hibernate will detect any instance with a null version or timestamp as transient, irrespective of what other <literal>unsaved-value</literal> strategies are specified. <emphasis>Declaring a nullable version or timestamp property is an easy way to avoid problems with transitive reattachment in Hibernate. It is especially useful for people using assigned identifiers or composite keys</emphasis>."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:1226
#, no-c-format
msgid "Timestamp (optional)"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1228
#, no-c-format
msgid "The optional <literal><timestamp></literal> element indicates that the table contains timestamped data. This provides an alternative to versioning. Timestamps are a less safe implementation of optimistic locking. However, sometimes the application might use the timestamps in other ways."
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:1244
-#, no-c-format
-msgid ""
- "<![CDATA[<timestamp\n"
- " column=\"timestamp_column\"\n"
- " name=\"propertyName\"\n"
- " access=\"field|property|ClassName\"\n"
- " unsaved-value=\"null|undefined\"\n"
- " source=\"vm|db\"\n"
- " generated=\"never|always\"\n"
- " node=\"element-name|@attribute-name|element/@attribute|.\"\n"
- "/>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:1247
#, no-c-format
msgid "<literal>column</literal> (optional - defaults to the property name): the name of a column holding the timestamp."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1253
#, no-c-format
msgid "<literal>name</literal>: the name of a JavaBeans style property of Java type <literal>Date</literal> or <literal>Timestamp</literal> of the persistent class."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1266
#, no-c-format
msgid "<literal>unsaved-value</literal> (optional - defaults to <literal>null</literal>): a version property value that indicates that an instance is newly instantiated (unsaved), distinguishing it from detached instances that were saved or loaded in a previous session. <literal>Undefined</literal> specifies that the identifier property value should be used."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1275
#, no-c-format
msgid "<literal>source</literal> (optional - defaults to <literal>vm</literal>): Where should Hibernate retrieve the timestamp value from? From the database, or from the current JVM? Database-based timestamps incur an overhead because Hibernate must hit the database in order to determine the \"next value\". It is safer to use in clustered environments. Not all <literal>Dialects</literal> are known to support the retrieval of the database's current timestamp. Others may also be unsafe for usage in locking due to lack of precision (Oracle 8, for example)."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1287
#, no-c-format
-msgid "<literal>generated</literal> (optional - defaults to <literal>never</literal>): specifies that this timestamp property value is actually generated by the database. See the discussion of <link linkend=\"mapping-generated\">generated properties</link> for more information."
+msgid "<literal>generated</literal> (optional - defaults to <literal>never</literal>): specifies that this timestamp property value is actually generated by the database. See the discussion of generated properties for more information (<xref linkend=\"mapping-generated\" />)."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:1298 basic_mapping.xml:2890
#, no-c-format
msgid "Note"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1299
#, no-c-format
msgid "<literal><Timestamp></literal> is equivalent to <literal><version type=\"timestamp\"></literal>. And <literal><timestamp source=\"db\"></literal> is equivalent to <literal><version type=\"dbtimestamp\"></literal>"
msgstr ""
#. Tag: title
-#: basic_mapping.xml:1311
#, no-c-format
msgid "Property"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1313
#, no-c-format
msgid "The <literal><property></literal> element declares a persistent JavaBean style property of the class."
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:1335
-#, no-c-format
-msgid ""
- "<![CDATA[<property\n"
- " name=\"propertyName\"\n"
- " column=\"column_name\"\n"
- " type=\"typename\"\n"
- " update=\"true|false\"\n"
- " insert=\"true|false\"\n"
- " formula=\"arbitrary SQL expression\"\n"
- " access=\"field|property|ClassName\"\n"
- " lazy=\"true|false\"\n"
- " unique=\"true|false\"\n"
- " not-null=\"true|false\"\n"
- " optimistic-lock=\"true|false\"\n"
- " generated=\"never|insert|always\"\n"
- " node=\"element-name|@attribute-name|element/@attribute|.\"\n"
- " index=\"index_name\"\n"
- " unique_key=\"unique_key_id\"\n"
- " length=\"L\"\n"
- " precision=\"P\"\n"
- " scale=\"S\"\n"
- "/>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:1338
#, no-c-format
msgid "<literal>name</literal>: the name of the property, with an initial lowercase letter."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1344
#, no-c-format
msgid "<literal>column</literal> (optional - defaults to the property name): the name of the mapped database table column. This can also be specified by nested <literal><column></literal> element(s)."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1356
#, no-c-format
msgid "<literal>update, insert</literal> (optional - defaults to <literal>true</literal>): specifies that the mapped columns should be included in SQL <literal>UPDATE</literal> and/or <literal>INSERT</literal> statements. Setting both to <literal>false</literal> allows a pure \"derived\" property whose value is initialized from some other property that maps to the same column(s), or by a trigger or other application."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1365
#, no-c-format
msgid "<literal>formula</literal> (optional): an SQL expression that defines the value for a <emphasis>computed</emphasis> property. Computed properties do not have a column mapping of their own."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1378
#, no-c-format
msgid "<literal>lazy</literal> (optional - defaults to <literal>false</literal>): specifies that this property should be fetched lazily when the instance variable is first accessed. It requires build-time bytecode instrumentation."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1385
#, no-c-format
msgid "<literal>unique</literal> (optional): enables the DDL generation of a unique constraint for the columns. Also, allow this to be the target of a <literal>property-ref</literal>."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1392
#, no-c-format
msgid "<literal>not-null</literal> (optional): enables the DDL generation of a nullability constraint for the columns."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1398 basic_mapping.xml:1581
#, no-c-format
msgid "<literal>optimistic-lock</literal> (optional - defaults to <literal>true</literal>): specifies that updates to this property do or do not require acquisition of the optimistic lock. In other words, it determines if a version increment should occur when this property is dirty."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1406
#, no-c-format
-msgid "<literal>generated</literal> (optional - defaults to <literal>never</literal>): specifies that this property value is actually generated by the database. See the discussion of <link linkend=\"mapping-generated\">generated properties</link> for more information."
+msgid "<literal>generated</literal> (optional - defaults to <literal>never</literal>): specifies that this property value is actually generated by the database. See the discussion of generated properties for more information (<xref linkend=\"mapping-generated\" />)."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1415
#, no-c-format
msgid "<emphasis>typename</emphasis> could be:"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1421
#, no-c-format
msgid "The name of a Hibernate basic type: <literal>integer, string, character, date, timestamp, float, binary, serializable, object, blob</literal> etc."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1427
#, no-c-format
msgid "The name of a Java class with a default basic type: <literal>int, float, char, java.lang.String, java.util.Date, java.lang.Integer, java.sql.Clob</literal> etc."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1433
#, no-c-format
msgid "The name of a serializable Java class."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1438
#, no-c-format
msgid "The class name of a custom type: <literal>com.illflow.type.MyCustomType</literal> etc."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1444
#, no-c-format
msgid "If you do not specify a type, Hibernate will use reflection upon the named property and guess the correct Hibernate type. Hibernate will attempt to interpret the name of the return class of the property getter using, in order, rules 2, 3, and 4. In certain cases you will need the <literal>type</literal> attribute. For example, to distinguish between <literal>Hibernate.DATE</literal> and <literal>Hibernate.TIMESTAMP</literal>, or to specify a custom type."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1454
#, no-c-format
msgid "The <literal>access</literal> attribute allows you to control how Hibernate accesses the property at runtime. By default, Hibernate will call the property get/set pair. If you specify <literal>access=\"field\"</literal>, Hibernate will bypass the get/set pair and access the field directly using reflection. You can specify your own strategy for property access by naming a class that implements the interface <literal>org.hibernate.property.PropertyAccessor</literal>."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1463
#, no-c-format
msgid "A powerful feature is derived properties. These properties are by definition read-only. The property value is computed at load time. You declare the computation as an SQL expression. This then translates to a <literal>SELECT</literal> clause subquery in the SQL query that loads an instance:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:1470
-#, no-c-format
-msgid ""
- "<![CDATA[\n"
- "<property name=\"totalPrice\"\n"
- " formula=\"( SELECT SUM (li.quantity*p.price) FROM LineItem li, Product p\n"
- " WHERE li.productId = p.productId\n"
- " AND li.customerId = customerId\n"
- " AND li.orderNumber = orderNumber )\"/>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:1472
#, no-c-format
msgid "You can reference the entity table by not declaring an alias on a particular column. This would be <literal>customerId</literal> in the given example. You can also use the nested <literal><formula></literal> mapping element if you do not want to use the attribute."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:1482
#, no-c-format
msgid "Many-to-one"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1484
#, no-c-format
msgid "An ordinary association to another persistent class is declared using a <literal>many-to-one</literal> element. The relational model is a many-to-one association; a foreign key in one table is referencing the primary key column(s) of the target table."
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:1512
-#, no-c-format
-msgid ""
- "<![CDATA[<many-to-one\n"
- " name=\"propertyName\"\n"
- " column=\"column_name\"\n"
- " class=\"ClassName\"\n"
- " cascade=\"cascade_style\"\n"
- " fetch=\"join|select\"\n"
- " update=\"true|false\"\n"
- " insert=\"true|false\"\n"
- " property-ref=\"propertyNameFromAssociatedClass\"\n"
- " access=\"field|property|ClassName\"\n"
- " unique=\"true|false\"\n"
- " not-null=\"true|false\"\n"
- " optimistic-lock=\"true|false\"\n"
- " lazy=\"proxy|no-proxy|false\"\n"
- " not-found=\"ignore|exception\"\n"
- " entity-name=\"EntityName\"\n"
- " formula=\"arbitrary SQL expression\"\n"
- " node=\"element-name|@attribute-name|element/@attribute|.\"\n"
- " embed-xml=\"true|false\"\n"
- " index=\"index_name\"\n"
- " unique_key=\"unique_key_id\"\n"
- " foreign-key=\"foreign_key_name\"\n"
- "/>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:1515 basic_mapping.xml:1696 basic_mapping.xml:1882
#, no-c-format
msgid "<literal>name</literal>: the name of the property."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1520 basic_mapping.xml:2311
#, no-c-format
msgid "<literal>column</literal> (optional): the name of the foreign key column. This can also be specified by nested <literal><column></literal> element(s)."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1527 basic_mapping.xml:1701
#, no-c-format
msgid "<literal>class</literal> (optional - defaults to the property type determined by reflection): the name of the associated class."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1533 basic_mapping.xml:1707
#, no-c-format
msgid "<literal>cascade</literal> (optional): specifies which operations should be cascaded from the parent object to the associated object."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1539 basic_mapping.xml:1722
#, no-c-format
msgid "<literal>fetch</literal> (optional - defaults to <literal>select</literal>): chooses between outer-join fetching or sequential select fetching."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1545
#, no-c-format
msgid "<literal>update, insert</literal> (optional - defaults to <literal>true</literal>): specifies that the mapped columns should be included in SQL <literal>UPDATE</literal> and/or <literal>INSERT</literal> statements. Setting both to <literal>false</literal> allows a pure \"derived\" association whose value is initialized from another property that maps to the same column(s), or by a trigger or other application."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1554
#, no-c-format
msgid "<literal>property-ref</literal> (optional): the name of a property of the associated class that is joined to this foreign key. If not specified, the primary key of the associated class is used."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1567
#, no-c-format
msgid "<literal>unique</literal> (optional): enables the DDL generation of a unique constraint for the foreign-key column. By allowing this to be the target of a <literal>property-ref</literal>, you can make the association multiplicity one-to-one."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1575
#, no-c-format
msgid "<literal>not-null</literal> (optional): enables the DDL generation of a nullability constraint for the foreign key columns."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1589
#, no-c-format
msgid "<literal>lazy</literal> (optional - defaults to <literal>proxy</literal>): by default, single point associations are proxied. <literal>lazy=\"no-proxy\"</literal> specifies that the property should be fetched lazily when the instance variable is first accessed. This requires build-time bytecode instrumentation. <literal>lazy=\"false\"</literal> specifies that the association will always be eagerly fetched."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1599
#, no-c-format
msgid "<literal>not-found</literal> (optional - defaults to <literal>exception</literal>): specifies how foreign keys that reference missing rows will be handled. <literal>ignore</literal> will treat a missing row as a null association."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1606 basic_mapping.xml:1760
#, no-c-format
msgid "<literal>entity-name</literal> (optional): the entity name of the associated class."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1611
#, no-c-format
msgid "<literal>formula</literal> (optional): an SQL expression that defines the value for a <emphasis>computed</emphasis> foreign key."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1619
#, no-c-format
-msgid "Setting a value of the <literal>cascade</literal> attribute to any meaningful value other than <literal>none</literal> will propagate certain operations to the associated object. The meaningful values are divided into three categories. First, basic operations, which include: <literal>persist, merge, delete, save-update, evict, replicate, lock and refresh</literal>; second, special values: <literal>delete-orphan</literal>; and third,<literal>all</literal> comma-separated combinations of operation names: <literal>cascade=\"persist,merge,evict\"</literal> or <literal>cascade=\"all,delete-orphan\"</literal>. See <xref linkend=\"objectstate-transitive\"/> for a full explanation. Note that single valued, many-to-one and one-to-one, associations do not support orphan delete."
+msgid "Setting a value of the <literal>cascade</literal> attribute to any meaningful value other than <literal>none</literal> will propagate certain operations to the associated object. The meaningful values are divided into three categories. First, basic operations, which include: <literal>persist, merge, delete, save-update, evict, replicate, lock and refresh</literal>; second, special values: <literal>delete-orphan</literal>; and third,<literal>all</literal> comma-separated combinations of operation names: <literal>cascade=\"persist,merge,evict\"</literal> or <literal>cascade=\"all,delete-orphan\"</literal>. See <xref linkend=\"objectstate-transitive\" /> for a full explanation. Note that single valued, many-to-one and one-to-one, associations do not support orphan delete."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1632
#, no-c-format
msgid "Here is an example of a typical <literal>many-to-one</literal> declaration:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:1636
-#, no-c-format
-msgid "<![CDATA[<many-to-one name=\"product\" class=\"Product\" column=\"PRODUCT_ID\"/>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:1638
#, no-c-format
msgid "The <literal>property-ref</literal> attribute should only be used for mapping legacy data where a foreign key refers to a unique key of the associated table other than the primary key. This is a complicated and confusing relational model. For example, if the <literal>Product</literal> class had a unique serial number that is not the primary key. The <literal>unique</literal> attribute controls Hibernate's DDL generation with the SchemaExport tool."
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:1647
-#, no-c-format
-msgid "<![CDATA[<property name=\"serialNumber\" unique=\"true\" type=\"string\" column=\"SERIAL_NUMBER\"/>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:1649
#, no-c-format
msgid "Then the mapping for <literal>OrderItem</literal> might use:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:1653
-#, no-c-format
-msgid "<![CDATA[<many-to-one name=\"product\" property-ref=\"serialNumber\" column=\"PRODUCT_SERIAL_NUMBER\"/>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:1655
#, no-c-format
msgid "This is not encouraged, however."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1659
#, no-c-format
msgid "If the referenced unique key comprises multiple properties of the associated entity, you should map the referenced properties inside a named <literal><properties></literal> element."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1664
#, no-c-format
msgid "If the referenced unique key is the property of a component, you can specify a property path:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:1668
-#, no-c-format
-msgid "<![CDATA[<many-to-one name=\"owner\" property-ref=\"identity.ssn\" column=\"OWNER_SSN\"/>]]>"
-msgstr ""
-
#. Tag: title
-#: basic_mapping.xml:1673
#, no-c-format
msgid "One-to-one"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1675
#, no-c-format
msgid "A one-to-one association to another persistent class is declared using a <literal>one-to-one</literal> element."
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:1693
-#, no-c-format
-msgid ""
- "<![CDATA[<one-to-one\n"
- " name=\"propertyName\"\n"
- " class=\"ClassName\"\n"
- " cascade=\"cascade_style\"\n"
- " constrained=\"true|false\"\n"
- " fetch=\"join|select\"\n"
- " property-ref=\"propertyNameFromAssociatedClass\"\n"
- " access=\"field|property|ClassName\"\n"
- " formula=\"any SQL expression\"\n"
- " lazy=\"proxy|no-proxy|false\"\n"
- " entity-name=\"EntityName\"\n"
- " node=\"element-name|@attribute-name|element/@attribute|.\"\n"
- " embed-xml=\"true|false\"\n"
- " foreign-key=\"foreign_key_name\"\n"
- "/>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:1713
#, no-c-format
msgid "<literal>constrained</literal> (optional): specifies that a foreign key constraint on the primary key of the mapped table and references the table of the associated class. This option affects the order in which <literal>save()</literal> and <literal>delete()</literal> are cascaded, and determines whether the association can be proxied. It is also used by the schema export tool."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1728
#, no-c-format
msgid "<literal>property-ref</literal> (optional): the name of a property of the associated class that is joined to the primary key of this class. If not specified, the primary key of the associated class is used."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1741
#, no-c-format
msgid "<literal>formula</literal> (optional): almost all one-to-one associations map to the primary key of the owning entity. If this is not the case, you can specify another column, columns or expression to join on using an SQL formula. See <literal>org.hibernate.test.onetooneformula</literal> for an example."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1749
#, no-c-format
msgid "<literal>lazy</literal> (optional - defaults to <literal>proxy</literal>): by default, single point associations are proxied. <literal>lazy=\"no-proxy\"</literal> specifies that the property should be fetched lazily when the instance variable is first accessed. It requires build-time bytecode instrumentation. <literal>lazy=\"false\"</literal> specifies that the association will always be eagerly fetched. <emphasis>Note that if <literal>constrained=\"false\"</literal>, proxying is impossible and Hibernate will eagerly fetch the association</emphasis>."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1767
#, no-c-format
msgid "There are two varieties of one-to-one associations:"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1771
#, no-c-format
msgid "primary key associations"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1774
#, no-c-format
msgid "unique foreign key associations"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1779
#, no-c-format
msgid "Primary key associations do not need an extra table column. If two rows are related by the association, then the two table rows share the same primary key value. To relate two objects by a primary key association, ensure that they are assigned the same identifier value."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1786
#, no-c-format
msgid "For a primary key association, add the following mappings to <literal>Employee</literal> and <literal>Person</literal> respectively:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:1791
-#, no-c-format
-msgid "<![CDATA[<one-to-one name=\"person\" class=\"Person\"/>]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: basic_mapping.xml:1792
-#, no-c-format
-msgid "<![CDATA[<one-to-one name=\"employee\" class=\"Employee\" constrained=\"true\"/>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:1794
#, no-c-format
msgid "Ensure that the primary keys of the related rows in the PERSON and EMPLOYEE tables are equal. You use a special Hibernate identifier generation strategy called <literal>foreign</literal>:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:1800
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"person\" table=\"PERSON\">\n"
- " <id name=\"id\" column=\"PERSON_ID\">\n"
- " <generator class=\"foreign\">\n"
- " <param name=\"property\">employee</param>\n"
- " </generator>\n"
- " </id>\n"
- " ...\n"
- " <one-to-one name=\"employee\"\n"
- " class=\"Employee\"\n"
- " constrained=\"true\"/>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:1802
#, no-c-format
msgid "A newly saved instance of <literal>Person</literal> is assigned the same primary key value as the <literal>Employee</literal> instance referred with the <literal>employee</literal> property of that <literal>Person</literal>."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1808
#, no-c-format
msgid "Alternatively, a foreign key with a unique constraint, from <literal>Employee</literal> to <literal>Person</literal>, can be expressed as:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:1813
-#, no-c-format
-msgid "<![CDATA[<many-to-one name=\"person\" class=\"Person\" column=\"PERSON_ID\" unique=\"true\"/>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:1815
#, no-c-format
msgid "This association can be made bidirectional by adding the following to the <literal>Person</literal> mapping:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:1820
-#, no-c-format
-msgid "<![CDATA[<one-to-one name=\"employee\" class=\"Employee\" property-ref=\"person\"/>]]>"
-msgstr ""
-
#. Tag: title
-#: basic_mapping.xml:1825
#, no-c-format
msgid "Natural-id"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:1827
-#, no-c-format
-msgid ""
- "<![CDATA[<natural-id mutable=\"true|false\"/>\n"
- " <property ... />\n"
- " <many-to-one ... />\n"
- " ......\n"
- "</natural-id>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:1829
#, no-c-format
msgid "Although we recommend the use of surrogate keys as primary keys, you should try to identify natural keys for all entities. A natural key is a property or combination of properties that is unique and non-null. It is also immutable. Map the properties of the natural key inside the <literal><natural-id></literal> element. Hibernate will generate the necessary unique key and nullability constraints and, as a result, your mapping will be more self-documenting."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1838
#, no-c-format
msgid "It is recommended that you implement <literal>equals()</literal> and <literal>hashCode()</literal> to compare the natural key properties of the entity."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1843
#, no-c-format
msgid "This mapping is not intended for use with entities that have natural primary keys."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1849
#, no-c-format
msgid "<literal>mutable</literal> (optional - defaults to <literal>false</literal>): by default, natural identifier properties are assumed to be immutable (constant)."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:1859
#, no-c-format
msgid "Component and dynamic-component"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1861
#, no-c-format
msgid "The <literal><component></literal> element maps properties of a child object to columns of the table of a parent class. Components can, in turn, declare their own properties, components or collections. See the \"Component\" examples below:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:1879
-#, no-c-format
-msgid ""
- "<![CDATA[<component\n"
- " name=\"propertyName\"\n"
- " class=\"className\"\n"
- " insert=\"true|false\"\n"
- " update=\"true|false\"\n"
- " access=\"field|property|ClassName\"\n"
- " lazy=\"true|false\"\n"
- " optimistic-lock=\"true|false\"\n"
- " unique=\"true|false\"\n"
- " node=\"element-name|.\"\n"
- ">\n"
- "\n"
- " <property ...../>\n"
- " <many-to-one .... />\n"
- " ........\n"
- "</component>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:1887
#, no-c-format
msgid "<literal>class</literal> (optional - defaults to the property type determined by reflection): the name of the component (child) class."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1893 basic_mapping.xml:1982
#, no-c-format
msgid "<literal>insert</literal>: do the mapped columns appear in SQL <literal>INSERTs</literal>?"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1899 basic_mapping.xml:1988
#, no-c-format
msgid "<literal>update</literal>: do the mapped columns appear in SQL <literal>UPDATEs</literal>?"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1911
#, no-c-format
msgid "<literal>lazy</literal> (optional - defaults to <literal>false</literal>): specifies that this component should be fetched lazily when the instance variable is first accessed. It requires build-time bytecode instrumentation."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1918
#, no-c-format
msgid "<literal>optimistic-lock</literal> (optional - defaults to <literal>true</literal>): specifies that updates to this component either do or do not require acquisition of the optimistic lock. It determines if a version increment should occur when this property is dirty."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1926 basic_mapping.xml:2002
#, no-c-format
msgid "<literal>unique</literal> (optional - defaults to <literal>false</literal>): specifies that a unique constraint exists upon all mapped columns of the component."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1935
#, no-c-format
msgid "The child <literal><property></literal> tags map properties of the child class to table columns."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1940
#, no-c-format
msgid "The <literal><component></literal> element allows a <literal><parent></literal> subelement that maps a property of the component class as a reference back to the containing entity."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1946
#, no-c-format
-msgid "The <literal><dynamic-component></literal> element allows a <literal>Map</literal> to be mapped as a component, where the property names refer to keys of the map. See <xref linkend=\"components-dynamic\"/> for more information."
+msgid "The <literal><dynamic-component></literal> element allows a <literal>Map</literal> to be mapped as a component, where the property names refer to keys of the map. See <xref linkend=\"components-dynamic\" /> for more information."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:1955
#, no-c-format
msgid "Properties"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1957
#, no-c-format
msgid "The <literal><properties></literal> element allows the definition of a named, logical grouping of the properties of a class. The most important use of the construct is that it allows a combination of properties to be the target of a <literal>property-ref</literal>. It is also a convenient way to define a multi-column unique constraint. For example:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:1973
-#, no-c-format
-msgid ""
- "<![CDATA[<properties\n"
- " name=\"logicalName\"\n"
- " insert=\"true|false\"\n"
- " update=\"true|false\"\n"
- " optimistic-lock=\"true|false\"\n"
- " unique=\"true|false\"\n"
- ">\n"
- "\n"
- " <property ...../>\n"
- " <many-to-one .... />\n"
- " ........\n"
- "</properties>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:1976
#, no-c-format
msgid "<literal>name</literal>: the logical name of the grouping. It is <emphasis>not</emphasis> an actual property name."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:1994
#, no-c-format
msgid "<literal>optimistic-lock</literal> (optional - defaults to <literal>true</literal>): specifies that updates to these properties either do or do not require acquisition of the optimistic lock. It determines if a version increment should occur when these properties are dirty."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2011
#, no-c-format
msgid "For example, if we have the following <literal><properties></literal> mapping:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:2015
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Person\">\n"
- " <id name=\"personNumber\"/>\n"
- "\n"
- " ...\n"
- " <properties name=\"name\"\n"
- " unique=\"true\" update=\"false\">\n"
- " <property name=\"firstName\"/>\n"
- " <property name=\"initial\"/>\n"
- " <property name=\"lastName\"/>\n"
- " </properties>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:2017
#, no-c-format
msgid "You might have some legacy data association that refers to this unique key of the <literal>Person</literal> table, instead of to the primary key:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:2022
-#, no-c-format
-msgid ""
- "<![CDATA[<many-to-one name=\"person\"\n"
- " class=\"Person\" property-ref=\"name\">\n"
- " <column name=\"firstName\"/>\n"
- " <column name=\"initial\"/>\n"
- " <column name=\"lastName\"/>\n"
- "</many-to-one>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:2024
#, no-c-format
msgid "The use of this outside the context of mapping legacy data is not recommended."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:2032
#, no-c-format
msgid "Subclass"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2034
#, no-c-format
msgid "Polymorphic persistence requires the declaration of each subclass of the root persistent class. For the table-per-class-hierarchy mapping strategy, the <literal><subclass></literal> declaration is used. For example:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:2047
-#, no-c-format
-msgid ""
- "<![CDATA[<subclass\n"
- " name=\"ClassName\"\n"
- " discriminator-value=\"discriminator_value\"\n"
- " proxy=\"ProxyInterface\"\n"
- " lazy=\"true|false\"\n"
- " dynamic-update=\"true|false\"\n"
- " dynamic-insert=\"true|false\"\n"
- " entity-name=\"EntityName\"\n"
- " node=\"element-name\"\n"
- " extends=\"SuperclassName\">\n"
- "\n"
- " <property .... />\n"
- " .....\n"
- "</subclass>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:2050 basic_mapping.xml:2108 basic_mapping.xml:2171
#, no-c-format
msgid "<literal>name</literal>: the fully qualified class name of the subclass."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2055
#, no-c-format
msgid "<literal>discriminator-value</literal> (optional - defaults to the class name): a value that distinguishes individual subclasses."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2061
#, no-c-format
msgid "<literal>proxy</literal> (optional): specifies a class or interface used for lazy initializing proxies."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2067
#, no-c-format
msgid "<literal>lazy</literal> (optional - defaults to <literal>true</literal>): setting <literal>lazy=\"false\"</literal> disables the use of lazy fetching."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2075
#, no-c-format
msgid "Each subclass declares its own persistent properties and subclasses. <literal><version></literal> and <literal><id></literal> properties are assumed to be inherited from the root class. Each subclass in a hierarchy must define a unique <literal>discriminator-value</literal>. If this is not specified, the fully qualified Java class name is used."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2083 basic_mapping.xml:2141 basic_mapping.xml:2199
#, no-c-format
-msgid "For information about inheritance mappings see <xref linkend=\"inheritance\"/>."
+msgid "For information about inheritance mappings see <xref linkend=\"inheritance\" />."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:2090
#, no-c-format
msgid "Joined-subclass"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2092
#, no-c-format
msgid "Each subclass can also be mapped to its own table. This is called the table-per-subclass mapping strategy. An inherited state is retrieved by joining with the table of the superclass. To do this you use the <literal><joined-subclass></literal> element. For example:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:2105
-#, no-c-format
-msgid ""
- "<![CDATA[<joined-subclass\n"
- " name=\"ClassName\"\n"
- " table=\"tablename\"\n"
- " proxy=\"ProxyInterface\"\n"
- " lazy=\"true|false\"\n"
- " dynamic-update=\"true|false\"\n"
- " dynamic-insert=\"true|false\"\n"
- " schema=\"schema\"\n"
- " catalog=\"catalog\"\n"
- " extends=\"SuperclassName\"\n"
- " persister=\"ClassName\"\n"
- " subselect=\"SQL expression\"\n"
- " entity-name=\"EntityName\"\n"
- " node=\"element-name\">\n"
- "\n"
- " <key .... >\n"
- "\n"
- " <property .... />\n"
- " .....\n"
- "</joined-subclass>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:2113 basic_mapping.xml:2176
#, no-c-format
msgid "<literal>table</literal>: the name of the subclass table."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2118 basic_mapping.xml:2181
#, no-c-format
msgid "<literal>proxy</literal> (optional): specifies a class or interface to use for lazy initializing proxies."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2124 basic_mapping.xml:2187
#, no-c-format
msgid "<literal>lazy</literal> (optional, defaults to <literal>true</literal>): setting <literal>lazy=\"false\"</literal> disables the use of lazy fetching."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2132
#, no-c-format
msgid "A discriminator column is not required for this mapping strategy. Each subclass must, however, declare a table column holding the object identifier using the <literal><key></literal> element. The mapping at the start of the chapter would then be re-written as:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:2139
-#, no-c-format
-msgid ""
- "<![CDATA[<?xml version=\"1.0\"?>\n"
- "<!DOCTYPE hibernate-mapping PUBLIC\n"
- " \"-//Hibernate/Hibernate Mapping DTD//EN\"\n"
- " \"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd\">\n"
- "\n"
- "<hibernate-mapping package=\"eg\">\n"
- "\n"
- " <class name=\"Cat\" table=\"CATS\">\n"
- " <id name=\"id\" column=\"uid\" type=\"long\">\n"
- " <generator class=\"hilo\"/>\n"
- " </id>\n"
- " <property name=\"birthdate\" type=\"date\"/>\n"
- " <property name=\"color\" not-null=\"true\"/>\n"
- " <property name=\"sex\" not-null=\"true\"/>\n"
- " <property name=\"weight\"/>\n"
- " <many-to-one name=\"mate\"/>\n"
- " <set name=\"kittens\">\n"
- " <key column=\"MOTHER\"/>\n"
- " <one-to-many class=\"Cat\"/>\n"
- " </set>\n"
- " <joined-subclass name=\"DomesticCat\" table=\"DOMESTIC_CATS\">\n"
- " <key column=\"CAT\"/>\n"
- " <property name=\"name\" type=\"string\"/>\n"
- " </joined-subclass>\n"
- " </class>\n"
- "\n"
- " <class name=\"eg.Dog\">\n"
- " <!-- mapping for Dog could go here -->\n"
- " </class>\n"
- "\n"
- "</hibernate-mapping>]]>"
-msgstr ""
-
#. Tag: title
-#: basic_mapping.xml:2148
#, no-c-format
msgid "Union-subclass"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2150
#, no-c-format
msgid "A third option is to map only the concrete classes of an inheritance hierarchy to tables. This is called the table-per-concrete-class strategy. Each table defines all persistent states of the class, including the inherited state. In Hibernate, it is not necessary to explicitly map such inheritance hierarchies. You can map each class with a separate <literal><class></literal> declaration. However, if you wish use polymorphic associations (e.g. an association to the superclass of your hierarchy), you need to use the <literal><union-subclass></literal> mapping. For example:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:2168
-#, no-c-format
-msgid ""
- "<![CDATA[<union-subclass\n"
- " name=\"ClassName\"\n"
- " table=\"tablename\"\n"
- " proxy=\"ProxyInterface\"\n"
- " lazy=\"true|false\"\n"
- " dynamic-update=\"true|false\"\n"
- " dynamic-insert=\"true|false\"\n"
- " schema=\"schema\"\n"
- " catalog=\"catalog\"\n"
- " extends=\"SuperclassName\"\n"
- " abstract=\"true|false\"\n"
- " persister=\"ClassName\"\n"
- " subselect=\"SQL expression\"\n"
- " entity-name=\"EntityName\"\n"
- " node=\"element-name\">\n"
- "\n"
- " <property .... />\n"
- " .....\n"
- "</union-subclass>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:2195
#, no-c-format
msgid "No discriminator column or key column is required for this mapping strategy."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:2206
#, no-c-format
msgid "Join"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2208
#, no-c-format
msgid "Using the <literal><join></literal> element, it is possible to map properties of one class to several tables that have a one-to-one relationship. For example:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:2222
-#, no-c-format
-msgid ""
- "<![CDATA[<join\n"
- " table=\"tablename\"\n"
- " schema=\"owner\"\n"
- " catalog=\"catalog\"\n"
- " fetch=\"join|select\"\n"
- " inverse=\"true|false\"\n"
- " optional=\"true|false\">\n"
- "\n"
- " <key ... />\n"
- "\n"
- " <property ... />\n"
- " ...\n"
- "</join>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:2226
#, no-c-format
msgid "<literal>table</literal>: the name of the joined table."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2243
#, no-c-format
msgid "<literal>fetch</literal> (optional - defaults to <literal>join</literal>): if set to <literal>join</literal>, the default, Hibernate will use an inner join to retrieve a <literal><join></literal> defined by a class or its superclasses. It will use an outer join for a <literal><join></literal> defined by a subclass. If set to <literal>select</literal> then Hibernate will use a sequential select for a <literal><join></literal> defined on a subclass. This will be issued only if a row represents an instance of the subclass. Inner joins will still be used to retrieve a <literal><join></literal> defined by the class and its superclasses."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2256
#, no-c-format
msgid "<literal>inverse</literal> (optional - defaults to <literal>false</literal>): if enabled, Hibernate will not insert or update the properties defined by this join."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2263
#, no-c-format
msgid "<literal>optional</literal> (optional - defaults to <literal>false</literal>): if enabled, Hibernate will insert a row only if the properties defined by this join are non-null. It will always use an outer join to retrieve the properties."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2272
#, no-c-format
msgid "For example, address information for a person can be mapped to a separate table while preserving value type semantics for all properties:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:2277
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Person\"\n"
- " table=\"PERSON\">\n"
- "\n"
- " <id name=\"id\" column=\"PERSON_ID\">...</id>\n"
- "\n"
- " <join table=\"ADDRESS\">\n"
- " <key column=\"ADDRESS_ID\"/>\n"
- " <property name=\"address\"/>\n"
- " <property name=\"zip\"/>\n"
- " <property name=\"country\"/>\n"
- " </join>\n"
- " ...]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:2279
#, no-c-format
msgid "This feature is often only useful for legacy data models. We recommend fewer tables than classes and a fine-grained domain model. However, it is useful for switching between inheritance mapping strategies in a single hierarchy, as explained later."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:2289
#, no-c-format
-msgid "<title>Key</title>"
+msgid "Key"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2291
#, no-c-format
msgid "The <literal><key></literal> element has featured a few times within this guide. It appears anywhere the parent mapping element defines a join to a new table that references the primary key of the original table. It also defines the foreign key in the joined table:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:2307
-#, no-c-format
-msgid ""
- "<![CDATA[<key\n"
- " column=\"columnname\"\n"
- " on-delete=\"noaction|cascade\"\n"
- " property-ref=\"propertyName\"\n"
- " not-null=\"true|false\"\n"
- " update=\"true|false\"\n"
- " unique=\"true|false\"\n"
- "/>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:2318
#, no-c-format
msgid "<literal>on-delete</literal> (optional - defaults to <literal>noaction</literal>): specifies whether the foreign key constraint has database-level cascade delete enabled."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2325
#, no-c-format
msgid "<literal>property-ref</literal> (optional): specifies that the foreign key refers to columns that are not the primary key of the original table. It is provided for legacy data."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2332
#, no-c-format
msgid "<literal>not-null</literal> (optional): specifies that the foreign key columns are not nullable. This is implied whenever the foreign key is also part of the primary key."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2339
#, no-c-format
msgid "<literal>update</literal> (optional): specifies that the foreign key should never be updated. This is implied whenever the foreign key is also part of the primary key."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2346
#, no-c-format
msgid "<literal>unique</literal> (optional): specifies that the foreign key should have a unique constraint. This is implied whenever the foreign key is also the primary key."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2354
#, no-c-format
msgid "For systems where delete performance is important, we recommend that all keys should be defined <literal>on-delete=\"cascade\"</literal>. Hibernate uses a database-level <literal>ON CASCADE DELETE</literal> constraint, instead of many individual <literal>DELETE</literal> statements. Be aware that this feature bypasses Hibernate's usual optimistic locking strategy for versioned data."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2362
#, no-c-format
msgid "The <literal>not-null</literal> and <literal>update</literal> attributes are useful when mapping a unidirectional one-to-many association. If you map a unidirectional one-to-many association to a non-nullable foreign key, you <emphasis>must</emphasis> declare the key column using <literal><key not-null=\"true\"></literal>."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:2372
#, no-c-format
msgid "Column and formula elements"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2373
#, no-c-format
msgid "Mapping elements which accept a <literal>column</literal> attribute will alternatively accept a <literal><column></literal> subelement. Likewise, <literal><formula></literal> is an alternative to the <literal>formula</literal> attribute. For example:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:2379
-#, no-c-format
-msgid ""
- "<![CDATA[<column\n"
- " name=\"column_name\"\n"
- " length=\"N\"\n"
- " precision=\"N\"\n"
- " scale=\"N\"\n"
- " not-null=\"true|false\"\n"
- " unique=\"true|false\"\n"
- " unique-key=\"multicolumn_unique_key_name\"\n"
- " index=\"index_name\"\n"
- " sql-type=\"sql_type_name\"\n"
- " check=\"SQL expression\"\n"
- " default=\"SQL expression\"/>]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: basic_mapping.xml:2381
-#, no-c-format
-msgid "<![CDATA[<formula>SQL expression</formula>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:2383
#, no-c-format
msgid "<literal>column</literal> and <literal>formula</literal> attributes can even be combined within the same property or association mapping to express, for example, exotic join conditions."
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:2389
-#, no-c-format
-msgid ""
- "<![CDATA[<many-to-one name=\"homeAddress\" class=\"Address\"\n"
- " insert=\"false\" update=\"false\">\n"
- " <column name=\"person_id\" not-null=\"true\" length=\"10\"/>\n"
- " <formula>'MAILING'</formula>\n"
- "</many-to-one>]]>"
-msgstr ""
-
#. Tag: title
-#: basic_mapping.xml:2394
#, no-c-format
msgid "Import"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2396
#, no-c-format
msgid "If your application has two persistent classes with the same name, and you do not want to specify the fully qualified package name in Hibernate queries, classes can be \"imported\" explicitly, rather than relying upon <literal>auto-import=\"true\"</literal>. You can also import classes and interfaces that are not explicitly mapped:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:2403
-#, no-c-format
-msgid "<![CDATA[<import class=\"java.lang.Object\" rename=\"Universe\"/>]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: basic_mapping.xml:2410
-#, no-c-format
-msgid ""
- "<![CDATA[<import\n"
- " class=\"ClassName\"\n"
- " rename=\"ShortName\"\n"
- "/>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:2413
#, no-c-format
msgid "<literal>class</literal>: the fully qualified class name of any Java class."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2418
#, no-c-format
msgid "<literal>rename</literal> (optional - defaults to the unqualified class name): a name that can be used in the query language."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:2429
#, no-c-format
-msgid "<title>Any</title>"
+msgid "Any"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2431
#, no-c-format
msgid "There is one more type of property mapping. The <literal><any></literal> mapping element defines a polymorphic association to classes from multiple tables. This type of mapping requires more than one column. The first column contains the type of the associated entity. The remaining columns contain the identifier. It is impossible to specify a foreign key constraint for this kind of association. This is not the usual way of mapping polymorphic associations and you should use this only in special cases. For example, for audit logs, user session data, etc."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2441
#, no-c-format
msgid "The <literal>meta-type</literal> attribute allows the application to specify a custom type that maps database column values to persistent classes that have identifier properties of the type specified by <literal>id-type</literal>. You must specify the mapping from values of the meta-type to class names."
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:2448
-#, no-c-format
-msgid ""
- "<![CDATA[<any name=\"being\" id-type=\"long\" meta-type=\"string\">\n"
- " <meta-value value=\"TBL_ANIMAL\" class=\"Animal\"/>\n"
- " <meta-value value=\"TBL_HUMAN\" class=\"Human\"/>\n"
- " <meta-value value=\"TBL_ALIEN\" class=\"Alien\"/>\n"
- " <column name=\"table_name\"/>\n"
- " <column name=\"id\"/>\n"
- "</any>]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: basic_mapping.xml:2459
-#, no-c-format
-msgid ""
- "<![CDATA[<any\n"
- " name=\"propertyName\"\n"
- " id-type=\"idtypename\"\n"
- " meta-type=\"metatypename\"\n"
- " cascade=\"cascade_style\"\n"
- " access=\"field|property|ClassName\"\n"
- " optimistic-lock=\"true|false\"\n"
- ">\n"
- " <meta-value ... />\n"
- " <meta-value ... />\n"
- " .....\n"
- " <column .... />\n"
- " <column .... />\n"
- " .....\n"
- "</any>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:2462
#, no-c-format
msgid "<literal>name</literal>: the property name."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2467
#, no-c-format
msgid "<literal>id-type</literal>: the identifier type."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2472
#, no-c-format
msgid "<literal>meta-type</literal> (optional - defaults to <literal>string</literal>): any type that is allowed for a discriminator mapping."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2478
#, no-c-format
msgid "<literal>cascade</literal> (optional- defaults to <literal>none</literal>): the cascade style."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2490
#, no-c-format
msgid "<literal>optimistic-lock</literal> (optional - defaults to <literal>true</literal>): specifies that updates to this property either do or do not require acquisition of the optimistic lock. It defines whether a version increment should occur if this property is dirty."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:2505
#, no-c-format
msgid "Hibernate types"
msgstr ""
#. Tag: title
-#: basic_mapping.xml:2508
#, no-c-format
msgid "Entities and values"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2510
#, no-c-format
msgid "In relation to the persistence service, Java language-level objects are classified into two groups:"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2515
#, no-c-format
msgid "An <emphasis>entity</emphasis> exists independently of any other objects holding references to the entity. Contrast this with the usual Java model, where an unreferenced object is garbage collected. Entities must be explicitly saved and deleted. Saves and deletions, however, can be <emphasis>cascaded</emphasis> from a parent entity to its children. This is different from the ODMG model of object persistence by reachability and corresponds more closely to how application objects are usually used in large systems. Entities support circular and shared references. They can also be versioned."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2526
#, no-c-format
msgid "An entity's persistent state consists of references to other entities and instances of <emphasis>value</emphasis> types. Values are primitives: collections (not what is inside a collection), components and certain immutable objects. Unlike entities, values in particular collections and components, <emphasis>are</emphasis> persisted and deleted by reachability. Since value objects and primitives are persisted and deleted along with their containing entity, they cannot be independently versioned. Values have no independent identity, so they cannot be shared by two entities or collections."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2537
#, no-c-format
msgid "Until now, we have been using the term \"persistent class\" to refer to entities. We will continue to do that. Not all user-defined classes with a persistent state, however, are entities. A <emphasis>component</emphasis> is a user-defined class with value semantics. A Java property of type <literal>java.lang.String</literal> also has value semantics. Given this definition, all types (classes) provided by the JDK have value type semantics in Java, while user-defined types can be mapped with entity or value type semantics. This decision is up to the application developer. An entity class in a domain model will normally have shared references to a single instance of that class, while composition or aggregation usually translates to a value type."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2551
#, no-c-format
msgid "We will revisit both concepts throughout this reference guide."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2555
#, no-c-format
msgid "The challenge is to map the Java type system, and the developers' definition of entities and value types, to the SQL/database type system. The bridge between both systems is provided by Hibernate. For entities, <literal><class></literal>, <literal><subclass></literal> and so on are used. For value types we use <literal><property></literal>, <literal><component></literal>etc., that usually have a <literal>type</literal> attribute. The value of this attribute is the name of a Hibernate <emphasis>mapping type</emphasis>. Hibernate provides a range of mappings for standard JDK value types out of the box. You can write your own mapping types and implement your own custom conversion strategies."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2568
#, no-c-format
msgid "With the exception of collections, all built-in Hibernate types support null semantics."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:2575
#, no-c-format
msgid "Basic value types"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2577
#, no-c-format
msgid "The built-in <emphasis>basic mapping types</emphasis> can be roughly categorized into the following:"
msgstr ""
-#. Tag: literal
-#: basic_mapping.xml:2582
+#. Tag: term
#, no-c-format
-msgid "integer, long, short, float, double, character, byte, boolean, yes_no, true_false"
+msgid "<literal>integer, long, short, float, double, character, byte, boolean, yes_no, true_false</literal>"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2585
#, no-c-format
msgid "Type mappings from Java primitives or wrapper classes to appropriate (vendor-specific) SQL column types. <literal>boolean, yes_no</literal> and <literal>true_false</literal> are all alternative encodings for a Java <literal>boolean</literal> or <literal>java.lang.Boolean</literal>."
msgstr ""
-#. Tag: literal
-#: basic_mapping.xml:2594
+#. Tag: term
#, no-c-format
-msgid "string"
+msgid "<literal>string</literal>"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2596
#, no-c-format
msgid "A type mapping from <literal>java.lang.String</literal> to <literal>VARCHAR</literal> (or Oracle <literal>VARCHAR2</literal>)."
msgstr ""
-#. Tag: literal
-#: basic_mapping.xml:2603
+#. Tag: term
#, no-c-format
-msgid "date, time, timestamp"
+msgid "<literal>date, time, timestamp</literal>"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2605
#, no-c-format
msgid "Type mappings from <literal>java.util.Date</literal> and its subclasses to SQL types <literal>DATE</literal>, <literal>TIME</literal> and <literal>TIMESTAMP</literal> (or equivalent)."
msgstr ""
-#. Tag: literal
-#: basic_mapping.xml:2613
+#. Tag: term
#, no-c-format
-msgid "calendar, calendar_date"
+msgid "<literal>calendar, calendar_date</literal>"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2615
#, no-c-format
msgid "Type mappings from <literal>java.util.Calendar</literal> to SQL types <literal>TIMESTAMP</literal> and <literal>DATE</literal> (or equivalent)."
msgstr ""
-#. Tag: literal
-#: basic_mapping.xml:2623
+#. Tag: term
#, no-c-format
-msgid "big_decimal, big_integer"
+msgid "<literal>big_decimal, big_integer</literal>"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2625
#, no-c-format
msgid "Type mappings from <literal>java.math.BigDecimal</literal> and <literal>java.math.BigInteger</literal> to <literal>NUMERIC</literal> (or Oracle <literal>NUMBER</literal>)."
msgstr ""
-#. Tag: literal
-#: basic_mapping.xml:2633
+#. Tag: term
#, no-c-format
-msgid "locale, timezone, currency"
+msgid "<literal>locale, timezone, currency</literal>"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2635
#, no-c-format
msgid "Type mappings from <literal>java.util.Locale</literal>, <literal>java.util.TimeZone</literal> and <literal>java.util.Currency</literal> to <literal>VARCHAR</literal> (or Oracle <literal>VARCHAR2</literal>). Instances of <literal>Locale</literal> and <literal>Currency</literal> are mapped to their ISO codes. Instances of <literal>TimeZone</literal> are mapped to their <literal>ID</literal>."
msgstr ""
-#. Tag: literal
-#: basic_mapping.xml:2647
+#. Tag: term
#, no-c-format
-msgid "class"
+msgid "<literal>class</literal>"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2649
#, no-c-format
msgid "A type mapping from <literal>java.lang.Class</literal> to <literal>VARCHAR</literal> (or Oracle <literal>VARCHAR2</literal>). A <literal>Class</literal> is mapped to its fully qualified name."
msgstr ""
-#. Tag: literal
-#: basic_mapping.xml:2657
+#. Tag: term
#, no-c-format
-msgid "binary"
+msgid "<literal>binary</literal>"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2659
#, no-c-format
msgid "Maps byte arrays to an appropriate SQL binary type."
msgstr ""
-#. Tag: literal
-#: basic_mapping.xml:2665
+#. Tag: term
#, no-c-format
-msgid "text"
+msgid "<literal>text</literal>"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2667
#, no-c-format
msgid "Maps long Java strings to a SQL <literal>CLOB</literal> or <literal>TEXT</literal> type."
msgstr ""
-#. Tag: literal
-#: basic_mapping.xml:2674
+#. Tag: term
#, no-c-format
-msgid "serializable"
+msgid "<literal>serializable</literal>"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2676
#, no-c-format
msgid "Maps serializable Java types to an appropriate SQL binary type. You can also indicate the Hibernate type <literal>serializable</literal> with the name of a serializable Java class or interface that does not default to a basic type."
msgstr ""
-#. Tag: literal
-#: basic_mapping.xml:2685
+#. Tag: term
#, no-c-format
-msgid "clob, blob"
+msgid "<literal>clob, blob</literal>"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2687
#, no-c-format
msgid "Type mappings for the JDBC classes <literal>java.sql.Clob</literal> and <literal>java.sql.Blob</literal>. These types can be inconvenient for some applications, since the blob or clob object cannot be reused outside of a transaction. Driver support is patchy and inconsistent."
msgstr ""
-#. Tag: literal
-#: basic_mapping.xml:2697
+#. Tag: term
#, no-c-format
-msgid "imm_date, imm_time, imm_timestamp, imm_calendar, imm_calendar_date, imm_serializable, imm_binary"
+msgid "<literal>imm_date, imm_time, imm_timestamp, imm_calendar, imm_calendar_date, imm_serializable, imm_binary</literal>"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2701
#, no-c-format
msgid "Type mappings for what are considered mutable Java types. This is where Hibernate makes certain optimizations appropriate only for immutable Java types, and the application treats the object as immutable. For example, you should not call <literal>Date.setTime()</literal> for an instance mapped as <literal>imm_timestamp</literal>. To change the value of the property, and have that change made persistent, the application must assign a new, nonidentical, object to the property."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2716
#, no-c-format
msgid "Unique identifiers of entities and collections can be of any basic type except <literal>binary</literal>, <literal>blob</literal> and <literal>clob</literal>. Composite identifiers are also allowed. See below for more information."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2722
#, no-c-format
msgid "The basic value types have corresponding <literal>Type</literal> constants defined on <literal>org.hibernate.Hibernate</literal>. For example, <literal>Hibernate.STRING</literal> represents the <literal>string</literal> type."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:2731
#, no-c-format
msgid "Custom value types"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2733
#, no-c-format
msgid "It is relatively easy for developers to create their own value types. For example, you might want to persist properties of type <literal>java.lang.BigInteger</literal> to <literal>VARCHAR</literal> columns. Hibernate does not provide a built-in type for this. Custom types are not limited to mapping a property, or collection element, to a single table column. So, for example, you might have a Java property <literal>getName()</literal>/<literal>setName()</literal> of type <literal>java.lang.String</literal> that is persisted to the columns <literal>FIRST_NAME</literal>, <literal>INITIAL</literal>, <literal>SURNAME</literal>."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2744
#, no-c-format
msgid "To implement a custom type, implement either <literal>org.hibernate.UserType</literal> or <literal>org.hibernate.CompositeUserType</literal> and declare properties using the fully qualified classname of the type. View <literal>org.hibernate.test.DoubleStringType</literal> to see the kind of things that are possible."
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:2752
-#, no-c-format
-msgid ""
- "<![CDATA[<property name=\"twoStrings\" type=\"org.hibernate.test.DoubleStringType\">\n"
- " <column name=\"first_string\"/>\n"
- " <column name=\"second_string\"/>\n"
- "</property>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:2754
#, no-c-format
msgid "Notice the use of <literal><column></literal> tags to map a property to multiple columns."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2759
#, no-c-format
msgid "The <literal>CompositeUserType</literal>, <literal>EnhancedUserType</literal>, <literal>UserCollectionType</literal>, and <literal>UserVersionType</literal> interfaces provide support for more specialized uses."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2765
#, no-c-format
msgid "You can even supply parameters to a <literal>UserType</literal> in the mapping file. To do this, your <literal>UserType</literal> must implement the <literal>org.hibernate.usertype.ParameterizedType</literal> interface. To supply parameters to your custom type, you can use the <literal><type></literal> element in your mapping files."
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:2773
-#, no-c-format
-msgid ""
- "<![CDATA[<property name=\"priority\">\n"
- " <type name=\"com.mycompany.usertypes.DefaultValueIntegerType\">\n"
- " <param name=\"default\">0</param>\n"
- " </type>\n"
- "</property>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:2775
#, no-c-format
msgid "The <literal>UserType</literal> can now retrieve the value for the parameter named <literal>default</literal> from the <literal>Properties</literal> object passed to it."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2780
#, no-c-format
msgid "If you regularly use a certain <literal>UserType</literal>, it is useful to define a shorter name for it. You can do this using the <literal><typedef></literal> element. Typedefs assign a name to a custom type, and can also contain a list of default parameter values if the type is parameterized."
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:2787
-#, no-c-format
-msgid ""
- "<![CDATA[<typedef class=\"com.mycompany.usertypes.DefaultValueIntegerType\" name=\"default_zero\">\n"
- " <param name=\"default\">0</param>\n"
- "</typedef>]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: basic_mapping.xml:2789
-#, no-c-format
-msgid "<![CDATA[<property name=\"priority\" type=\"default_zero\"/>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:2791
#, no-c-format
msgid "It is also possible to override the parameters supplied in a typedef on a case-by-case basis by using type parameters on the property mapping."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2796
#, no-c-format
msgid "Even though Hibernate's rich range of built-in types and support for components means you will rarely need to use a custom type, it is considered good practice to use custom types for non-entity classes that occur frequently in your application. For example, a <literal>MonetaryAmount</literal> class is a good candidate for a <literal>CompositeUserType</literal>, even though it could be mapped as a component. One reason for this is abstraction. With a custom type, your mapping documents would be protected against changes to the way monetary values are represented."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:2812
#, no-c-format
msgid "Mapping a class more than once"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2813
#, no-c-format
msgid "It is possible to provide more than one mapping for a particular persistent class. In this case, you must specify an <emphasis>entity name</emphasis> to disambiguate between instances of the two mapped entities. By default, the entity name is the same as the class name. Hibernate lets you specify the entity name when working with persistent objects, when writing queries, or when mapping associations to the named entity."
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:2821
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Contract\" table=\"Contracts\"\n"
- " entity-name=\"CurrentContract\">\n"
- " ...\n"
- " <set name=\"history\" inverse=\"true\"\n"
- " order-by=\"effectiveEndDate desc\">\n"
- " <key column=\"currentContractId\"/>\n"
- " <one-to-many entity-name=\"HistoricalContract\"/>\n"
- " </set>\n"
- "</class>\n"
- "\n"
- "<class name=\"Contract\" table=\"ContractHistory\"\n"
- " entity-name=\"HistoricalContract\">\n"
- " ...\n"
- " <many-to-one name=\"currentContract\"\n"
- " column=\"currentContractId\"\n"
- " entity-name=\"CurrentContract\"/>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:2823
#, no-c-format
msgid "Associations are now specified using <literal>entity-name</literal> instead of <literal>class</literal>."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:2831
#, no-c-format
msgid "SQL quoted identifiers"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2832
#, no-c-format
msgid "You can force Hibernate to quote an identifier in the generated SQL by enclosing the table or column name in backticks in the mapping document. Hibernate will use the correct quotation style for the SQL <literal>Dialect</literal>. This is usually double quotes, but the SQL Server uses brackets and MySQL uses backticks."
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:2839
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"LineItem\" table=\"`Line Item`\">\n"
- " <id name=\"id\" column=\"`Item Id`\"/><generator class=\"assigned\"/></id>\n"
- " <property name=\"itemNumber\" column=\"`Item #`\"/>\n"
- " ...\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: title
-#: basic_mapping.xml:2845
#, no-c-format
msgid "Metadata alternatives"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2847
#, no-c-format
msgid "XML does not suit all users so there are some alternative ways to define O/R mapping metadata in Hibernate."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:2852
#, no-c-format
msgid "Using XDoclet markup"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2854
#, no-c-format
msgid "Many Hibernate users prefer to embed mapping information directly in sourcecode using XDoclet <literal>@hibernate.tags</literal>. We do not cover this approach in this reference guide since it is considered part of XDoclet. However, we include the following example of the <literal>Cat</literal> class with XDoclet mappings:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:2861
-#, no-c-format
-msgid ""
- "<![CDATA[package eg;\n"
- "import java.util.Set;\n"
- "import java.util.Date;\n"
- "\n"
- "/**\n"
- " * @hibernate.class\n"
- " * table=\"CATS\"\n"
- " */\n"
- "public class Cat {\n"
- " private Long id; // identifier\n"
- " private Date birthdate;\n"
- " private Cat mother;\n"
- " private Set kittens\n"
- " private Color color;\n"
- " private char sex;\n"
- " private float weight;\n"
- "\n"
- " /*\n"
- " * @hibernate.id\n"
- " * generator-class=\"native\"\n"
- " * column=\"CAT_ID\"\n"
- " */\n"
- " public Long getId() {\n"
- " return id;\n"
- " }\n"
- " private void setId(Long id) {\n"
- " this.id=id;\n"
- " }\n"
- "\n"
- " /**\n"
- " * @hibernate.many-to-one\n"
- " * column=\"PARENT_ID\"\n"
- " */\n"
- " public Cat getMother() {\n"
- " return mother;\n"
- " }\n"
- " void setMother(Cat mother) {\n"
- " this.mother = mother;\n"
- " }\n"
- "\n"
- " /**\n"
- " * @hibernate.property\n"
- " * column=\"BIRTH_DATE\"\n"
- " */\n"
- " public Date getBirthdate() {\n"
- " return birthdate;\n"
- " }\n"
- " void setBirthdate(Date date) {\n"
- " birthdate = date;\n"
- " }\n"
- " /**\n"
- " * @hibernate.property\n"
- " * column=\"WEIGHT\"\n"
- " */\n"
- " public float getWeight() {\n"
- " return weight;\n"
- " }\n"
- " void setWeight(float weight) {\n"
- " this.weight = weight;\n"
- " }\n"
- "\n"
- " /**\n"
- " * @hibernate.property\n"
- " * column=\"COLOR\"\n"
- " * not-null=\"true\"\n"
- " */\n"
- " public Color getColor() {\n"
- " return color;\n"
- " }\n"
- " void setColor(Color color) {\n"
- " this.color = color;\n"
- " }\n"
- " /**\n"
- " * @hibernate.set\n"
- " * inverse=\"true\"\n"
- " * order-by=\"BIRTH_DATE\"\n"
- " * @hibernate.collection-key\n"
- " * column=\"PARENT_ID\"\n"
- " * @hibernate.collection-one-to-many\n"
- " */\n"
- " public Set getKittens() {\n"
- " return kittens;\n"
- " }\n"
- " void setKittens(Set kittens) {\n"
- " this.kittens = kittens;\n"
- " }\n"
- " // addKitten not needed by Hibernate\n"
- " public void addKitten(Cat kitten) {\n"
- " kittens.add(kitten);\n"
- " }\n"
- "\n"
- " /**\n"
- " * @hibernate.property\n"
- " * column=\"SEX\"\n"
- " * not-null=\"true\"\n"
- " * update=\"false\"\n"
- " */\n"
- " public char getSex() {\n"
- " return sex;\n"
- " }\n"
- " void setSex(char sex) {\n"
- " this.sex=sex;\n"
- " }\n"
- "}]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:2863
#, no-c-format
msgid "See the Hibernate website for more examples of XDoclet and Hibernate."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:2870
#, no-c-format
msgid "Using JDK 5.0 Annotations"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2872
#, no-c-format
msgid "JDK 5.0 introduced XDoclet-style annotations at the language level that are type-safe and checked at compile time. This mechanism is more powerful than XDoclet annotations and better supported by tools and IDEs. IntelliJ IDEA, for example, supports auto-completion and syntax highlighting of JDK 5.0 annotations. The new revision of the EJB specification (JSR-220) uses JDK 5.0 annotations as the primary metadata mechanism for entity beans. Hibernate3 implements the <literal>EntityManager</literal> of JSR-220 (the persistence API). Support for mapping metadata is available via the <emphasis>Hibernate Annotations</emphasis> package as a separate download. Both EJB3 (JSR-220) and Hibernate3 metadata is supported."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2883
#, no-c-format
msgid "This is an example of a POJO class annotated as an EJB entity bean:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:2887
-#, no-c-format
-msgid ""
- "<![CDATA[@Entity(access = AccessType.FIELD)\n"
- "public class Customer implements Serializable {\n"
- "\n"
- " @Id;\n"
- " Long id;\n"
- "\n"
- " String firstName;\n"
- " String lastName;\n"
- " Date birthday;\n"
- "\n"
- " @Transient\n"
- " Integer age;\n"
- "\n"
- " @Embedded\n"
- " private Address homeAddress;\n"
- "\n"
- " @OneToMany(cascade=CascadeType.ALL)\n"
- " @JoinColumn(name=\"CUSTOMER_ID\")\n"
- " Set<Order> orders;\n"
- "\n"
- " // Getter/setter and business methods\n"
- "}]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:2891
#, no-c-format
msgid "Support for JDK 5.0 Annotations (and JSR-220) is currently under development. Please refer to the Hibernate Annotations module for more details."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:2901
#, no-c-format
msgid "Generated properties"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2902
#, no-c-format
msgid "Generated properties are properties that have their values generated by the database. Typically, Hibernate applications needed to <literal>refresh</literal> objects that contain any properties for which the database was generating values. Marking properties as generated, however, lets the application delegate this responsibility to Hibernate. When Hibernate issues an SQL INSERT or UPDATE for an entity that has defined generated properties, it immediately issues a select afterwards to retrieve the generated values."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2911
#, no-c-format
-msgid "Properties marked as generated must additionally be non-insertable and non-updateable. Only <link linkend=\"mapping-declaration-version\">versions</link>, <link linkend=\"mapping-declaration-timestamp\">timestamps</link>, and <link linkend=\"mapping-declaration-property\">simple properties</link>, can be marked as generated."
+msgid "Properties marked as generated must additionally be non-insertable and non-updateable. Only versions (<xref linkend=\"mapping-declaration-version\" />), timestamps (<xref linkend=\"mapping-declaration-timestamp\" />), and simple properties (<xref linkend=\"mapping-declaration-property\" />), can be marked as generated."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2918
#, no-c-format
msgid "<literal>never</literal> (the default): the given property value is not generated within the database."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2922
#, no-c-format
-msgid "<literal>insert</literal>: the given property value is generated on insert, but is not regenerated on subsequent updates. Properties like created-date fall into this category. Even though <link linkend=\"mapping-declaration-version\">version</link> and <link linkend=\"mapping-declaration-timestamp\">timestamp</link> properties can be marked as generated, this option is not available."
+msgid "<literal>insert</literal>: the given property value is generated on insert, but is not regenerated on subsequent updates. Properties like created-date fall into this category. Even though version (<xref linkend=\"mapping-declaration-version\" />) and timestamp (<xref linkend=\"mapping-declaration-timestamp\" />) properties can be marked as generated, this option is not available."
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2930
#, no-c-format
msgid "<literal>always</literal>: the property value is generated both on insert and on update."
msgstr ""
#. Tag: title
-#: basic_mapping.xml:2937
#, no-c-format
msgid "Auxiliary database objects"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2938
#, no-c-format
msgid "Auxiliary database objects allow for the CREATE and DROP of arbitrary database objects. In conjunction with Hibernate's schema evolution tools, they have the ability to fully define a user schema within the Hibernate mapping files. Although designed specifically for creating and dropping things like triggers or stored procedures, any SQL command that can be run via a <literal>java.sql.Statement.execute()</literal> method is valid (for example, ALTERs, INSERTS, etc.). There are essentially two modes for defining auxiliary database objects:"
msgstr ""
#. Tag: para
-#: basic_mapping.xml:2947
#, no-c-format
msgid "The first mode is to explicitly list the CREATE and DROP commands in the mapping file:"
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:2951
-#, no-c-format
-msgid ""
- "<![CDATA[<hibernate-mapping>\n"
- " ...\n"
- " <database-object>\n"
- " <create>CREATE TRIGGER my_trigger ...</create>\n"
- " <drop>DROP TRIGGER my_trigger</drop>\n"
- " </database-object>\n"
- "</hibernate-mapping>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:2952
#, no-c-format
msgid "The second mode is to supply a custom class that constructs the CREATE and DROP commands. This custom class must implement the <literal>org.hibernate.mapping.AuxiliaryDatabaseObject</literal> interface."
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:2957
-#, no-c-format
-msgid ""
- "<![CDATA[<hibernate-mapping>\n"
- " ...\n"
- " <database-object>\n"
- " <definition class=\"MyTriggerDefinition\"/>\n"
- " </database-object>\n"
- "</hibernate-mapping>]]>"
-msgstr ""
-
#. Tag: para
-#: basic_mapping.xml:2958
#, no-c-format
msgid "Additionally, these database objects can be optionally scoped so that they only apply when certain dialects are used."
msgstr ""
-#. Tag: programlisting
-#: basic_mapping.xml:2962
-#, no-c-format
-msgid ""
- "<![CDATA[<hibernate-mapping>\n"
- " ...\n"
- " <database-object>\n"
- " <definition class=\"MyTriggerDefinition\"/>\n"
- " <dialect-scope name=\"org.hibernate.dialect.Oracle9iDialect\"/>\n"
- " <dialect-scope name=\"org.hibernate.dialect.Oracle10gDialect\"/>\n"
- " </database-object>\n"
- "</hibernate-mapping>]]>"
-msgstr ""
-
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/batch.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/batch.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/batch.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,379 +1,189 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-10 21:02+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:18\n"
+"PO-Revision-Date: 2010-01-08T04:07:18\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
-#: batch.xml:29
#, no-c-format
msgid "Batch processing"
msgstr ""
#. Tag: para
-#: batch.xml:31
#, no-c-format
msgid "A naive approach to inserting 100,000 rows in the database using Hibernate might look like this:"
msgstr ""
-#. Tag: programlisting
-#: batch.xml:36
-#, no-c-format
-msgid ""
- "<![CDATA[Session session = sessionFactory.openSession();\n"
- "Transaction tx = session.beginTransaction();\n"
- "for ( int i=0; i<100000; i++ ) {\n"
- " Customer customer = new Customer(.....);\n"
- " session.save(customer);\n"
- "}\n"
- "tx.commit();\n"
- "session.close();]]>"
-msgstr ""
-
#. Tag: para
-#: batch.xml:38
#, no-c-format
msgid "This would fall over with an <literal>OutOfMemoryException</literal> somewhere around the 50,000th row. That is because Hibernate caches all the newly inserted <literal>Customer</literal> instances in the session-level cache. In this chapter we will show you how to avoid this problem."
msgstr ""
#. Tag: para
-#: batch.xml:45
#, no-c-format
msgid "If you are undertaking batch processing you will need to enable the use of JDBC batching. This is absolutely essential if you want to achieve optimal performance. Set the JDBC batch size to a reasonable number (10-50, for example):"
msgstr ""
-#. Tag: programlisting
-#: batch.xml:52
-#, no-c-format
-msgid "<![CDATA[hibernate.jdbc.batch_size 20]]>"
-msgstr ""
-
#. Tag: para
-#: batch.xml:54
#, no-c-format
msgid "Hibernate disables insert batching at the JDBC level transparently if you use an <literal>identity</literal> identifier generator."
msgstr ""
#. Tag: para
-#: batch.xml:59
#, no-c-format
msgid "You can also do this kind of work in a process where interaction with the second-level cache is completely disabled:"
msgstr ""
-#. Tag: programlisting
-#: batch.xml:64
-#, no-c-format
-msgid "<![CDATA[hibernate.cache.use_second_level_cache false]]>"
-msgstr ""
-
#. Tag: para
-#: batch.xml:66
#, no-c-format
msgid "However, this is not absolutely necessary, since we can explicitly set the <literal>CacheMode</literal> to disable interaction with the second-level cache."
msgstr ""
#. Tag: title
-#: batch.xml:72
#, no-c-format
msgid "Batch inserts"
msgstr ""
#. Tag: para
-#: batch.xml:74
#, no-c-format
msgid "When making new objects persistent <literal>flush()</literal> and then <literal>clear()</literal> the session regularly in order to control the size of the first-level cache."
msgstr ""
-#. Tag: programlisting
-#: batch.xml:80
-#, no-c-format
-msgid ""
- "<![CDATA[Session session = sessionFactory.openSession();\n"
- "Transaction tx = session.beginTransaction();\n"
- " \n"
- "for ( int i=0; i<100000; i++ ) {\n"
- " Customer customer = new Customer(.....);\n"
- " session.save(customer);\n"
- " if ( i % 20 == 0 ) { //20, same as the JDBC batch size\n"
- " //flush a batch of inserts and release memory:\n"
- " session.flush();\n"
- " session.clear();\n"
- " }\n"
- "}\n"
- " \n"
- "tx.commit();\n"
- "session.close();]]>"
-msgstr ""
-
#. Tag: title
-#: batch.xml:85
#, no-c-format
msgid "Batch updates"
msgstr ""
#. Tag: para
-#: batch.xml:87
#, no-c-format
msgid "For retrieving and updating data, the same ideas apply. In addition, you need to use <literal>scroll()</literal> to take advantage of server-side cursors for queries that return many rows of data."
msgstr ""
-#. Tag: programlisting
-#: batch.xml:93
-#, no-c-format
-msgid ""
- "<![CDATA[Session session = sessionFactory.openSession();\n"
- "Transaction tx = session.beginTransaction();\n"
- " \n"
- "ScrollableResults customers = session.getNamedQuery(\"GetCustomers\")\n"
- " .setCacheMode(CacheMode.IGNORE)\n"
- " .scroll(ScrollMode.FORWARD_ONLY);\n"
- "int count=0;\n"
- "while ( customers.next() ) {\n"
- " Customer customer = (Customer) customers.get(0);\n"
- " customer.updateStuff(...);\n"
- " if ( ++count % 20 == 0 ) {\n"
- " //flush a batch of updates and release memory:\n"
- " session.flush();\n"
- " session.clear();\n"
- " }\n"
- "}\n"
- " \n"
- "tx.commit();\n"
- "session.close();]]>"
-msgstr ""
-
#. Tag: title
-#: batch.xml:98
#, no-c-format
msgid "The StatelessSession interface"
msgstr ""
#. Tag: para
-#: batch.xml:99
#, no-c-format
msgid "Alternatively, Hibernate provides a command-oriented API that can be used for streaming data to and from the database in the form of detached objects. A <literal>StatelessSession</literal> has no persistence context associated with it and does not provide many of the higher-level life cycle semantics. In particular, a stateless session does not implement a first-level cache nor interact with any second-level or query cache. It does not implement transactional write-behind or automatic dirty checking. Operations performed using a stateless session never cascade to associated instances. Collections are ignored by a stateless session. Operations performed via a stateless session bypass Hibernate's event model and interceptors. Due to the lack of a first-level cache, Stateless sessions are vulnerable to data aliasing effects. A stateless session is a lower-level abstraction that is much closer to the underlying JDBC."
msgstr ""
-#. Tag: programlisting
-#: batch.xml:114
-#, no-c-format
-msgid ""
- "<![CDATA[StatelessSession session = sessionFactory.openStatelessSession();\n"
- "Transaction tx = session.beginTransaction();\n"
- " \n"
- "ScrollableResults customers = session.getNamedQuery(\"GetCustomers\")\n"
- " .scroll(ScrollMode.FORWARD_ONLY);\n"
- "while ( customers.next() ) {\n"
- " Customer customer = (Customer) customers.get(0);\n"
- " customer.updateStuff(...);\n"
- " session.update(customer);\n"
- "}\n"
- " \n"
- "tx.commit();\n"
- "session.close();]]>"
-msgstr ""
-
#. Tag: para
-#: batch.xml:116
#, no-c-format
msgid "In this code example, the <literal>Customer</literal> instances returned by the query are immediately detached. They are never associated with any persistence context."
msgstr ""
#. Tag: para
-#: batch.xml:122
#, no-c-format
msgid "The <literal>insert(), update()</literal> and <literal>delete()</literal> operations defined by the <literal>StatelessSession</literal> interface are considered to be direct database row-level operations. They result in the immediate execution of a SQL <literal>INSERT, UPDATE</literal> or <literal>DELETE</literal> respectively. They have different semantics to the <literal>save(), saveOrUpdate()</literal> and <literal>delete()</literal> operations defined by the <literal>Session</literal> interface."
msgstr ""
#. Tag: title
-#: batch.xml:135
#, no-c-format
msgid "DML-style operations"
msgstr ""
#. Tag: para
-#: batch.xml:137
#, no-c-format
-msgid "As already discussed, automatic and transparent object/relational mapping is concerned with the management of the object state. The object state is available in memory. This means that manipulating data directly in the database (using the SQL <literal>Data Manipulation Language</literal> (DML) the statements: <literal>INSERT</literal>, <literal>UPDATE</literal>, <literal>DELETE</literal>) will not affect in-memory state. However, Hibernate provides methods for bulk SQL-style DML statement execution that is performed through the Hibernate Query Language (<link linkend=\"queryhql\">HQL</link>)."
+msgid "As already discussed, automatic and transparent object/relational mapping is concerned with the management of the object state. The object state is available in memory. This means that manipulating data directly in the database (using the SQL <literal>Data Manipulation Language</literal> (DML) the statements: <literal>INSERT</literal>, <literal>UPDATE</literal>, <literal>DELETE</literal>) will not affect in-memory state. However, Hibernate provides methods for bulk SQL-style DML statement execution that is performed through the Hibernate Query Language (<xref linkend=\"queryhql\" />)."
msgstr ""
#. Tag: para
-#: batch.xml:146
#, no-c-format
msgid "The pseudo-syntax for <literal>UPDATE</literal> and <literal>DELETE</literal> statements is: <literal>( UPDATE | DELETE ) FROM? EntityName (WHERE where_conditions)?</literal>."
msgstr ""
#. Tag: para
-#: batch.xml:151
#, no-c-format
msgid "Some points to note:"
msgstr ""
#. Tag: para
-#: batch.xml:157
#, no-c-format
msgid "In the from-clause, the FROM keyword is optional"
msgstr ""
#. Tag: para
-#: batch.xml:162
#, no-c-format
msgid "There can only be a single entity named in the from-clause. It can, however, be aliased. If the entity name is aliased, then any property references must be qualified using that alias. If the entity name is not aliased, then it is illegal for any property references to be qualified."
msgstr ""
#. Tag: para
-#: batch.xml:170
#, no-c-format
-msgid "No <link linkend=\"queryhql-joins-forms\">joins</link>, either implicit or explicit, can be specified in a bulk HQL query. Sub-queries can be used in the where-clause, where the subqueries themselves may contain joins."
+msgid "No <xref linkend=\"queryhql-joins-forms\" />, either implicit or explicit, can be specified in a bulk HQL query. Sub-queries can be used in the where-clause, where the subqueries themselves may contain joins."
msgstr ""
#. Tag: para
-#: batch.xml:177
#, no-c-format
msgid "The where-clause is also optional."
msgstr ""
#. Tag: para
-#: batch.xml:183
#, no-c-format
msgid "As an example, to execute an HQL <literal>UPDATE</literal>, use the <literal>Query.executeUpdate()</literal> method. The method is named for those familiar with JDBC's <literal>PreparedStatement.executeUpdate()</literal>:"
msgstr ""
-#. Tag: programlisting
-#: batch.xml:189
-#, no-c-format
-msgid ""
- "<![CDATA[Session session = sessionFactory.openSession();\n"
- "Transaction tx = session.beginTransaction();\n"
- "\n"
- "String hqlUpdate = \"update Customer c set c.name = :newName where c.name = :oldName\";\n"
- "// or String hqlUpdate = \"update Customer set name = :newName where name = :oldName\";\n"
- "int updatedEntities = s.createQuery( hqlUpdate )\n"
- " .setString( \"newName\", newName )\n"
- " .setString( \"oldName\", oldName )\n"
- " .executeUpdate();\n"
- "tx.commit();\n"
- "session.close();]]>"
-msgstr ""
-
#. Tag: para
-#: batch.xml:191
#, no-c-format
-msgid "In keeping with the EJB3 specification, HQL <literal>UPDATE</literal> statements, by default, do not effect the <link linkend=\"mapping-declaration-version\">version</link> or the <link linkend=\"mapping-declaration-timestamp\">timestamp</link> property values for the affected entities. However, you can force Hibernate to reset the <literal>version</literal> or <literal>timestamp</literal> property values through the use of a <literal>versioned update</literal>. This is achieved by adding the <literal>VERSIONED</literal> keyword after the <literal>UPDATE</literal> keyword."
+msgid "In keeping with the EJB3 specification, HQL <literal>UPDATE</literal> statements, by default, do not effect the version (<xref linkend=\"mapping-declaration-version\" />) or the timestamp (<xref linkend=\"mapping-declaration-timestamp\" />) property values for the affected entities. However, you can force Hibernate to reset the <literal>version</literal> or <literal>timestamp</literal> property values through the use of a <literal>versioned update</literal>. This is achieved by adding the <literal>VERSIONED</literal> keyword after the <literal>UPDATE</literal> keyword."
msgstr ""
-#. Tag: programlisting
-#: batch.xml:201
-#, no-c-format
-msgid ""
- "<![CDATA[Session session = sessionFactory.openSession();\n"
- "Transaction tx = session.beginTransaction();\n"
- "String hqlVersionedUpdate = \"update versioned Customer set name = :newName where name = :oldName\";\n"
- "int updatedEntities = s.createQuery( hqlUpdate )\n"
- " .setString( \"newName\", newName )\n"
- " .setString( \"oldName\", oldName )\n"
- " .executeUpdate();\n"
- "tx.commit();\n"
- "session.close();]]>"
-msgstr ""
-
#. Tag: para
-#: batch.xml:203
#, no-c-format
msgid "Custom version types, <literal>org.hibernate.usertype.UserVersionType</literal>, are not allowed in conjunction with a <literal>update versioned</literal> statement."
msgstr ""
#. Tag: para
-#: batch.xml:208
#, no-c-format
msgid "To execute an HQL <literal>DELETE</literal>, use the same <literal>Query.executeUpdate()</literal> method:"
msgstr ""
-#. Tag: programlisting
-#: batch.xml:213
-#, no-c-format
-msgid ""
- "<![CDATA[Session session = sessionFactory.openSession();\n"
- "Transaction tx = session.beginTransaction();\n"
- "\n"
- "String hqlDelete = \"delete Customer c where c.name = :oldName\";\n"
- "// or String hqlDelete = \"delete Customer where name = :oldName\";\n"
- "int deletedEntities = s.createQuery( hqlDelete )\n"
- " .setString( \"oldName\", oldName )\n"
- " .executeUpdate();\n"
- "tx.commit();\n"
- "session.close();]]>"
-msgstr ""
-
#. Tag: para
-#: batch.xml:215
#, no-c-format
msgid "The <literal>int</literal> value returned by the <literal>Query.executeUpdate()</literal> method indicates the number of entities effected by the operation. This may or may not correlate to the number of rows effected in the database. An HQL bulk operation might result in multiple actual SQL statements being executed (for joined-subclass, for example). The returned number indicates the number of actual entities affected by the statement. Going back to the example of joined-subclass, a delete against one of the subclasses may actually result in deletes against not just the table to which that subclass is mapped, but also the \"root\" table and potentially joined-subclass tables further down the inheritance hierarchy."
msgstr ""
#. Tag: para
-#: batch.xml:226
#, no-c-format
msgid "The pseudo-syntax for <literal>INSERT</literal> statements is: <literal>INSERT INTO EntityName properties_list select_statement</literal>. Some points to note:"
msgstr ""
#. Tag: para
-#: batch.xml:234
#, no-c-format
msgid "Only the INSERT INTO ... SELECT ... form is supported; not the INSERT INTO ... VALUES ... form."
msgstr ""
#. Tag: para
-#: batch.xml:237
#, no-c-format
msgid "The properties_list is analogous to the <literal>column specification</literal> in the SQL <literal>INSERT</literal> statement. For entities involved in mapped inheritance, only properties directly defined on that given class-level can be used in the properties_list. Superclass properties are not allowed and subclass properties do not make sense. In other words, <literal>INSERT</literal> statements are inherently non-polymorphic."
msgstr ""
#. Tag: para
-#: batch.xml:247
#, no-c-format
msgid "select_statement can be any valid HQL select query, with the caveat that the return types must match the types expected by the insert. Currently, this is checked during query compilation rather than allowing the check to relegate to the database. This might, however, cause problems between Hibernate <literal>Type</literal>s which are <emphasis>equivalent</emphasis> as opposed to <emphasis>equal</emphasis>. This might cause issues with mismatches between a property defined as a <literal>org.hibernate.type.DateType</literal> and a property defined as a <literal>org.hibernate.type.TimestampType</literal>, even though the database might not make a distinction or might be able to handle the conversion."
msgstr ""
#. Tag: para
-#: batch.xml:259
#, no-c-format
msgid "For the id property, the insert statement gives you two options. You can either explicitly specify the id property in the properties_list, in which case its value is taken from the corresponding select expression, or omit it from the properties_list, in which case a generated value is used. This latter option is only available when using id generators that operate in the database; attempting to use this option with any \"in memory\" type generators will cause an exception during parsing. For the purposes of this discussion, in-database generators are considered to be <literal>org.hibernate.id.SequenceGenerator</literal> (and its subclasses) and any implementers of <literal>org.hibernate.id.PostInsertIdentifierGenerator</literal>. The most notable exception here is <literal>org.hibernate.id.TableHiLoGenerator</literal>, which cannot be used because it does not expose a selectable way to get its values."
msgstr ""
#. Tag: para
-#: batch.xml:274
#, no-c-format
msgid "For properties mapped as either <literal>version</literal> or <literal>timestamp</literal>, the insert statement gives you two options. You can either specify the property in the properties_list, in which case its value is taken from the corresponding select expressions, or omit it from the properties_list, in which case the <literal>seed value</literal> defined by the <literal>org.hibernate.type.VersionType</literal> is used."
msgstr ""
#. Tag: para
-#: batch.xml:284
#, no-c-format
msgid "The following is an example of an HQL <literal>INSERT</literal> statement execution:"
msgstr ""
-#. Tag: programlisting
-#: batch.xml:288
-#, no-c-format
-msgid ""
- "<![CDATA[Session session = sessionFactory.openSession();\n"
- "Transaction tx = session.beginTransaction();\n"
- "\n"
- "String hqlInsert = \"insert into DelinquentAccount (id, name) select c.id, c.name from Customer c where ...\";\n"
- "int createdEntities = s.createQuery( hqlInsert )\n"
- " .executeUpdate();\n"
- "tx.commit();\n"
- "session.close();]]>"
-msgstr ""
-
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/best_practices.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/best_practices.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/best_practices.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,249 +1,208 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-10 21:02+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:18\n"
+"PO-Revision-Date: 2010-01-08T04:07:18\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
-#: best_practices.xml:29
#, no-c-format
msgid "Best Practices"
msgstr ""
#. Tag: term
-#: best_practices.xml:33
#, no-c-format
msgid "Write fine-grained classes and map them using <literal><component></literal>:"
msgstr ""
#. Tag: para
-#: best_practices.xml:35
#, no-c-format
msgid "Use an <literal>Address</literal> class to encapsulate <literal>street</literal>, <literal>suburb</literal>, <literal>state</literal>, <literal>postcode</literal>. This encourages code reuse and simplifies refactoring."
msgstr ""
#. Tag: term
-#: best_practices.xml:43
#, no-c-format
msgid "Declare identifier properties on persistent classes:"
msgstr ""
#. Tag: para
-#: best_practices.xml:45
#, no-c-format
msgid "Hibernate makes identifier properties optional. There are a range of reasons why you should use them. We recommend that identifiers be 'synthetic', that is, generated with no business meaning."
msgstr ""
#. Tag: term
-#: best_practices.xml:53
#, no-c-format
msgid "Identify natural keys:"
msgstr ""
#. Tag: para
-#: best_practices.xml:55
#, no-c-format
msgid "Identify natural keys for all entities, and map them using <literal><natural-id></literal>. Implement <literal>equals()</literal> and <literal>hashCode()</literal> to compare the properties that make up the natural key."
msgstr ""
#. Tag: term
-#: best_practices.xml:63
#, no-c-format
msgid "Place each class mapping in its own file:"
msgstr ""
#. Tag: para
-#: best_practices.xml:65
#, no-c-format
msgid "Do not use a single monolithic mapping document. Map <literal>com.eg.Foo</literal> in the file <literal>com/eg/Foo.hbm.xml</literal>. This makes sense, particularly in a team environment."
msgstr ""
#. Tag: term
-#: best_practices.xml:73
#, no-c-format
msgid "Load mappings as resources:"
msgstr ""
#. Tag: para
-#: best_practices.xml:75
#, no-c-format
msgid "Deploy the mappings along with the classes they map."
msgstr ""
#. Tag: term
-#: best_practices.xml:81
#, no-c-format
msgid "Consider externalizing query strings:"
msgstr ""
#. Tag: para
-#: best_practices.xml:83
#, no-c-format
msgid "This is recommended if your queries call non-ANSI-standard SQL functions. Externalizing the query strings to mapping files will make the application more portable."
msgstr ""
#. Tag: term
-#: best_practices.xml:91
#, no-c-format
msgid "Use bind variables."
msgstr ""
#. Tag: para
-#: best_practices.xml:93
#, no-c-format
msgid "As in JDBC, always replace non-constant values by \"?\". Do not use string manipulation to bind a non-constant value in a query. You should also consider using named parameters in queries."
msgstr ""
#. Tag: term
-#: best_practices.xml:101
#, no-c-format
msgid "Do not manage your own JDBC connections:"
msgstr ""
#. Tag: para
-#: best_practices.xml:103
#, no-c-format
msgid "Hibernate allows the application to manage JDBC connections, but his approach should be considered a last-resort. If you cannot use the built-in connection providers, consider providing your own implementation of <literal>org.hibernate.connection.ConnectionProvider</literal>."
msgstr ""
#. Tag: term
-#: best_practices.xml:111
#, no-c-format
msgid "Consider using a custom type:"
msgstr ""
#. Tag: para
-#: best_practices.xml:113
#, no-c-format
msgid "Suppose you have a Java type from a library that needs to be persisted but does not provide the accessors needed to map it as a component. You should consider implementing <literal>org.hibernate.UserType</literal>. This approach frees the application code from implementing transformations to/from a Hibernate type."
msgstr ""
#. Tag: term
-#: best_practices.xml:122
#, no-c-format
msgid "Use hand-coded JDBC in bottlenecks:"
msgstr ""
#. Tag: para
-#: best_practices.xml:124
#, no-c-format
msgid "In performance-critical areas of the system, some kinds of operations might benefit from direct JDBC. Do not assume, however, that JDBC is necessarily faster. Please wait until you <emphasis>know</emphasis> something is a bottleneck. If you need to use direct JDBC, you can open a Hibernate <literal>Session</literal> and usingfile:///usr/share/doc/HTML/en-US/index.html that JDBC connection. This way you can still use the same transaction strategy and underlying connection provider."
msgstr ""
#. Tag: term
-#: best_practices.xml:134
#, no-c-format
msgid "Understand <literal>Session</literal> flushing:"
msgstr ""
#. Tag: para
-#: best_practices.xml:136
#, no-c-format
msgid "Sometimes the Session synchronizes its persistent state with the database. Performance will be affected if this process occurs too often. You can sometimes minimize unnecessary flushing by disabling automatic flushing, or even by changing the order of queries and other operations within a particular transaction."
msgstr ""
#. Tag: term
-#: best_practices.xml:145
#, no-c-format
msgid "In a three tiered architecture, consider using detached objects:"
msgstr ""
#. Tag: para
-#: best_practices.xml:147
#, no-c-format
msgid "When using a servlet/session bean architecture, you can pass persistent objects loaded in the session bean to and from the servlet/JSP layer. Use a new session to service each request. Use <literal>Session.merge()</literal> or <literal>Session.saveOrUpdate()</literal> to synchronize objects with the database."
msgstr ""
#. Tag: term
-#: best_practices.xml:156
#, no-c-format
msgid "In a two tiered architecture, consider using long persistence contexts:"
msgstr ""
#. Tag: para
-#: best_practices.xml:158
#, no-c-format
msgid "Database Transactions have to be as short as possible for best scalability. However, it is often necessary to implement long running <emphasis>application transactions</emphasis>, a single unit-of-work from the point of view of a user. An application transaction might span several client request/response cycles. It is common to use detached objects to implement application transactions. An appropriate alternative in a two tiered architecture, is to maintain a single open persistence contact session for the whole life cycle of the application transaction. Then simply disconnect from the JDBC connection at the end of each request and reconnect at the beginning of the subsequent request. Never share a single session across more than one application transaction or you will be working with stale data."
msgstr ""
#. Tag: term
-#: best_practices.xml:172
#, no-c-format
msgid "Do not treat exceptions as recoverable:"
msgstr ""
#. Tag: para
-#: best_practices.xml:174
#, no-c-format
msgid "This is more of a necessary practice than a \"best\" practice. When an exception occurs, roll back the <literal>Transaction</literal> and close the <literal>Session</literal>. If you do not do this, Hibernate cannot guarantee that in-memory state accurately represents the persistent state. For example, do not use <literal>Session.load()</literal> to determine if an instance with the given identifier exists on the database; use <literal>Session.get()</literal> or a query instead."
msgstr ""
#. Tag: term
-#: best_practices.xml:184
#, no-c-format
msgid "Prefer lazy fetching for associations:"
msgstr ""
#. Tag: para
-#: best_practices.xml:186
#, no-c-format
msgid "Use eager fetching sparingly. Use proxies and lazy collections for most associations to classes that are not likely to be completely held in the second-level cache. For associations to cached classes, where there is an a extremely high probability of a cache hit, explicitly disable eager fetching using <literal>lazy=\"false\"</literal>. When join fetching is appropriate to a particular use case, use a query with a <literal>left join fetch</literal>."
msgstr ""
#. Tag: term
-#: best_practices.xml:196
#, no-c-format
msgid "Use the <emphasis>open session in view</emphasis> pattern, or a disciplined <emphasis>assembly phase</emphasis> to avoid problems with unfetched data:"
msgstr ""
#. Tag: para
-#: best_practices.xml:201
#, no-c-format
msgid "Hibernate frees the developer from writing tedious <emphasis>Data Transfer Objects</emphasis> (DTO). In a traditional EJB architecture, DTOs serve dual purposes: first, they work around the problem that entity beans are not serializable; second, they implicitly define an assembly phase where all data to be used by the view is fetched and marshalled into the DTOs before returning control to the presentation tier. Hibernate eliminates the first purpose. Unless you are prepared to hold the persistence context (the session) open across the view rendering process, you will still need an assembly phase. Think of your business methods as having a strict contract with the presentation tier about what data is available in the detached objects. This is not a limitation of Hibernate. It is a fundamental requirement of safe transactional data access."
msgstr ""
#. Tag: term
-#: best_practices.xml:215
#, no-c-format
msgid "Consider abstracting your business logic from Hibernate:"
msgstr ""
#. Tag: para
-#: best_practices.xml:217
#, no-c-format
msgid "Hide Hibernate data-access code behind an interface. Combine the <emphasis>DAO</emphasis> and <emphasis>Thread Local Session</emphasis> patterns. You can even have some classes persisted by handcoded JDBC associated to Hibernate via a <literal>UserType</literal>. This advice is, however, intended for \"sufficiently large\" applications. It is not appropriate for an application with five tables."
msgstr ""
#. Tag: term
-#: best_practices.xml:227
#, no-c-format
msgid "Do not use exotic association mappings:"
msgstr ""
#. Tag: para
-#: best_practices.xml:229
#, no-c-format
msgid "Practical test cases for real many-to-many associations are rare. Most of the time you need additional information stored in the \"link table\". In this case, it is much better to use two one-to-many associations to an intermediate link class. In fact, most associations are one-to-many and many-to-one. For this reason, you should proceed cautiously when using any other association style."
msgstr ""
#. Tag: term
-#: best_practices.xml:239
#, no-c-format
msgid "Prefer bidirectional associations:"
msgstr ""
#. Tag: para
-#: best_practices.xml:241
#, no-c-format
msgid "Unidirectional associations are more difficult to query. In a large application, almost all associations must be navigable in both directions in queries."
msgstr ""
Deleted: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/bibliography.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/bibliography.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/bibliography.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,70 +0,0 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
-#
-#, fuzzy
-msgid ""
-msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-10 21:02+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#: bibliography.xml:27
-#, no-c-format
-msgid "References"
-msgstr ""
-
-#. Tag: title
-#: bibliography.xml:31
-#, no-c-format
-msgid "Patterns of Enterprise Application Architecture"
-msgstr ""
-
-#. Tag: author
-#: bibliography.xml:34
-#, no-c-format
-msgid "<firstname>Martin</firstname> <surname>Fowler</surname>"
-msgstr ""
-
-#. Tag: holder
-#: bibliography.xml:41
-#, no-c-format
-msgid "Pearson Education, Inc."
-msgstr ""
-
-#. Tag: title
-#: bibliography.xml:50
-#, no-c-format
-msgid "Java Persistence with Hibernate"
-msgstr ""
-
-#. Tag: subtitle
-#: bibliography.xml:51
-#, no-c-format
-msgid "Second Edition of Hibernate in Action"
-msgstr ""
-
-#. Tag: author
-#: bibliography.xml:57
-#, no-c-format
-msgid "<firstname>Christian</firstname> <surname>Bauer</surname>"
-msgstr ""
-
-#. Tag: author
-#: bibliography.xml:61
-#, no-c-format
-msgid "<firstname>Gavin</firstname> <surname>King</surname>"
-msgstr ""
-
-#. Tag: holder
-#: bibliography.xml:68
-#, no-c-format
-msgid "Manning Publications Co."
-msgstr ""
-
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/collection_mapping.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/collection_mapping.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/collection_mapping.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,1210 +1,623 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-10 21:02+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:18\n"
+"PO-Revision-Date: 2010-01-08T04:07:18\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
-#: collection_mapping.xml:29
#, no-c-format
msgid "Collection mapping"
msgstr ""
#. Tag: title
-#: collection_mapping.xml:32
#, no-c-format
msgid "Persistent collections"
msgstr ""
#. Tag: para
-#: collection_mapping.xml:34
#, no-c-format
msgid "Hibernate requires that persistent collection-valued fields be declared as an interface type. For example:"
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:39
-#, no-c-format
-msgid ""
- "<![CDATA[public class Product {\n"
- " private String serialNumber;\n"
- " private Set parts = new HashSet();\n"
- " \n"
- " public Set getParts() { return parts; }\n"
- " void setParts(Set parts) { this.parts = parts; }\n"
- " public String getSerialNumber() { return serialNumber; }\n"
- " void setSerialNumber(String sn) { serialNumber = sn; }\n"
- "}]]>"
-msgstr ""
-
#. Tag: para
-#: collection_mapping.xml:41
#, no-c-format
msgid "The actual interface might be <literal>java.util.Set</literal>, <literal>java.util.Collection</literal>, <literal>java.util.List</literal>, <literal>java.util.Map</literal>, <literal>java.util.SortedSet</literal>, <literal>java.util.SortedMap</literal> or anything you like (\"anything you like\" means you will have to write an implementation of <literal>org.hibernate.usertype.UserCollectionType</literal>.)"
msgstr ""
#. Tag: para
-#: collection_mapping.xml:50
#, no-c-format
msgid "Notice how the instance variable was initialized with an instance of <literal>HashSet</literal>. This is the best way to initialize collection valued properties of newly instantiated (non-persistent) instances. When you make the instance persistent, by calling <literal>persist()</literal> for example, Hibernate will actually replace the <literal>HashSet</literal> with an instance of Hibernate's own implementation of <literal>Set</literal>. Be aware of the following errors:"
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:60
-#, no-c-format
-msgid ""
- "<![CDATA[Cat cat = new DomesticCat();\n"
- "Cat kitten = new DomesticCat();\n"
- "....\n"
- "Set kittens = new HashSet();\n"
- "kittens.add(kitten);\n"
- "cat.setKittens(kittens);\n"
- "session.persist(cat);\n"
- "kittens = cat.getKittens(); // Okay, kittens collection is a Set\n"
- "(HashSet) cat.getKittens(); // Error!]]>"
-msgstr ""
-
#. Tag: para
-#: collection_mapping.xml:62
#, no-c-format
msgid "The persistent collections injected by Hibernate behave like <literal>HashMap</literal>, <literal>HashSet</literal>, <literal>TreeMap</literal>, <literal>TreeSet</literal> or <literal>ArrayList</literal>, depending on the interface type."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:69
#, no-c-format
msgid "Collections instances have the usual behavior of value types. They are automatically persisted when referenced by a persistent object and are automatically deleted when unreferenced. If a collection is passed from one persistent object to another, its elements might be moved from one table to another. Two entities cannot share a reference to the same collection instance. Due to the underlying relational model, collection-valued properties do not support null value semantics. Hibernate does not distinguish between a null collection reference and an empty collection."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:80
#, no-c-format
msgid "Use persistent collections the same way you use ordinary Java collections. However, please ensure you understand the semantics of bidirectional associations (these are discussed later)."
msgstr ""
#. Tag: title
-#: collection_mapping.xml:89
#, no-c-format
msgid "Collection mappings"
msgstr ""
#. Tag: para
-#: collection_mapping.xml:92
#, no-c-format
msgid "There are quite a range of mappings that can be generated for collections that cover many common relational models. We suggest you experiment with the schema generation tool so that you understand how various mapping declarations translate to database tables."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:99
#, no-c-format
msgid "The Hibernate mapping element used for mapping a collection depends upon the type of interface. For example, a <literal><set></literal> element is used for mapping properties of type <literal>Set</literal>."
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:105
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Product\">\n"
- " <id name=\"serialNumber\" column=\"productSerialNumber\"/>\n"
- " <set name=\"parts\">\n"
- " <key column=\"productSerialNumber\" not-null=\"true\"/>\n"
- " <one-to-many class=\"Part\"/>\n"
- " </set>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: collection_mapping.xml:107
#, no-c-format
msgid "Apart from <literal><set></literal>, there is also <literal><list></literal>, <literal><map></literal>, <literal><bag></literal>, <literal><array></literal> and <literal><primitive-array></literal> mapping elements. The <literal><map></literal> element is representative:"
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:132
-#, no-c-format
-msgid ""
- "<![CDATA[<map\n"
- " name=\"propertyName\"\n"
- " table=\"table_name\"\n"
- " schema=\"schema_name\"\n"
- " lazy=\"true|extra|false\"\n"
- " inverse=\"true|false\"\n"
- " cascade=\"all|none|save-update|delete|all-delete-orphan|delete-orphan\"\n"
- " sort=\"unsorted|natural|comparatorClass\"\n"
- " order-by=\"column_name asc|desc\"\n"
- " where=\"arbitrary sql where condition\"\n"
- " fetch=\"join|select|subselect\"\n"
- " batch-size=\"N\"\n"
- " access=\"field|property|ClassName\"\n"
- " optimistic-lock=\"true|false\"\n"
- " mutable=\"true|false\"\n"
- " node=\"element-name|.\"\n"
- " embed-xml=\"true|false\"\n"
- ">\n"
- "\n"
- " <key .... />\n"
- " <map-key .... />\n"
- " <element .... />\n"
- "</map>]]>"
-msgstr ""
-
#. Tag: para
-#: collection_mapping.xml:135
#, no-c-format
msgid "<literal>name</literal>: the collection property name"
msgstr ""
#. Tag: para
-#: collection_mapping.xml:140
#, no-c-format
msgid "<literal>table</literal> (optional - defaults to property name): the name of the collection table. It is not used for one-to-many associations."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:146
#, no-c-format
msgid "<literal>schema</literal> (optional): the name of a table schema to override the schema declared on the root element"
msgstr ""
#. Tag: para
-#: collection_mapping.xml:152
#, no-c-format
msgid "<literal>lazy</literal> (optional - defaults to <literal>true</literal>): disables lazy fetching and specifies that the association is always eagerly fetched. It can also be used to enable \"extra-lazy\" fetching where most operations do not initialize the collection. This is suitable for large collections."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:161
#, no-c-format
msgid "<literal>inverse</literal> (optional - defaults to <literal>false</literal>): marks this collection as the \"inverse\" end of a bidirectional association."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:167
#, no-c-format
msgid "<literal>cascade</literal> (optional - defaults to <literal>none</literal>): enables operations to cascade to child entities."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:173
#, no-c-format
msgid "<literal>sort</literal> (optional): specifies a sorted collection with <literal>natural</literal> sort order or a given comparator class."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:179
#, no-c-format
msgid "<literal>order-by</literal> (optional, JDK1.4 only): specifies a table column or columns that define the iteration order of the <literal>Map</literal>, <literal>Set</literal> or bag, together with an optional <literal>asc</literal> or <literal>desc</literal>."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:186
#, no-c-format
msgid "<literal>where</literal> (optional): specifies an arbitrary SQL <literal>WHERE</literal> condition that is used when retrieving or removing the collection. This is useful if the collection needs to contain only a subset of the available data."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:193
#, no-c-format
msgid "<literal>fetch</literal> (optional, defaults to <literal>select</literal>): chooses between outer-join fetching, fetching by sequential select, and fetching by sequential subselect."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:200
#, no-c-format
msgid "<literal>batch-size</literal> (optional, defaults to <literal>1</literal>): specifies a \"batch size\" for lazily fetching instances of this collection."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:206
#, no-c-format
msgid "<literal>access</literal> (optional - defaults to <literal>property</literal>): the strategy Hibernate uses for accessing the collection property value."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:212
#, no-c-format
msgid "<literal>optimistic-lock</literal> (optional - defaults to <literal>true</literal>): specifies that changes to the state of the collection results in increments of the owning entity's version. For one-to-many associations you may want to disable this setting."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:220
#, no-c-format
msgid "<literal>mutable</literal> (optional - defaults to <literal>true</literal>): a value of <literal>false</literal> specifies that the elements of the collection never change. This allows for minor performance optimization in some cases."
msgstr ""
#. Tag: title
-#: collection_mapping.xml:230
#, no-c-format
msgid "Collection foreign keys"
msgstr ""
#. Tag: para
-#: collection_mapping.xml:232
#, no-c-format
msgid "Collection instances are distinguished in the database by the foreign key of the entity that owns the collection. This foreign key is referred to as the <emphasis>collection key column</emphasis>, or columns, of the collection table. The collection key column is mapped by the <literal><key></literal> element."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:240
#, no-c-format
msgid "There can be a nullability constraint on the foreign key column. For most collections, this is implied. For unidirectional one-to-many associations, the foreign key column is nullable by default, so you may need to specify <literal>not-null=\"true\"</literal>."
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:247
-#, no-c-format
-msgid "<![CDATA[<key column=\"productSerialNumber\" not-null=\"true\"/>]]>"
-msgstr ""
-
#. Tag: para
-#: collection_mapping.xml:249
#, no-c-format
msgid "The foreign key constraint can use <literal>ON DELETE CASCADE</literal>."
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:253
-#, no-c-format
-msgid "<![CDATA[<key column=\"productSerialNumber\" on-delete=\"cascade\"/>]]>"
-msgstr ""
-
#. Tag: para
-#: collection_mapping.xml:255
#, no-c-format
msgid "See the previous chapter for a full definition of the <literal><key></literal> element."
msgstr ""
#. Tag: title
-#: collection_mapping.xml:263
#, no-c-format
msgid "Collection elements"
msgstr ""
#. Tag: para
-#: collection_mapping.xml:265
#, no-c-format
msgid "Collections can contain almost any other Hibernate type, including: basic types, custom types, components and references to other entities. This is an important distinction. An object in a collection might be handled with \"value\" semantics (its life cycle fully depends on the collection owner), or it might be a reference to another entity with its own life cycle. In the latter case, only the \"link\" between the two objects is considered to be a state held by the collection."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:274
#, no-c-format
msgid "The contained type is referred to as the <emphasis>collection element type</emphasis>. Collection elements are mapped by <literal><element></literal> or <literal><composite-element></literal>, or in the case of entity references, with <literal><one-to-many></literal> or <literal><many-to-many></literal>. The first two map elements with value semantics, the next two are used to map entity associations."
msgstr ""
#. Tag: title
-#: collection_mapping.xml:286
#, no-c-format
msgid "Indexed collections"
msgstr ""
#. Tag: para
-#: collection_mapping.xml:288
#, no-c-format
msgid "All collection mappings, except those with set and bag semantics, need an <emphasis>index column</emphasis> in the collection table. An index column is a column that maps to an array index, or <literal>List</literal> index, or <literal>Map</literal> key. The index of a <literal>Map</literal> may be of any basic type, mapped with <literal><map-key></literal>. It can be an entity reference mapped with <literal><map-key-many-to-many></literal>, or it can be a composite type mapped with <literal><composite-map-key></literal>. The index of an array or list is always of type <literal>integer</literal> and is mapped using the <literal><list-index></literal> element. The mapped column contains sequential integers that are numbered from zero by default."
msgstr ""
-#. Tag: sect2
-#: collection_mapping.xml:299
+#. Tag: para
#, no-c-format
-msgid ""
- "<programlistingco> <areaspec> <area id=\"index1\" coords=\"2 45\"/> <area id=\"index2\" coords=\"3 45\"/> </areaspec> <programlisting><![CDATA[<list-index \n"
- " column=\"column_name\"\n"
- " base=\"0|1|...\"/>]]></programlisting> <calloutlist> <callout arearefs=\"index1\"> <para> <literal>column_name</literal> (required): the name of the column holding the collection index values. </para> </callout> <callout arearefs=\"index1\"> <para> <literal>base</literal> (optional - defaults to <literal>0</literal>): the value of the index column that corresponds to the first element of the list or array. </para> </callout> </calloutlist> </programlistingco> <programlistingco> <areaspec> <area id=\"mapkey1\" coords=\"2 45\"/> <area id=\"mapkey2\" coords=\"3 45\"/> <area id=\"mapkey3\" coords=\"4 45\"/> </areaspec> <programlisting><![CDATA[<map-key \n"
- " column=\"column_name\"\n"
- " formula=\"any SQL expression\"\n"
- " type=\"type_name\"\n"
- " node=\"@attribute-name\"\n"
- " length=\"N\"/>]]></programlisting> <calloutlist> <callout arearefs=\"mapkey1\"> <para> <literal>column</literal> (optional): the name of the column holding the collection index values. </para> </callout> <callout arearefs=\"mapkey2\"> <para> <literal>formula</literal> (optional): a SQL formula used to evaluate the key of the map. </para> </callout> <callout arearefs=\"mapkey3\"> <para> <literal>type</literal> (required): the type of the map keys. </para> </callout> </calloutlist> </programlistingco> <programlistingco> <areaspec> <area id=\"indexmanytomany1\" coords=\"2 45\"/> <area id=\"indexmanytomany2\" coords=\"3 45\"/> <area id=\"indexmanytomany3\" coords=\"3 45\"/> </areaspec> <programlisting><![CDATA[<map-key-many-to-many\n"
- " column=\"column_name\"\n"
- " formula=\"any SQL expression\"\n"
- " class=\"ClassName\"\n"
- "/>]]></programlisting> <calloutlist> <callout arearefs=\"indexmanytomany1\"> <para> <literal>column</literal> (optional): the name of the foreign key column for the collection index values. </para> </callout> <callout arearefs=\"indexmanytomany2\"> <para> <literal>formula</literal> (optional): a SQ formula used to evaluate the foreign key of the map key. </para> </callout> <callout arearefs=\"indexmanytomany3\"> <para> <literal>class</literal> (required): the entity class used as the map key. </para> </callout> </calloutlist> </programlistingco>"
+msgid "<literal>column_name</literal> (required): the name of the column holding the collection index values."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:380
#, no-c-format
+msgid "<literal>base</literal> (optional - defaults to <literal>0</literal>): the value of the index column that corresponds to the first element of the list or array."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>column</literal> (optional): the name of the column holding the collection index values."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>formula</literal> (optional): a SQL formula used to evaluate the key of the map."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>type</literal> (required): the type of the map keys."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>column</literal> (optional): the name of the foreign key column for the collection index values."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>formula</literal> (optional): a SQ formula used to evaluate the foreign key of the map key."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>class</literal> (required): the entity class used as the map key."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
msgid "If your table does not have an index column, and you still wish to use <literal>List</literal> as the property type, you can map the property as a Hibernate <emphasis><bag></emphasis>. A bag does not retain its order when it is retrieved from the database, but it can be optionally sorted or ordered."
msgstr ""
#. Tag: title
-#: collection_mapping.xml:390
#, no-c-format
msgid "Collections of values and many-to-many associations"
msgstr ""
#. Tag: para
-#: collection_mapping.xml:392
#, no-c-format
msgid "Any collection of values or many-to-many associations requires a dedicated <emphasis>collection table</emphasis> with a foreign key column or columns, <emphasis>collection element column</emphasis> or columns, and possibly an index column or columns."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:399
#, no-c-format
msgid "For a collection of values use the <literal><element></literal> tag. For example:"
msgstr ""
-#. Tag: sect2
-#: collection_mapping.xml:401
+#. Tag: para
#, no-c-format
-msgid ""
- "<programlistingco> <areaspec> <area id=\"element1b\" coords=\"2 50\"/> <area id=\"element2b\" coords=\"3 50\"/> <area id=\"element3b\" coords=\"4 50\"/> </areaspec> <programlisting><![CDATA[<element\n"
- " column=\"column_name\"\n"
- " formula=\"any SQL expression\"\n"
- " type=\"typename\"\n"
- " length=\"L\"\n"
- " precision=\"P\"\n"
- " scale=\"S\"\n"
- " not-null=\"true|false\"\n"
- " unique=\"true|false\"\n"
- " node=\"element-name\"\n"
- "/>]]></programlisting> <calloutlist> <callout arearefs=\"element1b\"> <para> <literal>column</literal> (optional): the name of the column holding the collection element values. </para> </callout> <callout arearefs=\"element2b\"> <para> <literal>formula</literal> (optional): an SQL formula used to evaluate the element. </para> </callout> <callout arearefs=\"element3b\"> <para> <literal>type</literal> (required): the type of the collection element. </para> </callout> </calloutlist> </programlistingco> <para> A <emphasis>many-to-many association</emphasis> is specified using the <literal><many-to-many></literal> element. </para> <programlistingco> <areaspec> <area id=\"manytomany1\" coords=\"2 60\"/> <area id=\"manytomany2\" coords=\"3 60\"/> <area id=\"manytomany3\" coords=\"4 60\"/> <area id=\"manytomany4\" coords=\"5 60\"/> <area id=\"manytomany5\" coords=\"6 60\"/> <area id=\"manytomany6\" coords=\"7 60\"/> <area id=\"manytomany7\" coords=\"8 60\"/> <area id=\!
"manytomany8\" coords=\"9 60\"/> </areaspec> <programlisting><![CDATA[<many-to-many\n"
- " column=\"column_name\"\n"
- " formula=\"any SQL expression\"\n"
- " class=\"ClassName\"\n"
- " fetch=\"select|join\"\n"
- " unique=\"true|false\"\n"
- " not-found=\"ignore|exception\"\n"
- " entity-name=\"EntityName\"\n"
- " property-ref=\"propertyNameFromAssociatedClass\"\n"
- " node=\"element-name\"\n"
- " embed-xml=\"true|false\"\n"
- " />]]></programlisting> <calloutlist> <callout arearefs=\"manytomany1\"> <para> <literal>column</literal> (optional): the name of the element foreign key column. </para> </callout> <callout arearefs=\"manytomany2\"> <para> <literal>formula</literal> (optional): an SQL formula used to evaluate the element foreign key value. </para> </callout> <callout arearefs=\"manytomany3\"> <para> <literal>class</literal> (required): the name of the associated class. </para> </callout> <callout arearefs=\"manytomany4\"> <para> <literal>fetch</literal> (optional - defaults to <literal>join</literal>): enables outer-join or sequential select fetching for this association. This is a special case; for full eager fetching in a single <literal>SELECT</literal> of an entity and its many-to-many relationships to other entities, you would enable <literal>join</literal> fetching,not only of the collection itself, but also with this attribute on the <literal><many-to-many></literal> !
nested element. </para> </callout> <callout arearefs=\"manytomany5\"> <para> <literal>unique</literal> (optional): enables the DDL generation of a unique constraint for the foreign-key column. This makes the association multiplicity effectively one-to-many. </para> </callout> <callout arearefs=\"manytomany6\"> <para> <literal>not-found</literal> (optional - defaults to <literal>exception</literal>): specifies how foreign keys that reference missing rows will be handled: <literal>ignore</literal> will treat a missing row as a null association. </para> </callout> <callout arearefs=\"manytomany7\"> <para> <literal>entity-name</literal> (optional): the entity name of the associated class, as an alternative to <literal>class</literal>. </para> </callout> <callout arearefs=\"manytomany8\"> <para> <literal>property-ref</literal> (optional): the name of a property of the associated class that is joined to this foreign key. If not specified, the primary key of the associated class i!
s used. </para> </callout> </calloutlist> </programlistingco>"
+msgid "<literal>column</literal> (optional): the name of the column holding the collection element values."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:506
#, no-c-format
-msgid "Here are some examples."
+msgid "<literal>formula</literal> (optional): an SQL formula used to evaluate the element."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:509
#, no-c-format
-msgid "A set of strings:"
+msgid "<literal>type</literal> (required): the type of the collection element."
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:513
+#. Tag: para
#, no-c-format
-msgid ""
- "<![CDATA[<set name=\"names\" table=\"person_names\">\n"
- " <key column=\"person_id\"/>\n"
- " <element column=\"person_name\" type=\"string\"/>\n"
- "</set>]]>"
+msgid "A <emphasis>many-to-many association</emphasis> is specified using the <literal><many-to-many></literal> element."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:515
#, no-c-format
-msgid "A bag containing integers with an iteration order determined by the <literal>order-by</literal> attribute:"
+msgid "<literal>column</literal> (optional): the name of the element foreign key column."
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:520
+#. Tag: para
#, no-c-format
-msgid ""
- "<![CDATA[<bag name=\"sizes\" \n"
- " table=\"item_sizes\" \n"
- " order-by=\"size asc\">\n"
- " <key column=\"item_id\"/>\n"
- " <element column=\"size\" type=\"integer\"/>\n"
- "</bag>]]>"
+msgid "<literal>formula</literal> (optional): an SQL formula used to evaluate the element foreign key value."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:522
#, no-c-format
-msgid "An array of entities, in this case, a many-to-many association:"
+msgid "<literal>class</literal> (required): the name of the associated class."
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:526
+#. Tag: para
#, no-c-format
-msgid ""
- "<![CDATA[<array name=\"addresses\" \n"
- " table=\"PersonAddress\" \n"
- " cascade=\"persist\">\n"
- " <key column=\"personId\"/>\n"
- " <list-index column=\"sortOrder\"/>\n"
- " <many-to-many column=\"addressId\" class=\"Address\"/>\n"
- "</array>]]>"
+msgid "<literal>fetch</literal> (optional - defaults to <literal>join</literal>): enables outer-join or sequential select fetching for this association. This is a special case; for full eager fetching in a single <literal>SELECT</literal> of an entity and its many-to-many relationships to other entities, you would enable <literal>join</literal> fetching,not only of the collection itself, but also with this attribute on the <literal><many-to-many></literal> nested element."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:528
#, no-c-format
-msgid "A map from string indices to dates:"
+msgid "<literal>unique</literal> (optional): enables the DDL generation of a unique constraint for the foreign-key column. This makes the association multiplicity effectively one-to-many."
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:532
+#. Tag: para
#, no-c-format
-msgid ""
- "<![CDATA[<map name=\"holidays\" \n"
- " table=\"holidays\" \n"
- " schema=\"dbo\" \n"
- " order-by=\"hol_name asc\">\n"
- " <key column=\"id\"/>\n"
- " <map-key column=\"hol_name\" type=\"string\"/>\n"
- " <element column=\"hol_date\" type=\"date\"/>\n"
- "</map>]]>"
+msgid "<literal>not-found</literal> (optional - defaults to <literal>exception</literal>): specifies how foreign keys that reference missing rows will be handled: <literal>ignore</literal> will treat a missing row as a null association."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:534
#, no-c-format
-msgid "A list of components (this is discussed in the next chapter):"
+msgid "<literal>entity-name</literal> (optional): the entity name of the associated class, as an alternative to <literal>class</literal>."
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:538
+#. Tag: para
#, no-c-format
-msgid ""
- "<![CDATA[<list name=\"carComponents\" \n"
- " table=\"CarComponents\">\n"
- " <key column=\"carId\"/>\n"
- " <list-index column=\"sortOrder\"/>\n"
- " <composite-element class=\"CarComponent\">\n"
- " <property name=\"price\"/>\n"
- " <property name=\"type\"/>\n"
- " <property name=\"serialNumber\" column=\"serialNum\"/>\n"
- " </composite-element>\n"
- "</list>]]>"
+msgid "<literal>property-ref</literal> (optional): the name of a property of the associated class that is joined to this foreign key. If not specified, the primary key of the associated class is used."
msgstr ""
-#. Tag: title
-#: collection_mapping.xml:543
+#. Tag: para
#, no-c-format
-msgid "One-to-many associations"
+msgid "Here are some examples."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:545
#, no-c-format
-msgid "A <emphasis>one-to-many association</emphasis> links the tables of two classes via a foreign key with no intervening collection table. This mapping loses certain semantics of normal Java collections:"
+msgid "A set of strings:"
msgstr ""
#. Tag: para
-#: collection_mapping.xml:553
#, no-c-format
-msgid "An instance of the contained entity class cannot belong to more than one instance of the collection."
+msgid "A bag containing integers with an iteration order determined by the <literal>order-by</literal> attribute:"
msgstr ""
#. Tag: para
-#: collection_mapping.xml:559
#, no-c-format
-msgid "An instance of the contained entity class cannot appear at more than one value of the collection index."
+msgid "An array of entities, in this case, a many-to-many association:"
msgstr ""
#. Tag: para
-#: collection_mapping.xml:566
#, no-c-format
-msgid "An association from <literal>Product</literal> to <literal>Part</literal> requires the existence of a foreign key column and possibly an index column to the <literal>Part</literal> table. A <literal><one-to-many></literal> tag indicates that this is a one-to-many association."
+msgid "A map from string indices to dates:"
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:579
+#. Tag: para
#, no-c-format
-msgid ""
- "<![CDATA[<one-to-many \n"
- " class=\"ClassName\"\n"
- " not-found=\"ignore|exception\"\n"
- " entity-name=\"EntityName\"\n"
- " node=\"element-name\"\n"
- " embed-xml=\"true|false\"\n"
- " />]]>"
+msgid "A list of components (this is discussed in the next chapter):"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "One-to-many associations"
+msgstr ""
+
#. Tag: para
-#: collection_mapping.xml:582
#, no-c-format
-msgid "<literal>class</literal> (required): the name of the associated class."
+msgid "A <emphasis>one-to-many association</emphasis> links the tables of two classes via a foreign key with no intervening collection table. This mapping loses certain semantics of normal Java collections:"
msgstr ""
#. Tag: para
-#: collection_mapping.xml:587
#, no-c-format
-msgid "<literal>not-found</literal> (optional - defaults to <literal>exception</literal>): specifies how cached identifiers that reference missing rows will be handled. <literal>ignore</literal> will treat a missing row as a null association."
+msgid "An instance of the contained entity class cannot belong to more than one instance of the collection."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:594
#, no-c-format
-msgid "<literal>entity-name</literal> (optional): the entity name of the associated class, as an alternative to <literal>class</literal>."
+msgid "An instance of the contained entity class cannot appear at more than one value of the collection index."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:602
#, no-c-format
-msgid "The <literal><one-to-many></literal> element does not need to declare any columns. Nor is it necessary to specify the <literal>table</literal> name anywhere."
+msgid "An association from <literal>Product</literal> to <literal>Part</literal> requires the existence of a foreign key column and possibly an index column to the <literal>Part</literal> table. A <literal><one-to-many></literal> tag indicates that this is a one-to-many association."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:609
#, no-c-format
-msgid "If the foreign key column of a <literal><one-to-many></literal> association is declared <literal>NOT NULL</literal>, you must declare the <literal><key></literal> mapping <literal>not-null=\"true\"</literal> or <emphasis>use a bidirectional association</emphasis> with the collection mapping marked <literal>inverse=\"true\"</literal>. See the discussion of bidirectional associations later in this chapter for more information."
+msgid "<literal>not-found</literal> (optional - defaults to <literal>exception</literal>): specifies how cached identifiers that reference missing rows will be handled. <literal>ignore</literal> will treat a missing row as a null association."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:619
#, no-c-format
-msgid "The following example shows a map of <literal>Part</literal> entities by name, where <literal>partName</literal> is a persistent property of <literal>Part</literal>. Notice the use of a formula-based index:"
+msgid "The <literal><one-to-many></literal> element does not need to declare any columns. Nor is it necessary to specify the <literal>table</literal> name anywhere."
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:625
+#. Tag: para
#, no-c-format
-msgid ""
- "<![CDATA[<map name=\"parts\"\n"
- " cascade=\"all\">\n"
- " <key column=\"productId\" not-null=\"true\"/>\n"
- " <map-key formula=\"partName\"/>\n"
- " <one-to-many class=\"Part\"/>\n"
- "</map>]]>"
+msgid "If the foreign key column of a <literal><one-to-many></literal> association is declared <literal>NOT NULL</literal>, you must declare the <literal><key></literal> mapping <literal>not-null=\"true\"</literal> or <emphasis>use a bidirectional association</emphasis> with the collection mapping marked <literal>inverse=\"true\"</literal>. See the discussion of bidirectional associations later in this chapter for more information."
msgstr ""
+#. Tag: para
+#, no-c-format
+msgid "The following example shows a map of <literal>Part</literal> entities by name, where <literal>partName</literal> is a persistent property of <literal>Part</literal>. Notice the use of a formula-based index:"
+msgstr ""
+
#. Tag: title
-#: collection_mapping.xml:631
#, no-c-format
msgid "Advanced collection mappings"
msgstr ""
#. Tag: title
-#: collection_mapping.xml:634
#, no-c-format
msgid "Sorted collections"
msgstr ""
#. Tag: para
-#: collection_mapping.xml:636
#, no-c-format
msgid "Hibernate supports collections implementing <literal>java.util.SortedMap</literal> and <literal>java.util.SortedSet</literal>. You must specify a comparator in the mapping file:"
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:641
-#, no-c-format
-msgid ""
- "<![CDATA[<set name=\"aliases\" \n"
- " table=\"person_aliases\" \n"
- " sort=\"natural\">\n"
- " <key column=\"person\"/>\n"
- " <element column=\"name\" type=\"string\"/>\n"
- "</set>\n"
- "\n"
- "<map name=\"holidays\" sort=\"my.custom.HolidayComparator\">\n"
- " <key column=\"year_id\"/>\n"
- " <map-key column=\"hol_name\" type=\"string\"/>\n"
- " <element column=\"hol_date\" type=\"date\"/>\n"
- "</map>]]>"
-msgstr ""
-
#. Tag: para
-#: collection_mapping.xml:643
#, no-c-format
msgid "Allowed values of the <literal>sort</literal> attribute are <literal>unsorted</literal>, <literal>natural</literal> and the name of a class implementing <literal>java.util.Comparator</literal>."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:649
#, no-c-format
msgid "Sorted collections actually behave like <literal>java.util.TreeSet</literal> or <literal>java.util.TreeMap</literal>."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:654
#, no-c-format
msgid "If you want the database itself to order the collection elements, use the <literal>order-by</literal> attribute of <literal>set</literal>, <literal>bag</literal> or <literal>map</literal> mappings. This solution is only available under JDK 1.4 or higher and is implemented using <literal>LinkedHashSet</literal> or <literal>LinkedHashMap</literal>. This performs the ordering in the SQL query and not in the memory."
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:663
-#, no-c-format
-msgid ""
- "<![CDATA[<set name=\"aliases\" table=\"person_aliases\" order-by=\"lower(name) asc\">\n"
- " <key column=\"person\"/>\n"
- " <element column=\"name\" type=\"string\"/>\n"
- "</set>\n"
- "\n"
- "<map name=\"holidays\" order-by=\"hol_date, hol_name\">\n"
- " <key column=\"year_id\"/>\n"
- " <map-key column=\"hol_name\" type=\"string\"/>\n"
- " <element column=\"hol_date type=\"date\"/>\n"
- "</map>]]>"
-msgstr ""
-
#. Tag: title
-#: collection_mapping.xml:666
#, no-c-format
msgid "Note"
msgstr ""
#. Tag: para
-#: collection_mapping.xml:667
#, no-c-format
msgid "The value of the <literal>order-by</literal> attribute is an SQL ordering, not an HQL ordering."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:673
#, no-c-format
msgid "Associations can even be sorted by arbitrary criteria at runtime using a collection <literal>filter()</literal>:"
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:678
-#, no-c-format
-msgid "<![CDATA[sortedUsers = s.createFilter( group.getUsers(), \"order by this.name\" ).list();]]>"
-msgstr ""
-
#. Tag: title
-#: collection_mapping.xml:683
#, no-c-format
msgid "Bidirectional associations"
msgstr ""
#. Tag: para
-#: collection_mapping.xml:685
#, no-c-format
msgid "A <emphasis>bidirectional association</emphasis> allows navigation from both \"ends\" of the association. Two kinds of bidirectional association are supported:"
msgstr ""
#. Tag: term
-#: collection_mapping.xml:692
#, no-c-format
msgid "one-to-many"
msgstr ""
#. Tag: para
-#: collection_mapping.xml:694
#, no-c-format
msgid "set or bag valued at one end and single-valued at the other"
msgstr ""
#. Tag: term
-#: collection_mapping.xml:700
#, no-c-format
msgid "many-to-many"
msgstr ""
#. Tag: para
-#: collection_mapping.xml:702
#, no-c-format
msgid "set or bag valued at both ends"
msgstr ""
#. Tag: para
-#: collection_mapping.xml:711
#, no-c-format
msgid "You can specify a bidirectional many-to-many association by mapping two many-to-many associations to the same database table and declaring one end as <emphasis>inverse</emphasis>. You cannot select an indexed collection."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:718
#, no-c-format
msgid "Here is an example of a bidirectional many-to-many association that illustrates how each category can have many items and each item can be in many categories:"
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:723
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Category\">\n"
- " <id name=\"id\" column=\"CATEGORY_ID\"/>\n"
- " ...\n"
- " <bag name=\"items\" table=\"CATEGORY_ITEM\">\n"
- " <key column=\"CATEGORY_ID\"/>\n"
- " <many-to-many class=\"Item\" column=\"ITEM_ID\"/>\n"
- " </bag>\n"
- "</class>\n"
- "\n"
- "<class name=\"Item\">\n"
- " <id name=\"id\" column=\"ITEM_ID\"/>\n"
- " ...\n"
- "\n"
- " <!-- inverse end -->\n"
- " <bag name=\"categories\" table=\"CATEGORY_ITEM\" inverse=\"true\">\n"
- " <key column=\"ITEM_ID\"/>\n"
- " <many-to-many class=\"Category\" column=\"CATEGORY_ID\"/>\n"
- " </bag>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: collection_mapping.xml:725
#, no-c-format
msgid "Changes made only to the inverse end of the association are <emphasis>not</emphasis> persisted. This means that Hibernate has two representations in memory for every bidirectional association: one link from A to B and another link from B to A. This is easier to understand if you think about the Java object model and how a many-to-many relationship in Javais created:"
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:733
-#, no-c-format
-msgid ""
- "<![CDATA[\n"
- "category.getItems().add(item); // The category now \"knows\" about the relationship\n"
- "item.getCategories().add(category); // The item now \"knows\" about the relationship\n"
- "\n"
- "session.persist(item); // The relationship won't be saved!\n"
- "session.persist(category); // The relationship will be saved]]>"
-msgstr ""
-
#. Tag: para
-#: collection_mapping.xml:735
#, no-c-format
msgid "The non-inverse side is used to save the in-memory representation to the database."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:739
#, no-c-format
msgid "You can define a bidirectional one-to-many association by mapping a one-to-many association to the same table column(s) as a many-to-one association and declaring the many-valued end <literal>inverse=\"true\"</literal>."
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:745
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Parent\">\n"
- " <id name=\"id\" column=\"parent_id\"/>\n"
- " ....\n"
- " <set name=\"children\" inverse=\"true\">\n"
- " <key column=\"parent_id\"/>\n"
- " <one-to-many class=\"Child\"/>\n"
- " </set>\n"
- "</class>\n"
- "\n"
- "<class name=\"Child\">\n"
- " <id name=\"id\" column=\"child_id\"/>\n"
- " ....\n"
- " <many-to-one name=\"parent\" \n"
- " class=\"Parent\" \n"
- " column=\"parent_id\"\n"
- " not-null=\"true\"/>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: collection_mapping.xml:747
#, no-c-format
msgid "Mapping one end of an association with <literal>inverse=\"true\"</literal> does not affect the operation of cascades as these are orthogonal concepts."
msgstr ""
#. Tag: title
-#: collection_mapping.xml:755
#, no-c-format
msgid "Bidirectional associations with indexed collections"
msgstr ""
#. Tag: para
-#: collection_mapping.xml:756
#, no-c-format
msgid "A bidirectional association where one end is represented as a <literal><list></literal> or <literal><map></literal>, requires special consideration. If there is a property of the child class that maps to the index column you can use <literal>inverse=\"true\"</literal> on the collection mapping:"
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:763
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Parent\">\n"
- " <id name=\"id\" column=\"parent_id\"/>\n"
- " ....\n"
- " <map name=\"children\" inverse=\"true\">\n"
- " <key column=\"parent_id\"/>\n"
- " <map-key column=\"name\" \n"
- " type=\"string\"/>\n"
- " <one-to-many class=\"Child\"/>\n"
- " </map>\n"
- "</class>\n"
- "\n"
- "<class name=\"Child\">\n"
- " <id name=\"id\" column=\"child_id\"/>\n"
- " ....\n"
- " <property name=\"name\" \n"
- " not-null=\"true\"/>\n"
- " <many-to-one name=\"parent\" \n"
- " class=\"Parent\" \n"
- " column=\"parent_id\"\n"
- " not-null=\"true\"/>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: collection_mapping.xml:765
#, no-c-format
msgid "If there is no such property on the child class, the association cannot be considered truly bidirectional. That is, there is information available at one end of the association that is not available at the other end. In this case, you cannot map the collection <literal>inverse=\"true\"</literal>. Instead, you could use the following mapping:"
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:772
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Parent\">\n"
- " <id name=\"id\" column=\"parent_id\"/>\n"
- " ....\n"
- " <map name=\"children\">\n"
- " <key column=\"parent_id\"\n"
- " not-null=\"true\"/>\n"
- " <map-key column=\"name\" \n"
- " type=\"string\"/>\n"
- " <one-to-many class=\"Child\"/>\n"
- " </map>\n"
- "</class>\n"
- "\n"
- "<class name=\"Child\">\n"
- " <id name=\"id\" column=\"child_id\"/>\n"
- " ....\n"
- " <many-to-one name=\"parent\" \n"
- " class=\"Parent\" \n"
- " column=\"parent_id\"\n"
- " insert=\"false\"\n"
- " update=\"false\"\n"
- " not-null=\"true\"/>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: collection_mapping.xml:774
#, no-c-format
-msgid "Note that in this mapping, the collection-valued end of the association is responsible for updates to the foreign key."
+msgid "Note that in this mapping, the collection-valued end of the association is responsible for updates to the foreign key. <!-- TODO: Does this really result in some unnecessary update statements? -->"
msgstr ""
#. Tag: title
-#: collection_mapping.xml:782
#, no-c-format
msgid "Ternary associations"
msgstr ""
#. Tag: para
-#: collection_mapping.xml:784
#, no-c-format
msgid "There are three possible approaches to mapping a ternary association. One approach is to use a <literal>Map</literal> with an association as its index:"
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:789
-#, no-c-format
-msgid ""
- "<![CDATA[<map name=\"contracts\">\n"
- " <key column=\"employer_id\" not-null=\"true\"/>\n"
- " <map-key-many-to-many column=\"employee_id\" class=\"Employee\"/>\n"
- " <one-to-many class=\"Contract\"/>\n"
- "</map>]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: collection_mapping.xml:791
-#, no-c-format
-msgid ""
- "<![CDATA[<map name=\"connections\">\n"
- " <key column=\"incoming_node_id\"/>\n"
- " <map-key-many-to-many column=\"outgoing_node_id\" class=\"Node\"/>\n"
- " <many-to-many column=\"connection_id\" class=\"Connection\"/>\n"
- "</map>]]>"
-msgstr ""
-
#. Tag: para
-#: collection_mapping.xml:793
#, no-c-format
msgid "A second approach is to remodel the association as an entity class. This is the most common approach."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:798
#, no-c-format
msgid "A final alternative is to use composite elements, which will be discussed later."
msgstr ""
-#. Tag: literal
-#: collection_mapping.xml:805
+#. Tag: title
#, no-c-format
-msgid "Using an <idbag>"
+msgid "<literal>Using an <idbag></literal>"
msgstr ""
#. Tag: para
-#: collection_mapping.xml:807
#, no-c-format
msgid "The majority of the many-to-many associations and collections of values shown previously all map to tables with composite keys, even though it has been have suggested that entities should have synthetic identifiers (surrogate keys). A pure association table does not seem to benefit much from a surrogate key, although a collection of composite values <emphasis>might</emphasis>. It is for this reason that Hibernate provides a feature that allows you to map many-to-many associations and collections of values to a table with a surrogate key."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:817
#, no-c-format
msgid "The <literal><idbag></literal> element lets you map a <literal>List</literal> (or <literal>Collection</literal>) with bag semantics. For example:"
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:822
-#, no-c-format
-msgid ""
- "<![CDATA[<idbag name=\"lovers\" table=\"LOVERS\">\n"
- " <collection-id column=\"ID\" type=\"long\">\n"
- " <generator class=\"sequence\"/>\n"
- " </collection-id>\n"
- " <key column=\"PERSON1\"/>\n"
- " <many-to-many column=\"PERSON2\" class=\"Person\" fetch=\"join\"/>\n"
- "</idbag>]]>"
-msgstr ""
-
#. Tag: para
-#: collection_mapping.xml:824
#, no-c-format
msgid "An <literal><idbag></literal> has a synthetic id generator, just like an entity class. A different surrogate key is assigned to each collection row. Hibernate does not, however, provide any mechanism for discovering the surrogate key value of a particular row."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:831
#, no-c-format
msgid "The update performance of an <literal><idbag></literal> supersedes a regular <literal><bag></literal>. Hibernate can locate individual rows efficiently and update or delete them individually, similar to a list, map or set."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:837
#, no-c-format
msgid "In the current implementation, the <literal>native</literal> identifier generation strategy is not supported for <literal><idbag></literal> collection identifiers."
msgstr ""
#. Tag: title
-#: collection_mapping.xml:861
#, no-c-format
msgid "Collection examples"
msgstr ""
#. Tag: para
-#: collection_mapping.xml:863
#, no-c-format
msgid "This section covers collection examples."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:867
#, no-c-format
msgid "The following class has a collection of <literal>Child</literal> instances:"
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:871
-#, no-c-format
-msgid ""
- "<![CDATA[package eg;\n"
- "import java.util.Set;\n"
- "\n"
- "public class Parent {\n"
- " private long id;\n"
- " private Set children;\n"
- "\n"
- " public long getId() { return id; }\n"
- " private void setId(long id) { this.id=id; }\n"
- "\n"
- " private Set getChildren() { return children; }\n"
- " private void setChildren(Set children) { this.children=children; }\n"
- "\n"
- " ....\n"
- " ....\n"
- "}]]>"
-msgstr ""
-
#. Tag: para
-#: collection_mapping.xml:873
#, no-c-format
msgid "If each child has, at most, one parent, the most natural mapping is a one-to-many association:"
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:879
-#, no-c-format
-msgid ""
- "<![CDATA[<hibernate-mapping>\n"
- "\n"
- " <class name=\"Parent\">\n"
- " <id name=\"id\">\n"
- " <generator class=\"sequence\"/>\n"
- " </id>\n"
- " <set name=\"children\">\n"
- " <key column=\"parent_id\"/>\n"
- " <one-to-many class=\"Child\"/>\n"
- " </set>\n"
- " </class>\n"
- "\n"
- " <class name=\"Child\">\n"
- " <id name=\"id\">\n"
- " <generator class=\"sequence\"/>\n"
- " </id>\n"
- " <property name=\"name\"/>\n"
- " </class>\n"
- "\n"
- "</hibernate-mapping>]]>"
-msgstr ""
-
#. Tag: para
-#: collection_mapping.xml:881
#, no-c-format
msgid "This maps to the following table definitions:"
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:885
-#, no-c-format
-msgid ""
- "<![CDATA[create table parent ( id bigint not null primary key )\n"
- "create table child ( id bigint not null primary key, name varchar(255), parent_id bigint )\n"
- "alter table child add constraint childfk0 (parent_id) references parent]]>"
-msgstr ""
-
#. Tag: para
-#: collection_mapping.xml:887
#, no-c-format
msgid "If the parent is <emphasis>required</emphasis>, use a bidirectional one-to-many association:"
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:892
-#, no-c-format
-msgid ""
- "<![CDATA[<hibernate-mapping>\n"
- "\n"
- " <class name=\"Parent\">\n"
- " <id name=\"id\">\n"
- " <generator class=\"sequence\"/>\n"
- " </id>\n"
- " <set name=\"children\" inverse=\"true\">\n"
- " <key column=\"parent_id\"/>\n"
- " <one-to-many class=\"Child\"/>\n"
- " </set>\n"
- " </class>\n"
- "\n"
- " <class name=\"Child\">\n"
- " <id name=\"id\">\n"
- " <generator class=\"sequence\"/>\n"
- " </id>\n"
- " <property name=\"name\"/>\n"
- " <many-to-one name=\"parent\" class=\"Parent\" column=\"parent_id\" not-null=\"true\"/>\n"
- " </class>\n"
- "\n"
- "</hibernate-mapping>]]>"
-msgstr ""
-
#. Tag: para
-#: collection_mapping.xml:894
#, no-c-format
msgid "Notice the <literal>NOT NULL</literal> constraint:"
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:898
-#, no-c-format
-msgid ""
- "<![CDATA[create table parent ( id bigint not null primary key )\n"
- "create table child ( id bigint not null\n"
- " primary key,\n"
- " name varchar(255),\n"
- " parent_id bigint not null )\n"
- "alter table child add constraint childfk0 (parent_id) references parent]]>"
-msgstr ""
-
#. Tag: para
-#: collection_mapping.xml:900
#, no-c-format
msgid "Alternatively, if this association must be unidirectional you can declare the <literal>NOT NULL</literal> constraint on the <literal><key></literal> mapping:"
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:906
-#, no-c-format
-msgid ""
- "<![CDATA[<hibernate-mapping>\n"
- "\n"
- " <class name=\"Parent\">\n"
- " <id name=\"id\">\n"
- " <generator class=\"sequence\"/>\n"
- " </id>\n"
- " <set name=\"children\">\n"
- " <key column=\"parent_id\" not-null=\"true\"/>\n"
- " <one-to-many class=\"Child\"/>\n"
- " </set>\n"
- " </class>\n"
- "\n"
- " <class name=\"Child\">\n"
- " <id name=\"id\">\n"
- " <generator class=\"sequence\"/>\n"
- " </id>\n"
- " <property name=\"name\"/>\n"
- " </class>\n"
- "\n"
- "</hibernate-mapping>]]>"
-msgstr ""
-
#. Tag: para
-#: collection_mapping.xml:908
#, no-c-format
msgid "On the other hand, if a child has multiple parents, a many-to-many association is appropriate:"
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:913
-#, no-c-format
-msgid ""
- "<![CDATA[<hibernate-mapping>\n"
- "\n"
- " <class name=\"Parent\">\n"
- " <id name=\"id\">\n"
- " <generator class=\"sequence\"/>\n"
- " </id>\n"
- " <set name=\"children\" table=\"childset\">\n"
- " <key column=\"parent_id\"/>\n"
- " <many-to-many class=\"Child\" column=\"child_id\"/>\n"
- " </set>\n"
- " </class>\n"
- "\n"
- " <class name=\"Child\">\n"
- " <id name=\"id\">\n"
- " <generator class=\"sequence\"/>\n"
- " </id>\n"
- " <property name=\"name\"/>\n"
- " </class>\n"
- "\n"
- "</hibernate-mapping>]]>"
-msgstr ""
-
#. Tag: para
-#: collection_mapping.xml:915
#, no-c-format
msgid "Table definitions:"
msgstr ""
-#. Tag: programlisting
-#: collection_mapping.xml:919
-#, no-c-format
-msgid ""
- "<![CDATA[create table parent ( id bigint not null primary key )\n"
- "create table child ( id bigint not null primary key, name varchar(255) )\n"
- "create table childset ( parent_id bigint not null,\n"
- " child_id bigint not null,\n"
- " primary key ( parent_id, child_id ) )\n"
- "alter table childset add constraint childsetfk0 (parent_id) references parent\n"
- "alter table childset add constraint childsetfk1 (child_id) references child]]>"
-msgstr ""
-
#. Tag: para
-#: collection_mapping.xml:921
#, no-c-format
-msgid "For more examples and a complete explanation of a parent/child relationship mapping, see <xref linkend=\"example-parentchild\"/> for more information."
+msgid "For more examples and a complete explanation of a parent/child relationship mapping, see <xref linkend=\"example-parentchild\" /> for more information."
msgstr ""
#. Tag: para
-#: collection_mapping.xml:926
#, no-c-format
msgid "Even more complex association mappings are covered in the next chapter."
msgstr ""
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/component_mapping.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/component_mapping.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/component_mapping.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,481 +1,203 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-10 21:02+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:18\n"
+"PO-Revision-Date: 2010-01-08T04:07:18\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
-#: component_mapping.xml:29
#, no-c-format
msgid "Component Mapping"
msgstr ""
#. Tag: para
-#: component_mapping.xml:31
#, no-c-format
msgid "The notion of a <emphasis>component</emphasis> is re-used in several different contexts and purposes throughout Hibernate."
msgstr ""
#. Tag: title
-#: component_mapping.xml:37
#, no-c-format
msgid "Dependent objects"
msgstr ""
#. Tag: para
-#: component_mapping.xml:39
#, no-c-format
msgid "A component is a contained object that is persisted as a value type and not an entity reference. The term \"component\" refers to the object-oriented notion of composition and not to architecture-level components. For example, you can model a person like this:"
msgstr ""
-#. Tag: programlisting
-#: component_mapping.xml:45
-#, no-c-format
-msgid ""
- "<![CDATA[public class Person {\n"
- " private java.util.Date birthday;\n"
- " private Name name;\n"
- " private String key;\n"
- " public String getKey() {\n"
- " return key;\n"
- " }\n"
- " private void setKey(String key) {\n"
- " this.key=key;\n"
- " }\n"
- " public java.util.Date getBirthday() {\n"
- " return birthday;\n"
- " }\n"
- " public void setBirthday(java.util.Date birthday) {\n"
- " this.birthday = birthday;\n"
- " }\n"
- " public Name getName() {\n"
- " return name;\n"
- " }\n"
- " public void setName(Name name) {\n"
- " this.name = name;\n"
- " }\n"
- " ......\n"
- " ......\n"
- "}]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: component_mapping.xml:47
-#, no-c-format
-msgid ""
- "<![CDATA[public class Name {\n"
- " char initial;\n"
- " String first;\n"
- " String last;\n"
- " public String getFirst() {\n"
- " return first;\n"
- " }\n"
- " void setFirst(String first) {\n"
- " this.first = first;\n"
- " }\n"
- " public String getLast() {\n"
- " return last;\n"
- " }\n"
- " void setLast(String last) {\n"
- " this.last = last;\n"
- " }\n"
- " public char getInitial() {\n"
- " return initial;\n"
- " }\n"
- " void setInitial(char initial) {\n"
- " this.initial = initial;\n"
- " }\n"
- "}]]>"
-msgstr ""
-
#. Tag: para
-#: component_mapping.xml:49
#, no-c-format
msgid "Now <literal>Name</literal> can be persisted as a component of <literal>Person</literal>. <literal>Name</literal> defines getter and setter methods for its persistent properties, but it does not need to declare any interfaces or identifier properties."
msgstr ""
#. Tag: para
-#: component_mapping.xml:56
#, no-c-format
msgid "Our Hibernate mapping would look like this:"
msgstr ""
-#. Tag: programlisting
-#: component_mapping.xml:60
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"eg.Person\" table=\"person\">\n"
- " <id name=\"Key\" column=\"pid\" type=\"string\">\n"
- " <generator class=\"uuid\"/>\n"
- " </id>\n"
- " <property name=\"birthday\" type=\"date\"/>\n"
- " <component name=\"Name\" class=\"eg.Name\"> <!-- class attribute optional -->\n"
- " <property name=\"initial\"/>\n"
- " <property name=\"first\"/>\n"
- " <property name=\"last\"/>\n"
- " </component>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: component_mapping.xml:62
#, no-c-format
msgid "The person table would have the columns <literal>pid</literal>, <literal>birthday</literal>, <literal>initial</literal>, <literal>first</literal> and <literal>last</literal>."
msgstr ""
#. Tag: para
-#: component_mapping.xml:70
#, no-c-format
msgid "Like value types, components do not support shared references. In other words, two persons could have the same name, but the two person objects would contain two independent name objects that were only \"the same\" by value. The null value semantics of a component are <emphasis>ad hoc</emphasis>. When reloading the containing object, Hibernate will assume that if all component columns are null, then the entire component is null. This is suitable for most purposes."
msgstr ""
#. Tag: para
-#: component_mapping.xml:78
#, no-c-format
msgid "The properties of a component can be of any Hibernate type (collections, many-to-one associations, other components, etc). Nested components should <emphasis>not</emphasis> be considered an exotic usage. Hibernate is intended to support a fine-grained object model."
msgstr ""
#. Tag: para
-#: component_mapping.xml:85
#, no-c-format
msgid "The <literal><component></literal> element allows a <literal><parent></literal> subelement that maps a property of the component class as a reference back to the containing entity."
msgstr ""
-#. Tag: programlisting
-#: component_mapping.xml:91
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"eg.Person\" table=\"person\">\n"
- " <id name=\"Key\" column=\"pid\" type=\"string\">\n"
- " <generator class=\"uuid\"/>\n"
- " </id>\n"
- " <property name=\"birthday\" type=\"date\"/>\n"
- " <component name=\"Name\" class=\"eg.Name\" unique=\"true\">\n"
- " <parent name=\"namedPerson\"/> <!-- reference back to the Person -->\n"
- " <property name=\"initial\"/>\n"
- " <property name=\"first\"/>\n"
- " <property name=\"last\"/>\n"
- " </component>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: title
-#: component_mapping.xml:96
#, no-c-format
msgid "Collections of dependent objects"
msgstr ""
#. Tag: para
-#: component_mapping.xml:98
#, no-c-format
msgid "Collections of components are supported (e.g. an array of type <literal>Name</literal>). Declare your component collection by replacing the <literal><element></literal> tag with a <literal><composite-element></literal> tag:"
msgstr ""
-#. Tag: programlisting
-#: component_mapping.xml:105
-#, no-c-format
-msgid ""
- "<![CDATA[<set name=\"someNames\" table=\"some_names\" lazy=\"true\">\n"
- " <key column=\"id\"/>\n"
- " <composite-element class=\"eg.Name\"> <!-- class attribute required -->\n"
- " <property name=\"initial\"/>\n"
- " <property name=\"first\"/>\n"
- " <property name=\"last\"/>\n"
- " </composite-element>\n"
- "</set>]]>"
-msgstr ""
-
#. Tag: para
-#: component_mapping.xml:108
#, no-c-format
msgid "If you define a <literal>Set</literal> of composite elements, it is important to implement <literal>equals()</literal> and <literal>hashCode()</literal> correctly."
msgstr ""
#. Tag: para
-#: component_mapping.xml:115
#, no-c-format
msgid "Composite elements can contain components but not collections. If your composite element contains components, use the <literal><nested-composite-element></literal> tag. This case is a collection of components which themselves have components. You may want to consider if a one-to-many association is more appropriate. Remodel the composite element as an entity, but be aware that even though the Java model is the same, the relational model and persistence semantics are still slightly different."
msgstr ""
#. Tag: para
-#: component_mapping.xml:127
#, no-c-format
msgid "A composite element mapping does not support null-able properties if you are using a <literal><set></literal>. There is no separate primary key column in the composite element table. Hibernate uses each column's value to identify a record when deleting objects, which is not possible with null values. You have to either use only not-null properties in a composite-element or choose a <literal><list></literal>, <literal><map></literal>, <literal><bag></literal> or <literal><idbag></literal>."
msgstr ""
#. Tag: para
-#: component_mapping.xml:138
#, no-c-format
msgid "A special case of a composite element is a composite element with a nested <literal><many-to-one></literal> element. This mapping allows you to map extra columns of a many-to-many association table to the composite element class. The following is a many-to-many association from <literal>Order</literal> to <literal>Item</literal>, where <literal>purchaseDate</literal>, <literal>price</literal> and <literal>quantity</literal> are properties of the association:"
msgstr ""
-#. Tag: programlisting
-#: component_mapping.xml:148
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"eg.Order\" .... >\n"
- " ....\n"
- " <set name=\"purchasedItems\" table=\"purchase_items\" lazy=\"true\">\n"
- " <key column=\"order_id\">\n"
- " <composite-element class=\"eg.Purchase\">\n"
- " <property name=\"purchaseDate\"/>\n"
- " <property name=\"price\"/>\n"
- " <property name=\"quantity\"/>\n"
- " <many-to-one name=\"item\" class=\"eg.Item\"/> <!-- class attribute is optional -->\n"
- " </composite-element>\n"
- " </set>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: component_mapping.xml:150
#, no-c-format
msgid "There cannot be a reference to the purchase on the other side for bidirectional association navigation. Components are value types and do not allow shared references. A single <literal>Purchase</literal> can be in the set of an <literal>Order</literal>, but it cannot be referenced by the <literal>Item</literal> at the same time."
msgstr ""
#. Tag: para
-#: component_mapping.xml:158
#, no-c-format
msgid "Even ternary (or quaternary, etc) associations are possible:"
msgstr ""
-#. Tag: programlisting
-#: component_mapping.xml:160
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"eg.Order\" .... >\n"
- " ....\n"
- " <set name=\"purchasedItems\" table=\"purchase_items\" lazy=\"true\">\n"
- " <key column=\"order_id\">\n"
- " <composite-element class=\"eg.OrderLine\">\n"
- " <many-to-one name=\"purchaseDetails class=\"eg.Purchase\"/>\n"
- " <many-to-one name=\"item\" class=\"eg.Item\"/>\n"
- " </composite-element>\n"
- " </set>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: component_mapping.xml:162
#, no-c-format
msgid "Composite elements can appear in queries using the same syntax as associations to other entities."
msgstr ""
#. Tag: title
-#: component_mapping.xml:170
#, no-c-format
msgid "Components as Map indices"
msgstr ""
#. Tag: para
-#: component_mapping.xml:172
#, no-c-format
msgid "The <literal><composite-map-key></literal> element allows you to map a component class as the key of a <literal>Map</literal>. Ensure that you override <literal>hashCode()</literal> and <literal>equals()</literal> correctly on the component class."
msgstr ""
#. Tag: title
-#: component_mapping.xml:181
#, no-c-format
msgid "Components as composite identifiers"
msgstr ""
#. Tag: para
-#: component_mapping.xml:183
#, no-c-format
msgid "You can use a component as an identifier of an entity class. Your component class must satisfy certain requirements:"
msgstr ""
#. Tag: para
-#: component_mapping.xml:190
#, no-c-format
msgid "It must implement <literal>java.io.Serializable</literal>."
msgstr ""
#. Tag: para
-#: component_mapping.xml:195
#, no-c-format
msgid "It must re-implement <literal>equals()</literal> and <literal>hashCode()</literal> consistently with the database's notion of composite key equality."
msgstr ""
#. Tag: title
-#: component_mapping.xml:204
#, no-c-format
msgid "Note"
msgstr ""
#. Tag: para
-#: component_mapping.xml:205
#, no-c-format
msgid "In Hibernate3, although the second requirement is not an absolutely hard requirement of Hibernate, it is recommended."
msgstr ""
#. Tag: para
-#: component_mapping.xml:211
#, no-c-format
msgid "You cannot use an <literal>IdentifierGenerator</literal> to generate composite keys. Instead the application must assign its own identifiers."
msgstr ""
#. Tag: para
-#: component_mapping.xml:216
#, no-c-format
msgid "Use the <literal><composite-id></literal> tag, with nested <literal><key-property></literal> elements, in place of the usual <literal><id></literal> declaration. For example, the <literal>OrderLine</literal> class has a primary key that depends upon the (composite) primary key of <literal>Order</literal>."
msgstr ""
-#. Tag: programlisting
-#: component_mapping.xml:224
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"OrderLine\">\n"
- " \n"
- " <composite-id name=\"id\" class=\"OrderLineId\">\n"
- " <key-property name=\"lineId\"/>\n"
- " <key-property name=\"orderId\"/>\n"
- " <key-property name=\"customerId\"/>\n"
- " </composite-id>\n"
- " \n"
- " <property name=\"name\"/>\n"
- " \n"
- " <many-to-one name=\"order\" class=\"Order\"\n"
- " insert=\"false\" update=\"false\">\n"
- " <column name=\"orderId\"/>\n"
- " <column name=\"customerId\"/>\n"
- " </many-to-one>\n"
- " ....\n"
- " \n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: component_mapping.xml:226
#, no-c-format
msgid "Any foreign keys referencing the <literal>OrderLine</literal> table are now composite. Declare this in your mappings for other classes. An association to <literal>OrderLine</literal> is mapped like this:"
msgstr ""
-#. Tag: programlisting
-#: component_mapping.xml:232
-#, no-c-format
-msgid ""
- "<![CDATA[<many-to-one name=\"orderLine\" class=\"OrderLine\">\n"
- "<!-- the \"class\" attribute is optional, as usual -->\n"
- " <column name=\"lineId\"/>\n"
- " <column name=\"orderId\"/>\n"
- " <column name=\"customerId\"/>\n"
- "</many-to-one>]]>"
-msgstr ""
-
#. Tag: para
-#: component_mapping.xml:235
#, no-c-format
-msgid "The <literal>column</literal> element is an alternative to the <literal>column</literal> attribute everywhere. Using the <literal>column</literal> element just gives more declaration options, which are mostly useful when utilizing <literal>hbm2ddl</literal>"
+msgid "The <literal><column></literal> tag is an alternative to the <literal>column</literal> attribute everywhere. Using the <literal><column></literal> tag just gives more declaration options, which are mostly useful when utilizing <literal>hbm2ddl</literal>."
msgstr ""
#. Tag: para
-#: component_mapping.xml:244
#, no-c-format
msgid "A <literal>many-to-many</literal> association to <literal>OrderLine</literal> also uses the composite foreign key:"
msgstr ""
-#. Tag: programlisting
-#: component_mapping.xml:249
-#, no-c-format
-msgid ""
- "<![CDATA[<set name=\"undeliveredOrderLines\">\n"
- " <key column name=\"warehouseId\"/>\n"
- " <many-to-many class=\"OrderLine\">\n"
- " <column name=\"lineId\"/>\n"
- " <column name=\"orderId\"/>\n"
- " <column name=\"customerId\"/>\n"
- " </many-to-many>\n"
- "</set>]]>"
-msgstr ""
-
#. Tag: para
-#: component_mapping.xml:251
#, no-c-format
msgid "The collection of <literal>OrderLine</literal>s in <literal>Order</literal> would use:"
msgstr ""
-#. Tag: programlisting
-#: component_mapping.xml:256
-#, no-c-format
-msgid ""
- "<![CDATA[<set name=\"orderLines\" inverse=\"true\">\n"
- " <key>\n"
- " <column name=\"orderId\"/>\n"
- " <column name=\"customerId\"/>\n"
- " </key>\n"
- " <one-to-many class=\"OrderLine\"/>\n"
- "</set>]]>"
-msgstr ""
-
#. Tag: para
-#: component_mapping.xml:258
#, no-c-format
msgid "The <literal><one-to-many></literal> element declares no columns."
msgstr ""
#. Tag: para
-#: component_mapping.xml:262
#, no-c-format
msgid "If <literal>OrderLine</literal> itself owns a collection, it also has a composite foreign key."
msgstr ""
-#. Tag: programlisting
-#: component_mapping.xml:267
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"OrderLine\">\n"
- " ....\n"
- " ....\n"
- " <list name=\"deliveryAttempts\">\n"
- " <key> <!-- a collection inherits the composite key type -->\n"
- " <column name=\"lineId\"/>\n"
- " <column name=\"orderId\"/>\n"
- " <column name=\"customerId\"/>\n"
- " </key>\n"
- " <list-index column=\"attemptId\" base=\"1\"/>\n"
- " <composite-element class=\"DeliveryAttempt\">\n"
- " ...\n"
- " </composite-element>\n"
- " </set>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: title
-#: component_mapping.xml:272
#, no-c-format
msgid "Dynamic components"
msgstr ""
#. Tag: para
-#: component_mapping.xml:274
#, no-c-format
msgid "You can also map a property of type <literal>Map</literal>:"
msgstr ""
-#. Tag: programlisting
-#: component_mapping.xml:278
-#, no-c-format
-msgid ""
- "<![CDATA[<dynamic-component name=\"userAttributes\">\n"
- " <property name=\"foo\" column=\"FOO\" type=\"string\"/>\n"
- " <property name=\"bar\" column=\"BAR\" type=\"integer\"/>\n"
- " <many-to-one name=\"baz\" class=\"Baz\" column=\"BAZ_ID\"/>\n"
- "</dynamic-component>]]>"
-msgstr ""
-
#. Tag: para
-#: component_mapping.xml:280
#, no-c-format
msgid "The semantics of a <literal><dynamic-component></literal> mapping are identical to <literal><component></literal>. The advantage of this kind of mapping is the ability to determine the actual properties of the bean at deployment time just by editing the mapping document. Runtime manipulation of the mapping document is also possible, using a DOM parser. You can also access, and change, Hibernate's configuration-time metamodel via the <literal>Configuration</literal> object."
msgstr ""
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/configuration.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/configuration.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/configuration.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,2188 +1,1663 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-23 18:41+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:18\n"
+"PO-Revision-Date: 2010-01-08T04:07:18\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
-#: configuration.xml:29
#, no-c-format
msgid "Configuration"
msgstr ""
#. Tag: para
-#: configuration.xml:31
#, no-c-format
msgid "Hibernate is designed to operate in many different environments and, as such, there is a broad range of configuration parameters. Fortunately, most have sensible default values and Hibernate is distributed with an example <literal>hibernate.properties</literal> file in <literal>etc/</literal> that displays the various options. Simply put the example file in your classpath and customize it to suit your needs."
msgstr ""
#. Tag: title
-#: configuration.xml:40
#, no-c-format
msgid "Programmatic configuration"
msgstr ""
#. Tag: para
-#: configuration.xml:42
#, no-c-format
msgid "An instance of <classname>org.hibernate.cfg.Configuration</classname> represents an entire set of mappings of an application's Java types to an SQL database. The <classname>org.hibernate.cfg.Configuration</classname> is used to build an immutable <interfacename>org.hibernate.SessionFactory</interfacename>. The mappings are compiled from various XML mapping files."
msgstr ""
#. Tag: para
-#: configuration.xml:49
#, no-c-format
msgid "You can obtain a <classname>org.hibernate.cfg.Configuration</classname> instance by instantiating it directly and specifying XML mapping documents. If the mapping files are in the classpath, use <literal>addResource()</literal>. For example:"
msgstr ""
-#. Tag: programlisting
-#: configuration.xml:55
-#, no-c-format
-msgid ""
- "<![CDATA[Configuration cfg = new Configuration()\n"
- " .addResource(\"Item.hbm.xml\")\n"
- " .addResource(\"Bid.hbm.xml\");]]>"
-msgstr ""
-
#. Tag: para
-#: configuration.xml:57
#, no-c-format
msgid "An alternative way is to specify the mapped class and allow Hibernate to find the mapping document for you:"
msgstr ""
-#. Tag: programlisting
-#: configuration.xml:62
-#, no-c-format
-msgid ""
- "<![CDATA[Configuration cfg = new Configuration()\n"
- " .addClass(org.hibernate.auction.Item.class)\n"
- " .addClass(org.hibernate.auction.Bid.class);]]>"
-msgstr ""
-
#. Tag: para
-#: configuration.xml:64
#, no-c-format
msgid "Hibernate will then search for mapping files named <filename>/org/hibernate/auction/Item.hbm.xml</filename> and <filename>/org/hibernate/auction/Bid.hbm.xml</filename> in the classpath. This approach eliminates any hardcoded filenames."
msgstr ""
#. Tag: para
-#: configuration.xml:70
#, no-c-format
msgid "A <classname>org.hibernate.cfg.Configuration</classname> also allows you to specify configuration properties. For example:"
msgstr ""
-#. Tag: programlisting
-#: configuration.xml:75
-#, no-c-format
-msgid ""
- "<![CDATA[Configuration cfg = new Configuration()\n"
- " .addClass(org.hibernate.auction.Item.class)\n"
- " .addClass(org.hibernate.auction.Bid.class)\n"
- " .setProperty(\"hibernate.dialect\", \"org.hibernate.dialect.MySQLInnoDBDialect\")\n"
- " .setProperty(\"hibernate.connection.datasource\", \"java:comp/env/jdbc/test\")\n"
- " .setProperty(\"hibernate.order_updates\", \"true\");]]>"
-msgstr ""
-
#. Tag: para
-#: configuration.xml:77
#, no-c-format
msgid "This is not the only way to pass configuration properties to Hibernate. Some alternative options include:"
msgstr ""
#. Tag: para
-#: configuration.xml:84
#, no-c-format
msgid "Pass an instance of <classname>java.util.Properties</classname> to <literal>Configuration.setProperties()</literal>."
msgstr ""
#. Tag: para
-#: configuration.xml:90
#, no-c-format
msgid "Place a file named <filename>hibernate.properties</filename> in a root directory of the classpath."
msgstr ""
#. Tag: para
-#: configuration.xml:95
#, no-c-format
msgid "Set <literal>System</literal> properties using <literal>java -Dproperty=value</literal>."
msgstr ""
#. Tag: para
-#: configuration.xml:100
#, no-c-format
msgid "Include <literal><property></literal> elements in <literal>hibernate.cfg.xml</literal> (this is discussed later)."
msgstr ""
#. Tag: para
-#: configuration.xml:107
#, no-c-format
msgid "If you want to get started quickly<filename>hibernate.properties</filename> is the easiest approach."
msgstr ""
#. Tag: para
-#: configuration.xml:111
#, no-c-format
msgid "The <classname>org.hibernate.cfg.Configuration</classname> is intended as a startup-time object that will be discarded once a <literal>SessionFactory</literal> is created."
msgstr ""
#. Tag: title
-#: configuration.xml:119
#, no-c-format
msgid "Obtaining a SessionFactory"
msgstr ""
#. Tag: para
-#: configuration.xml:121
#, no-c-format
-msgid "When all mappings have been parsed by the <classname>org.hibernate.cfg.Configuration</classname>, the application must obtain a factory for <interfacename>org.hibernate.Session</interfacename> instances. This factory is intended to be shared by all application threads:"
+msgid "When all mappings have been parsed by the <classname>org.hibernate.cfg.Configuration</classname>, the application must obtain a factory for <classname>org.hibernate.Session</classname> instances. This factory is intended to be shared by all application threads:"
msgstr ""
-#. Tag: programlisting
-#: configuration.xml:127
-#, no-c-format
-msgid "<![CDATA[SessionFactory sessions = cfg.buildSessionFactory();]]>"
-msgstr ""
-
#. Tag: para
-#: configuration.xml:129
#, no-c-format
-msgid "Hibernate does allow your application to instantiate more than one <interfacename>org.hibernate.SessionFactory</interfacename>. This is useful if you are using more than one database."
+msgid "Hibernate does allow your application to instantiate more than one <classname>org.hibernate.SessionFactory</classname>. This is useful if you are using more than one database."
msgstr ""
#. Tag: title
-#: configuration.xml:138
#, no-c-format
msgid "JDBC connections"
msgstr ""
#. Tag: para
-#: configuration.xml:140
#, no-c-format
msgid "It is advisable to have the <interfacename>org.hibernate.SessionFactory</interfacename> create and pool JDBC connections for you. If you take this approach, opening a <interfacename>org.hibernate.Session</interfacename> is as simple as:"
msgstr ""
-#. Tag: programlisting
-#: configuration.xml:146
-#, no-c-format
-msgid "<![CDATA[Session session = sessions.openSession(); // open a new Session]]>"
-msgstr ""
-
#. Tag: para
-#: configuration.xml:148
#, no-c-format
msgid "Once you start a task that requires access to the database, a JDBC connection will be obtained from the pool."
msgstr ""
#. Tag: para
-#: configuration.xml:153
#, no-c-format
msgid "Before you can do this, you first need to pass some JDBC connection properties to Hibernate. All Hibernate property names and semantics are defined on the class <classname>org.hibernate.cfg.Environment</classname>. The most important settings for JDBC connection configuration are outlined below."
msgstr ""
#. Tag: para
-#: configuration.xml:159
#, no-c-format
msgid "Hibernate will obtain and pool connections using <classname>java.sql.DriverManager</classname> if you set the following properties:"
msgstr ""
#. Tag: title
-#: configuration.xml:165
#, no-c-format
msgid "Hibernate JDBC Properties"
msgstr ""
-#. Tag: entry
-#: configuration.xml:171 configuration.xml:257 configuration.xml:353 configuration.xml:546 configuration.xml:741 configuration.xml:848 configuration.xml:936
+#. Tag: para
#, no-c-format
msgid "Property name"
msgstr ""
-#. Tag: entry
-#: configuration.xml:172 configuration.xml:258 configuration.xml:354 configuration.xml:547 configuration.xml:742 configuration.xml:849 configuration.xml:937
+#. Tag: para
#, no-c-format
msgid "Purpose"
msgstr ""
-#. Tag: property
-#: configuration.xml:178
+#. Tag: para
#, no-c-format
-msgid "hibernate.connection.driver_class"
+msgid "<property>hibernate.connection.driver_class</property>"
msgstr ""
-#. Tag: emphasis
-#: configuration.xml:181
+#. Tag: para
#, no-c-format
-msgid "JDBC driver class"
+msgid "<emphasis>JDBC driver class</emphasis>"
msgstr ""
-#. Tag: property
-#: configuration.xml:186
+#. Tag: para
#, no-c-format
-msgid "hibernate.connection.url"
+msgid "<property>hibernate.connection.url</property>"
msgstr ""
-#. Tag: emphasis
-#: configuration.xml:189
+#. Tag: para
#, no-c-format
-msgid "JDBC URL"
+msgid "<emphasis>JDBC URL</emphasis>"
msgstr ""
-#. Tag: property
-#: configuration.xml:194 configuration.xml:288
+#. Tag: para
#, no-c-format
-msgid "hibernate.connection.username"
+msgid "<property>hibernate.connection.username</property>"
msgstr ""
-#. Tag: emphasis
-#: configuration.xml:197
+#. Tag: para
#, no-c-format
-msgid "database user"
+msgid "<emphasis>database user</emphasis>"
msgstr ""
-#. Tag: property
-#: configuration.xml:202 configuration.xml:296
+#. Tag: para
#, no-c-format
-msgid "hibernate.connection.password"
+msgid "<property>hibernate.connection.password</property>"
msgstr ""
-#. Tag: emphasis
-#: configuration.xml:205
+#. Tag: para
#, no-c-format
-msgid "database user password"
+msgid "<emphasis>database user password</emphasis>"
msgstr ""
-#. Tag: property
-#: configuration.xml:210
+#. Tag: para
#, no-c-format
-msgid "hibernate.connection.pool_size"
+msgid "<property>hibernate.connection.pool_size</property>"
msgstr ""
-#. Tag: emphasis
-#: configuration.xml:213
+#. Tag: para
#, no-c-format
-msgid "maximum number of pooled connections"
+msgid "<emphasis>maximum number of pooled connections</emphasis>"
msgstr ""
#. Tag: para
-#: configuration.xml:220
#, no-c-format
msgid "Hibernate's own connection pooling algorithm is, however, quite rudimentary. It is intended to help you get started and is <emphasis>not intended for use in a production system</emphasis>, or even for performance testing. You should use a third party pool for best performance and stability. Just replace the <property>hibernate.connection.pool_size</property> property with connection pool specific settings. This will turn off Hibernate's internal pool. For example, you might like to use c3p0."
msgstr ""
#. Tag: para
-#: configuration.xml:230
#, no-c-format
msgid "C3P0 is an open source JDBC connection pool distributed along with Hibernate in the <filename>lib</filename> directory. Hibernate will use its <classname>org.hibernate.connection.C3P0ConnectionProvider</classname> for connection pooling if you set <property>hibernate.c3p0.*</property> properties. If you would like to use Proxool, refer to the packaged <filename>hibernate.properties</filename> and the Hibernate web site for more information."
msgstr ""
#. Tag: para
-#: configuration.xml:238
#, no-c-format
msgid "The following is an example <filename>hibernate.properties</filename> file for c3p0:"
msgstr ""
-#. Tag: programlisting
-#: configuration.xml:242
-#, no-c-format
-msgid ""
- "<![CDATA[hibernate.connection.driver_class = org.postgresql.Driver\n"
- "hibernate.connection.url = jdbc:postgresql://localhost/mydatabase\n"
- "hibernate.connection.username = myuser\n"
- "hibernate.connection.password = secret\n"
- "hibernate.c3p0.min_size=5\n"
- "hibernate.c3p0.max_size=20\n"
- "hibernate.c3p0.timeout=1800\n"
- "hibernate.c3p0.max_statements=50\n"
- "hibernate.dialect = org.hibernate.dialect.PostgreSQLDialect]]>"
-msgstr ""
-
#. Tag: para
-#: configuration.xml:244
#, no-c-format
msgid "For use inside an application server, you should almost always configure Hibernate to obtain connections from an application server <interfacename>javax.sql.Datasource</interfacename> registered in JNDI. You will need to set at least one of the following properties:"
msgstr ""
#. Tag: title
-#: configuration.xml:251
#, no-c-format
msgid "Hibernate Datasource Properties"
msgstr ""
-#. Tag: property
-#: configuration.xml:264
+#. Tag: para
#, no-c-format
-msgid "hibernate.connection.datasource"
+msgid "<property>hibernate.connection.datasource</property>"
msgstr ""
-#. Tag: emphasis
-#: configuration.xml:267
+#. Tag: para
#, no-c-format
-msgid "datasource JNDI name"
+msgid "<emphasis>datasource JNDI name</emphasis>"
msgstr ""
-#. Tag: property
-#: configuration.xml:272
+#. Tag: para
#, no-c-format
-msgid "hibernate.jndi.url"
+msgid "<property>hibernate.jndi.url</property>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:274
+#. Tag: para
#, no-c-format
msgid "<emphasis>URL of the JNDI provider</emphasis> (optional)"
msgstr ""
-#. Tag: property
-#: configuration.xml:280
+#. Tag: para
#, no-c-format
-msgid "hibernate.jndi.class"
+msgid "<property>hibernate.jndi.class</property>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:282
+#. Tag: para
#, no-c-format
msgid "<emphasis>class of the JNDI <literal>InitialContextFactory</literal></emphasis> (optional)"
msgstr ""
-#. Tag: entry
-#: configuration.xml:290
+#. Tag: para
#, no-c-format
msgid "<emphasis>database user</emphasis> (optional)"
msgstr ""
-#. Tag: entry
-#: configuration.xml:298
+#. Tag: para
#, no-c-format
msgid "<emphasis>database user password</emphasis> (optional)"
msgstr ""
#. Tag: para
-#: configuration.xml:306
#, no-c-format
msgid "Here is an example <filename>hibernate.properties</filename> file for an application server provided JNDI datasource:"
msgstr ""
-#. Tag: programlisting
-#: configuration.xml:311
-#, no-c-format
-msgid ""
- "<![CDATA[hibernate.connection.datasource = java:/comp/env/jdbc/test\n"
- "hibernate.transaction.factory_class = \\\n"
- " org.hibernate.transaction.JTATransactionFactory\n"
- "hibernate.transaction.manager_lookup_class = \\\n"
- " org.hibernate.transaction.JBossTransactionManagerLookup\n"
- "hibernate.dialect = org.hibernate.dialect.PostgreSQLDialect]]>"
-msgstr ""
-
#. Tag: para
-#: configuration.xml:313
#, no-c-format
msgid "JDBC connections obtained from a JNDI datasource will automatically participate in the container-managed transactions of the application server."
msgstr ""
#. Tag: para
-#: configuration.xml:318
#, no-c-format
msgid "Arbitrary connection properties can be given by prepending \"<literal>hibernate.connection</literal>\" to the connection property name. For example, you can specify a <property>charSet</property> connection property using <property>hibernate.connection.charSet</property>."
msgstr ""
#. Tag: para
-#: configuration.xml:324
#, no-c-format
msgid "You can define your own plugin strategy for obtaining JDBC connections by implementing the interface <interfacename>org.hibernate.connection.ConnectionProvider</interfacename>, and specifying your custom implementation via the <property>hibernate.connection.provider_class</property> property."
msgstr ""
#. Tag: title
-#: configuration.xml:333
#, no-c-format
msgid "Optional configuration properties"
msgstr ""
#. Tag: para
-#: configuration.xml:335
#, no-c-format
msgid "There are a number of other properties that control the behavior of Hibernate at runtime. All are optional and have reasonable default values."
msgstr ""
-#. Tag: warning
-#: configuration.xml:341
+#. Tag: para
#, no-c-format
-msgid "<emphasis>Some of these properties are \"system-level\" only.</emphasis> System-level properties can be set only via <literal>java -Dproperty=value</literal> or <filename>hibernate.properties</filename>. They <emphasis>cannot</emphasis> be set by the other techniques described above."
+msgid "Some of these properties are system-level only. System-level properties can be set only via <code>java -Dproperty=value</code> or <filename>hibernate.properties</filename>. They <emphasis>cannot</emphasis> be set by the other techniques described above."
msgstr ""
#. Tag: title
-#: configuration.xml:347
#, no-c-format
msgid "Hibernate Configuration Properties"
msgstr ""
-#. Tag: property
-#: configuration.xml:360
+#. Tag: para
#, no-c-format
-msgid "hibernate.dialect"
+msgid "<property>hibernate.dialect</property>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:362
+#. Tag: para
#, no-c-format
msgid "The classname of a Hibernate <classname>org.hibernate.dialect.Dialect</classname> which allows Hibernate to generate SQL optimized for a particular relational database."
msgstr ""
#. Tag: para
-#: configuration.xml:365
#, no-c-format
msgid "<emphasis role=\"strong\">e.g.</emphasis> <literal>full.classname.of.Dialect</literal>"
msgstr ""
#. Tag: para
-#: configuration.xml:369
#, no-c-format
msgid "In most cases Hibernate will actually be able to choose the correct <classname>org.hibernate.dialect.Dialect</classname> implementation based on the <literal>JDBC metadata</literal> returned by the JDBC driver."
msgstr ""
-#. Tag: property
-#: configuration.xml:378
+#. Tag: para
#, no-c-format
-msgid "hibernate.show_sql"
+msgid "<property>hibernate.show_sql</property>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:380
+#. Tag: para
#, no-c-format
msgid "Write all SQL statements to console. This is an alternative to setting the log category <literal>org.hibernate.SQL</literal> to <literal>debug</literal>."
msgstr ""
#. Tag: para
-#: configuration.xml:384 configuration.xml:396 configuration.xml:490 configuration.xml:503 configuration.xml:516 configuration.xml:529 configuration.xml:581 configuration.xml:608 configuration.xml:621 configuration.xml:676 configuration.xml:904 configuration.xml:919 configuration.xml:1009
#, no-c-format
msgid "<emphasis role=\"strong\">e.g.</emphasis> <literal>true</literal> | <literal>false</literal>"
msgstr ""
-#. Tag: property
-#: configuration.xml:392
+#. Tag: para
#, no-c-format
-msgid "hibernate.format_sql"
+msgid "<property>hibernate.format_sql</property>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:394
+#. Tag: para
#, no-c-format
msgid "Pretty print the SQL in the log and console."
msgstr ""
-#. Tag: property
-#: configuration.xml:404
+#. Tag: para
#, no-c-format
-msgid "hibernate.default_schema"
+msgid "<property>hibernate.default_schema</property>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:406
+#. Tag: para
#, no-c-format
msgid "Qualify unqualified table names with the given schema/tablespace in generated SQL."
msgstr ""
#. Tag: para
-#: configuration.xml:409
#, no-c-format
msgid "<emphasis role=\"strong\">e.g.</emphasis> <literal>SCHEMA_NAME</literal>"
msgstr ""
-#. Tag: property
-#: configuration.xml:417
+#. Tag: para
#, no-c-format
-msgid "hibernate.default_catalog"
+msgid "<property>hibernate.default_catalog</property>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:419
+#. Tag: para
#, no-c-format
msgid "Qualifies unqualified table names with the given catalog in generated SQL."
msgstr ""
#. Tag: para
-#: configuration.xml:422
#, no-c-format
msgid "<emphasis role=\"strong\">e.g.</emphasis> <literal>CATALOG_NAME</literal>"
msgstr ""
-#. Tag: property
-#: configuration.xml:430
+#. Tag: para
#, no-c-format
-msgid "hibernate.session_factory_name"
+msgid "<property>hibernate.session_factory_name</property>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:432
+#. Tag: para
#, no-c-format
msgid "The <interfacename>org.hibernate.SessionFactory</interfacename> will be automatically bound to this name in JNDI after it has been created."
msgstr ""
#. Tag: para
-#: configuration.xml:435 configuration.xml:875
#, no-c-format
msgid "<emphasis role=\"strong\">e.g.</emphasis> <literal>jndi/composite/name</literal>"
msgstr ""
-#. Tag: property
-#: configuration.xml:443
+#. Tag: para
#, no-c-format
-msgid "hibernate.max_fetch_depth"
+msgid "<property>hibernate.max_fetch_depth</property>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:445
+#. Tag: para
#, no-c-format
msgid "Sets a maximum \"depth\" for the outer join fetch tree for single-ended associations (one-to-one, many-to-one). A <literal>0</literal> disables default outer join fetching."
msgstr ""
#. Tag: para
-#: configuration.xml:449
#, no-c-format
msgid "<emphasis role=\"strong\">e.g.</emphasis> recommended values between <literal>0</literal> and <literal>3</literal>"
msgstr ""
-#. Tag: property
-#: configuration.xml:458
+#. Tag: para
#, no-c-format
-msgid "hibernate.default_batch_fetch_size"
+msgid "<property>hibernate.default_batch_fetch_size</property>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:460
+#. Tag: para
#, no-c-format
msgid "Sets a default size for Hibernate batch fetching of associations."
msgstr ""
#. Tag: para
-#: configuration.xml:462
#, no-c-format
msgid "<emphasis role=\"strong\">e.g.</emphasis> recommended values <literal>4</literal>, <literal>8</literal>, <literal>16</literal>"
msgstr ""
-#. Tag: property
-#: configuration.xml:471
+#. Tag: para
#, no-c-format
-msgid "hibernate.default_entity_mode"
+msgid "<property>hibernate.default_entity_mode</property>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:473
+#. Tag: para
#, no-c-format
-msgid "Sets a default mode for entity representation for all sessions opened from this <literal>SessionFactory</literal>"
+msgid "Sets a default mode for entity representation for all sessions opened from this <literal>SessionFactory</literal>."
msgstr ""
#. Tag: para
-#: configuration.xml:476
#, no-c-format
msgid "<literal>dynamic-map</literal>, <literal>dom4j</literal>, <literal>pojo</literal>"
msgstr ""
-#. Tag: property
-#: configuration.xml:484
+#. Tag: para
#, no-c-format
-msgid "hibernate.order_updates"
+msgid "<property>hibernate.order_updates</property>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:486
+#. Tag: para
#, no-c-format
msgid "Forces Hibernate to order SQL updates by the primary key value of the items being updated. This will result in fewer transaction deadlocks in highly concurrent systems."
msgstr ""
-#. Tag: property
-#: configuration.xml:498
+#. Tag: para
#, no-c-format
-msgid "hibernate.generate_statistics"
+msgid "<property>hibernate.generate_statistics</property>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:500
+#. Tag: para
#, no-c-format
msgid "If enabled, Hibernate will collect statistics useful for performance tuning."
msgstr ""
-#. Tag: property
-#: configuration.xml:511
+#. Tag: para
#, no-c-format
-msgid "hibernate.use_identifier_rollback"
+msgid "<property>hibernate.use_identifier_rollback</property>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:513
+#. Tag: para
#, no-c-format
msgid "If enabled, generated identifier properties will be reset to default values when objects are deleted."
msgstr ""
-#. Tag: property
-#: configuration.xml:524
+#. Tag: para
#, no-c-format
-msgid "hibernate.use_sql_comments"
+msgid "<property>hibernate.use_sql_comments</property>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:526
+#. Tag: para
#, no-c-format
msgid "If turned on, Hibernate will generate comments inside the SQL, for easier debugging, defaults to <literal>false</literal>."
msgstr ""
#. Tag: title
-#: configuration.xml:540
#, no-c-format
msgid "Hibernate JDBC and Connection Properties"
msgstr ""
-#. Tag: property
-#: configuration.xml:553
+#. Tag: para
#, no-c-format
-msgid "hibernate.jdbc.fetch_size"
+msgid "<property>hibernate.jdbc.fetch_size</property>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:555
+#. Tag: para
#, no-c-format
msgid "A non-zero value determines the JDBC fetch size (calls <literal>Statement.setFetchSize()</literal>)."
msgstr ""
-#. Tag: property
-#: configuration.xml:562
+#. Tag: para
#, no-c-format
-msgid "hibernate.jdbc.batch_size"
+msgid "<property>hibernate.jdbc.batch_size</property>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:564
+#. Tag: para
#, no-c-format
msgid "A non-zero value enables use of JDBC2 batch updates by Hibernate."
msgstr ""
#. Tag: para
-#: configuration.xml:566
#, no-c-format
msgid "<emphasis role=\"strong\">e.g.</emphasis> recommended values between <literal>5</literal> and <literal>30</literal>"
msgstr ""
-#. Tag: property
-#: configuration.xml:574
+#. Tag: para
#, no-c-format
-msgid "hibernate.jdbc.batch_versioned_data"
+msgid "<property>hibernate.jdbc.batch_versioned_data</property>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:576
+#. Tag: para
#, no-c-format
msgid "Set this property to <literal>true</literal> if your JDBC driver returns correct row counts from <literal>executeBatch()</literal>. Iit is usually safe to turn this option on. Hibernate will then use batched DML for automatically versioned data. Defaults to <literal>false</literal>."
msgstr ""
-#. Tag: property
-#: configuration.xml:589
+#. Tag: para
#, no-c-format
-msgid "hibernate.jdbc.factory_class"
+msgid "<property>hibernate.jdbc.factory_class</property>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:591
+#. Tag: para
#, no-c-format
msgid "Select a custom <interfacename>org.hibernate.jdbc.Batcher</interfacename>. Most applications will not need this configuration property."
msgstr ""
#. Tag: para
-#: configuration.xml:594
#, no-c-format
msgid "<emphasis role=\"strong\">e.g.</emphasis> <literal>classname.of.BatcherFactory</literal>"
msgstr ""
-#. Tag: property
-#: configuration.xml:602
+#. Tag: para
#, no-c-format
-msgid "hibernate.jdbc.use_scrollable_resultset"
+msgid "<property>hibernate.jdbc.use_scrollable_resultset</property>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:604
+#. Tag: para
#, no-c-format
msgid "Enables use of JDBC2 scrollable resultsets by Hibernate. This property is only necessary when using user-supplied JDBC connections. Hibernate uses connection metadata otherwise."
msgstr ""
-#. Tag: property
-#: configuration.xml:616
+#. Tag: para
#, no-c-format
-msgid "hibernate.jdbc.use_streams_for_binary"
+msgid "<property>hibernate.jdbc.use_streams_for_binary</property>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:618
+#. Tag: para
#, no-c-format
msgid "Use streams when writing/reading <literal>binary</literal> or <literal>serializable</literal> types to/from JDBC. <emphasis>*system-level property*</emphasis>"
msgstr ""
-#. Tag: property
-#: configuration.xml:629
+#. Tag: para
#, no-c-format
-msgid "hibernate.jdbc.use_get_generated_keys"
+msgid "<property>hibernate.jdbc.use_get_generated_keys</property>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:631
+#. Tag: para
#, no-c-format
msgid "Enables use of JDBC3 <literal>PreparedStatement.getGeneratedKeys()</literal> to retrieve natively generated keys after insert. Requires JDBC3+ driver and JRE1.4+, set to false if your driver has problems with the Hibernate identifier generators. By default, it tries to determine the driver capabilities using connection metadata."
msgstr ""
#. Tag: para
-#: configuration.xml:637 configuration.xml:767 configuration.xml:779 configuration.xml:793 configuration.xml:831
#, no-c-format
msgid "<emphasis role=\"strong\">e.g.</emphasis> <literal>true|false</literal>"
msgstr ""
-#. Tag: property
-#: configuration.xml:645
+#. Tag: para
#, no-c-format
-msgid "hibernate.connection.provider_class"
+msgid "<property>hibernate.connection.provider_class</property>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:647
+#. Tag: para
#, no-c-format
msgid "The classname of a custom <interfacename>org.hibernate.connection.ConnectionProvider</interfacename> which provides JDBC connections to Hibernate."
msgstr ""
#. Tag: para
-#: configuration.xml:650
#, no-c-format
msgid "<emphasis role=\"strong\">e.g.</emphasis> <literal>classname.of.ConnectionProvider</literal>"
msgstr ""
-#. Tag: property
-#: configuration.xml:658
+#. Tag: para
#, no-c-format
-msgid "hibernate.connection.isolation"
+msgid "<property>hibernate.connection.isolation</property>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:660
+#. Tag: para
#, no-c-format
msgid "Sets the JDBC transaction isolation level. Check <interfacename>java.sql.Connection</interfacename> for meaningful values, but note that most databases do not support all isolation levels and some define additional, non-standard isolations."
msgstr ""
#. Tag: para
-#: configuration.xml:664
#, no-c-format
msgid "<emphasis role=\"strong\">e.g.</emphasis> <literal>1, 2, 4, 8</literal>"
msgstr ""
-#. Tag: property
-#: configuration.xml:672
+#. Tag: para
#, no-c-format
-msgid "hibernate.connection.autocommit"
+msgid "<property>hibernate.connection.autocommit</property>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:674
+#. Tag: para
#, no-c-format
msgid "Enables autocommit for JDBC pooled connections (it is not recommended)."
msgstr ""
-#. Tag: property
-#: configuration.xml:684
+#. Tag: para
#, no-c-format
-msgid "hibernate.connection.release_mode"
+msgid "<property>hibernate.connection.release_mode</property>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:686
+#. Tag: para
#, no-c-format
msgid "Specifies when Hibernate should release JDBC connections. By default, a JDBC connection is held until the session is explicitly closed or disconnected. For an application server JTA datasource, use <literal>after_statement</literal> to aggressively release connections after every JDBC call. For a non-JTA connection, it often makes sense to release the connection at the end of each transaction, by using <literal>after_transaction</literal>. <literal>auto</literal> will choose <literal>after_statement</literal> for the JTA and CMT transaction strategies and <literal>after_transaction</literal> for the JDBC transaction strategy."
msgstr ""
#. Tag: para
-#: configuration.xml:697
#, no-c-format
msgid "<emphasis role=\"strong\">e.g.</emphasis> <literal>auto</literal> (default) | <literal>on_close</literal> | <literal>after_transaction</literal> | <literal>after_statement</literal>"
msgstr ""
#. Tag: para
-#: configuration.xml:702
#, no-c-format
-msgid "This setting only affects <literal>Session</literal>s returned from <literal>SessionFactory.openSession</literal>. For <literal>Session</literal>s obtained through <literal>SessionFactory.getCurrentSession</literal>, the <literal>CurrentSessionContext</literal> implementation configured for use controls the connection release mode for those <literal>Session</literal>s. See"
+msgid "This setting only affects <literal>Session</literal>s returned from <literal>SessionFactory.openSession</literal>. For <literal>Session</literal>s obtained through <literal>SessionFactory.getCurrentSession</literal>, the <literal>CurrentSessionContext</literal> implementation configured for use controls the connection release mode for those <literal>Session</literal>s. See <xref linkend=\"architecture-current-session\" />"
msgstr ""
-#. Tag: entry
-#: configuration.xml:713
+#. Tag: para
#, no-c-format
msgid "<property>hibernate.connection.</property><emphasis><propertyName></emphasis>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:716
+#. Tag: para
#, no-c-format
msgid "Pass the JDBC property <emphasis><propertyName></emphasis> to <literal>DriverManager.getConnection()</literal>."
msgstr ""
-#. Tag: entry
-#: configuration.xml:722
+#. Tag: para
#, no-c-format
msgid "<property>hibernate.jndi.</property><emphasis><propertyName></emphasis>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:725
+#. Tag: para
#, no-c-format
msgid "Pass the property <emphasis><propertyName></emphasis> to the JNDI <literal>InitialContextFactory</literal>."
msgstr ""
#. Tag: title
-#: configuration.xml:735
#, no-c-format
msgid "Hibernate Cache Properties"
msgstr ""
-#. Tag: literal
-#: configuration.xml:748
+#. Tag: para
#, no-c-format
-msgid "hibernate.cache.provider_class"
+msgid "<literal>hibernate.cache.provider_class</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:750
+#. Tag: para
#, no-c-format
msgid "The classname of a custom <literal>CacheProvider</literal>."
msgstr ""
#. Tag: para
-#: configuration.xml:752
#, no-c-format
msgid "<emphasis role=\"strong\">e.g.</emphasis> <literal>classname.of.CacheProvider</literal>"
msgstr ""
-#. Tag: literal
-#: configuration.xml:760
+#. Tag: para
#, no-c-format
-msgid "hibernate.cache.use_minimal_puts"
+msgid "<literal>hibernate.cache.use_minimal_puts</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:762
+#. Tag: para
#, no-c-format
msgid "Optimizes second-level cache operation to minimize writes, at the cost of more frequent reads. This setting is most useful for clustered caches and, in Hibernate3, is enabled by default for clustered cache implementations."
msgstr ""
-#. Tag: literal
-#: configuration.xml:775
+#. Tag: para
#, no-c-format
-msgid "hibernate.cache.use_query_cache"
+msgid "<literal>hibernate.cache.use_query_cache</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:777
+#. Tag: para
#, no-c-format
msgid "Enables the query cache. Individual queries still have to be set cachable."
msgstr ""
-#. Tag: literal
-#: configuration.xml:787
+#. Tag: para
#, no-c-format
-msgid "hibernate.cache.use_second_level_cache"
+msgid "<literal>hibernate.cache.use_second_level_cache</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:789
+#. Tag: para
#, no-c-format
msgid "Can be used to completely disable the second level cache, which is enabled by default for classes which specify a <literal><cache></literal> mapping."
msgstr ""
-#. Tag: literal
-#: configuration.xml:801
+#. Tag: para
#, no-c-format
-msgid "hibernate.cache.query_cache_factory"
+msgid "<literal>hibernate.cache.query_cache_factory</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:803
+#. Tag: para
#, no-c-format
msgid "The classname of a custom <literal>QueryCache</literal> interface, defaults to the built-in <literal>StandardQueryCache</literal>."
msgstr ""
#. Tag: para
-#: configuration.xml:806
#, no-c-format
msgid "<emphasis role=\"strong\">e.g.</emphasis> <literal>classname.of.QueryCache</literal>"
msgstr ""
-#. Tag: literal
-#: configuration.xml:814
+#. Tag: para
#, no-c-format
-msgid "hibernate.cache.region_prefix"
+msgid "<literal>hibernate.cache.region_prefix</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:816
+#. Tag: para
#, no-c-format
msgid "A prefix to use for second-level cache region names."
msgstr ""
#. Tag: para
-#: configuration.xml:818
#, no-c-format
msgid "<emphasis role=\"strong\">e.g.</emphasis> <literal>prefix</literal>"
msgstr ""
-#. Tag: literal
-#: configuration.xml:826
+#. Tag: para
#, no-c-format
-msgid "hibernate.cache.use_structured_entries"
+msgid "<literal>hibernate.cache.use_structured_entries</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:828
+#. Tag: para
#, no-c-format
msgid "Forces Hibernate to store data in the second-level cache in a more human-friendly format."
msgstr ""
#. Tag: title
-#: configuration.xml:842
#, no-c-format
msgid "Hibernate Transaction Properties"
msgstr ""
-#. Tag: literal
-#: configuration.xml:855
+#. Tag: para
#, no-c-format
-msgid "hibernate.transaction.factory_class"
+msgid "<literal>hibernate.transaction.factory_class</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:857
+#. Tag: para
#, no-c-format
msgid "The classname of a <literal>TransactionFactory</literal> to use with Hibernate <literal>Transaction</literal> API (defaults to <literal>JDBCTransactionFactory</literal>)."
msgstr ""
#. Tag: para
-#: configuration.xml:861
#, no-c-format
msgid "<emphasis role=\"strong\">e.g.</emphasis> <literal>classname.of.TransactionFactory</literal>"
msgstr ""
-#. Tag: literal
-#: configuration.xml:869
+#. Tag: para
#, no-c-format
-msgid "jta.UserTransaction"
+msgid "<literal>jta.UserTransaction</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:871
+#. Tag: para
#, no-c-format
msgid "A JNDI name used by <literal>JTATransactionFactory</literal> to obtain the JTA <literal>UserTransaction</literal> from the application server."
msgstr ""
-#. Tag: literal
-#: configuration.xml:883
+#. Tag: para
#, no-c-format
-msgid "hibernate.transaction.manager_lookup_class"
+msgid "<literal>hibernate.transaction. manager_lookup_class</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:885
+#. Tag: para
#, no-c-format
msgid "The classname of a <literal>TransactionManagerLookup</literal>. It is required when JVM-level caching is enabled or when using hilo generator in a JTA environment."
msgstr ""
#. Tag: para
-#: configuration.xml:889
#, no-c-format
msgid "<emphasis role=\"strong\">e.g.</emphasis> <literal>classname.of.TransactionManagerLookup</literal>"
msgstr ""
-#. Tag: literal
-#: configuration.xml:897
+#. Tag: para
#, no-c-format
-msgid "hibernate.transaction.flush_before_completion"
+msgid "<literal>hibernate.transaction. flush_before_completion</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:899
+#. Tag: para
#, no-c-format
-msgid "If enabled, the session will be automatically flushed during the before completion phase of the transaction. Built-in and automatic session context management is preferred, see <xref linkend=\"architecture-current-session\"/>."
+msgid "If enabled, the session will be automatically flushed during the before completion phase of the transaction. Built-in and automatic session context management is preferred, see <xref linkend=\"architecture-current-session\" />."
msgstr ""
-#. Tag: literal
-#: configuration.xml:912
+#. Tag: para
#, no-c-format
-msgid "hibernate.transaction.auto_close_session"
+msgid "<literal>hibernate.transaction. auto_close_session</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:914
+#. Tag: para
#, no-c-format
-msgid "If enabled, the session will be automatically closed during the after completion phase of the transaction. Built-in and automatic session context management is preferred, see <xref linkend=\"architecture-current-session\"/>."
+msgid "If enabled, the session will be automatically closed during the after completion phase of the transaction. Built-in and automatic session context management is preferred, see <xref linkend=\"architecture-current-session\" />."
msgstr ""
#. Tag: title
-#: configuration.xml:930
#, no-c-format
msgid "Miscellaneous Properties"
msgstr ""
-#. Tag: literal
-#: configuration.xml:943
+#. Tag: para
#, no-c-format
-msgid "hibernate.current_session_context_class"
+msgid "<literal>hibernate. current_session_context_class</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:945
+#. Tag: para
#, no-c-format
-msgid "Supply a custom strategy for the scoping of the \"current\" <literal>Session</literal>. See <xref linkend=\"architecture-current-session\"/> for more information about the built-in strategies."
+msgid "Supply a custom strategy for the scoping of the \"current\" <literal>Session</literal>. See <xref linkend=\"architecture-current-session\" /> for more information about the built-in strategies."
msgstr ""
#. Tag: para
-#: configuration.xml:950
#, no-c-format
msgid "<emphasis role=\"strong\">e.g.</emphasis> <literal>jta</literal> | <literal>thread</literal> | <literal>managed</literal> | <literal>custom.Class</literal>"
msgstr ""
-#. Tag: literal
-#: configuration.xml:959
+#. Tag: para
#, no-c-format
-msgid "hibernate.query.factory_class"
+msgid "<literal>hibernate.query.factory_class</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:961
+#. Tag: para
#, no-c-format
msgid "Chooses the HQL parser implementation."
msgstr ""
#. Tag: para
-#: configuration.xml:963
#, no-c-format
msgid "<emphasis role=\"strong\">e.g.</emphasis> <literal>org.hibernate.hql.ast.ASTQueryTranslatorFactory</literal> or <literal>org.hibernate.hql.classic.ClassicQueryTranslatorFactory</literal>"
msgstr ""
-#. Tag: literal
-#: configuration.xml:972
+#. Tag: para
#, no-c-format
-msgid "hibernate.query.substitutions"
+msgid "<literal>hibernate.query.substitutions</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:974
+#. Tag: para
#, no-c-format
msgid "Is used to map from tokens in Hibernate queries to SQL tokens (tokens might be function or literal names, for example)."
msgstr ""
#. Tag: para
-#: configuration.xml:977
#, no-c-format
msgid "<emphasis role=\"strong\">e.g.</emphasis> <literal>hqlLiteral=SQL_LITERAL, hqlFunction=SQLFUNC</literal>"
msgstr ""
-#. Tag: literal
-#: configuration.xml:985
+#. Tag: para
#, no-c-format
-msgid "hibernate.hbm2ddl.auto"
+msgid "<literal>hibernate.hbm2ddl.auto</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:987
+#. Tag: para
#, no-c-format
msgid "Automatically validates or exports schema DDL to the database when the <literal>SessionFactory</literal> is created. With <literal>create-drop</literal>, the database schema will be dropped when the <literal>SessionFactory</literal> is closed explicitly."
msgstr ""
#. Tag: para
-#: configuration.xml:993
#, no-c-format
msgid "<emphasis role=\"strong\">e.g.</emphasis> <literal>validate</literal> | <literal>update</literal> | <literal>create</literal> | <literal>create-drop</literal>"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1002
+#. Tag: para
#, no-c-format
-msgid "hibernate.cglib.use_reflection_optimizer"
+msgid "<literal>hibernate.cglib. use_reflection_optimizer</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1004
+#. Tag: para
#, no-c-format
msgid "Enables the use of CGLIB instead of runtime reflection (System-level property). Reflection can sometimes be useful when troubleshooting. Hibernate always requires CGLIB even if you turn off the optimizer. You cannot set this property in <literal>hibernate.cfg.xml</literal>."
msgstr ""
#. Tag: title
-#: configuration.xml:1020
#, no-c-format
msgid "SQL Dialects"
msgstr ""
#. Tag: para
-#: configuration.xml:1022
#, no-c-format
msgid "Always set the <literal>hibernate.dialect</literal> property to the correct <literal>org.hibernate.dialect.Dialect</literal> subclass for your database. If you specify a dialect, Hibernate will use sensible defaults for some of the other properties listed above. This means that you will not have to specify them manually."
msgstr ""
#. Tag: title
-#: configuration.xml:1030
#, no-c-format
msgid "Hibernate SQL Dialects (<literal>hibernate.dialect</literal>)"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1036
+#. Tag: para
#, no-c-format
msgid "RDBMS"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1037
+#. Tag: para
#, no-c-format
msgid "Dialect"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1042
+#. Tag: para
#, no-c-format
-msgid "<entry>DB2</entry>"
+msgid "DB2"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1042
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.dialect.DB2Dialect"
+msgid "<literal>org.hibernate.dialect.DB2Dialect</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1045
+#. Tag: para
#, no-c-format
msgid "DB2 AS/400"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1045
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.dialect.DB2400Dialect"
+msgid "<literal>org.hibernate.dialect.DB2400Dialect</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1048
+#. Tag: para
#, no-c-format
msgid "DB2 OS390"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1048
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.dialect.DB2390Dialect"
+msgid "<literal>org.hibernate.dialect.DB2390Dialect</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1051
+#. Tag: para
#, no-c-format
msgid "PostgreSQL"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1051
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.dialect.PostgreSQLDialect"
+msgid "<literal>org.hibernate.dialect.PostgreSQLDialect</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1054
+#. Tag: para
#, no-c-format
msgid "MySQL"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1054
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.dialect.MySQLDialect"
+msgid "<literal>org.hibernate.dialect.MySQLDialect</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1057
+#. Tag: para
#, no-c-format
msgid "MySQL with InnoDB"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1057
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.dialect.MySQLInnoDBDialect"
+msgid "<literal>org.hibernate.dialect.MySQLInnoDBDialect</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1060
+#. Tag: para
#, no-c-format
msgid "MySQL with MyISAM"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1060
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.dialect.MySQLMyISAMDialect"
+msgid "<literal>org.hibernate.dialect.MySQLMyISAMDialect</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1063
+#. Tag: para
#, no-c-format
msgid "Oracle (any version)"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1063
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.dialect.OracleDialect"
+msgid "<literal>org.hibernate.dialect.OracleDialect</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1066
+#. Tag: para
#, no-c-format
msgid "Oracle 9i"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1066
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.dialect.Oracle9iDialect"
+msgid "<literal>org.hibernate.dialect.Oracle9iDialect</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1069
+#. Tag: para
#, no-c-format
msgid "Oracle 10g"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1069
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.dialect.Oracle10gDialect"
+msgid "<literal>org.hibernate.dialect.Oracle10gDialect</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1072
+#. Tag: para
#, no-c-format
msgid "Sybase"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1072
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.dialect.SybaseDialect"
+msgid "<literal>org.hibernate.dialect.SybaseDialect</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1075
+#. Tag: para
#, no-c-format
msgid "Sybase Anywhere"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1075
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.dialect.SybaseAnywhereDialect"
+msgid "<literal>org.hibernate.dialect.SybaseAnywhereDialect</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1078
+#. Tag: para
#, no-c-format
msgid "Microsoft SQL Server"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1078
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.dialect.SQLServerDialect"
+msgid "<literal>org.hibernate.dialect.SQLServerDialect</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1081
+#. Tag: para
#, no-c-format
msgid "SAP DB"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1081
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.dialect.SAPDBDialect"
+msgid "<literal>org.hibernate.dialect.SAPDBDialect</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1084
+#. Tag: para
#, no-c-format
msgid "Informix"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1084
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.dialect.InformixDialect"
+msgid "<literal>org.hibernate.dialect.InformixDialect</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1087
+#. Tag: para
#, no-c-format
msgid "HypersonicSQL"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1087
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.dialect.HSQLDialect"
+msgid "<literal>org.hibernate.dialect.HSQLDialect</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1090
+#. Tag: para
#, no-c-format
msgid "Ingres"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1090
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.dialect.IngresDialect"
+msgid "<literal>org.hibernate.dialect.IngresDialect</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1093
+#. Tag: para
#, no-c-format
msgid "Progress"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1093
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.dialect.ProgressDialect"
+msgid "<literal>org.hibernate.dialect.ProgressDialect</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1096
+#. Tag: para
#, no-c-format
msgid "Mckoi SQL"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1096
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.dialect.MckoiDialect"
+msgid "<literal>org.hibernate.dialect.MckoiDialect</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1099
+#. Tag: para
#, no-c-format
msgid "Interbase"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1099
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.dialect.InterbaseDialect"
+msgid "<literal>org.hibernate.dialect.InterbaseDialect</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1102
+#. Tag: para
#, no-c-format
msgid "Pointbase"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1102
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.dialect.PointbaseDialect"
+msgid "<literal>org.hibernate.dialect.PointbaseDialect</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1105
+#. Tag: para
#, no-c-format
msgid "FrontBase"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1105
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.dialect.FrontbaseDialect"
+msgid "<literal>org.hibernate.dialect.FrontbaseDialect</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1108
+#. Tag: para
#, no-c-format
msgid "Firebird"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1108
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.dialect.FirebirdDialect"
+msgid "<literal>org.hibernate.dialect.FirebirdDialect</literal>"
msgstr ""
#. Tag: title
-#: configuration.xml:1117
#, no-c-format
msgid "Outer Join Fetching"
msgstr ""
#. Tag: para
-#: configuration.xml:1119
#, no-c-format
msgid "If your database supports ANSI, Oracle or Sybase style outer joins, <emphasis>outer join fetching</emphasis> will often increase performance by limiting the number of round trips to and from the database. This is, however, at the cost of possibly more work performed by the database itself. Outer join fetching allows a whole graph of objects connected by many-to-one, one-to-many, many-to-many and one-to-one associations to be retrieved in a single SQL <literal>SELECT</literal>."
msgstr ""
#. Tag: para
-#: configuration.xml:1128
#, no-c-format
msgid "Outer join fetching can be disabled <emphasis>globally</emphasis> by setting the property <literal>hibernate.max_fetch_depth</literal> to <literal>0</literal>. A setting of <literal>1</literal> or higher enables outer join fetching for one-to-one and many-to-one associations that have been mapped with <literal>fetch=\"join\"</literal>."
msgstr ""
#. Tag: para
-#: configuration.xml:1136
#, no-c-format
-msgid "See <xref linkend=\"performance-fetching\"/> for more information."
+msgid "See <xref linkend=\"performance-fetching\" /> for more information."
msgstr ""
#. Tag: title
-#: configuration.xml:1143
#, no-c-format
msgid "Binary Streams"
msgstr ""
#. Tag: para
-#: configuration.xml:1145
#, no-c-format
msgid "Oracle limits the size of <literal>byte</literal> arrays that can be passed to and/or from its JDBC driver. If you wish to use large instances of <literal>binary</literal> or <literal>serializable</literal> type, you should enable <literal>hibernate.jdbc.use_streams_for_binary</literal>. <emphasis>This is a system-level setting only.</emphasis>"
msgstr ""
#. Tag: title
-#: configuration.xml:1156
#, no-c-format
msgid "Second-level and query cache"
msgstr ""
#. Tag: para
-#: configuration.xml:1158
#, no-c-format
-msgid "The properties prefixed by <literal>hibernate.cache</literal> allow you to use a process or cluster scoped second-level cache system with Hibernate. See the <xref linkend=\"performance-cache\"/> for more information."
+msgid "The properties prefixed by <literal>hibernate.cache</literal> allow you to use a process or cluster scoped second-level cache system with Hibernate. See the <xref linkend=\"performance-cache\" /> for more information."
msgstr ""
#. Tag: title
-#: configuration.xml:1168
#, no-c-format
msgid "Query Language Substitution"
msgstr ""
#. Tag: para
-#: configuration.xml:1170
#, no-c-format
msgid "You can define new Hibernate query tokens using <literal>hibernate.query.substitutions</literal>. For example:"
msgstr ""
-#. Tag: programlisting
-#: configuration.xml:1175
-#, no-c-format
-msgid "hibernate.query.substitutions true=1, false=0"
-msgstr ""
-
#. Tag: para
-#: configuration.xml:1177
#, no-c-format
msgid "This would cause the tokens <literal>true</literal> and <literal>false</literal> to be translated to integer literals in the generated SQL."
msgstr ""
-#. Tag: programlisting
-#: configuration.xml:1182
-#, no-c-format
-msgid "hibernate.query.substitutions toLowercase=LOWER"
-msgstr ""
-
#. Tag: para
-#: configuration.xml:1184
#, no-c-format
msgid "This would allow you to rename the SQL <literal>LOWER</literal> function."
msgstr ""
#. Tag: title
-#: configuration.xml:1191
#, no-c-format
msgid "Hibernate statistics"
msgstr ""
#. Tag: para
-#: configuration.xml:1193
#, no-c-format
msgid "If you enable <literal>hibernate.generate_statistics</literal>, Hibernate exposes a number of metrics that are useful when tuning a running system via <literal>SessionFactory.getStatistics()</literal>. Hibernate can even be configured to expose these statistics via JMX. Read the Javadoc of the interfaces in <literal>org.hibernate.stats</literal> for more information."
msgstr ""
#. Tag: title
-#: configuration.xml:1205
#, no-c-format
msgid "Logging"
msgstr ""
#. Tag: para
-#: configuration.xml:1207
#, no-c-format
msgid "Hibernate utilizes <ulink url=\"http://www.slf4j.org/\">Simple Logging Facade for Java</ulink> (SLF4J) in order to log various system events. SLF4J can direct your logging output to several logging frameworks (NOP, Simple, log4j version 1.2, JDK 1.4 logging, JCL or logback) depending on your chosen binding. In order to setup logging you will need <filename>slf4j-api.jar</filename> in your classpath together with the jar file for your preferred binding - <filename>slf4j-log4j12.jar</filename> in the case of Log4J. See the SLF4J <ulink url=\"http://www.slf4j.org/manual.html\">documentation</ulink> for more detail. To use Log4j you will also need to place a <filename>log4j.properties</filename> file in your classpath. An example properties file is distributed with Hibernate in the <literal>src/</literal> directory."
msgstr ""
#. Tag: para
-#: configuration.xml:1218
#, no-c-format
msgid "It is recommended that you familiarize yourself with Hibernate's log messages. A lot of work has been put into making the Hibernate log as detailed as possible, without making it unreadable. It is an essential troubleshooting device. The most interesting log categories are the following:"
msgstr ""
#. Tag: title
-#: configuration.xml:1227
#, no-c-format
msgid "Hibernate Log Categories"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1233
+#. Tag: para
#, no-c-format
msgid "Category"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1234
+#. Tag: para
#, no-c-format
msgid "Function"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1239
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.SQL"
+msgid "<literal>org.hibernate.SQL</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1240
+#. Tag: para
#, no-c-format
msgid "Log all SQL DML statements as they are executed"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1243
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.type"
+msgid "<literal>org.hibernate.type</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1244
+#. Tag: para
#, no-c-format
msgid "Log all JDBC parameters"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1247
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.tool.hbm2ddl"
+msgid "<literal>org.hibernate.tool. hbm2ddl</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1248
+#. Tag: para
#, no-c-format
msgid "Log all SQL DDL statements as they are executed"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1251
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.pretty"
+msgid "<literal>org.hibernate.pretty</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1252
+#. Tag: para
#, no-c-format
msgid "Log the state of all entities (max 20 entities) associated with the session at flush time"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1258
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.cache"
+msgid "<literal>org.hibernate.cache</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1259
+#. Tag: para
#, no-c-format
msgid "Log all second-level cache activity"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1262
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.transaction"
+msgid "<literal>org.hibernate. transaction</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1263
+#. Tag: para
#, no-c-format
msgid "Log transaction related activity"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1266
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.jdbc"
+msgid "<literal>org.hibernate.jdbc</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1267
+#. Tag: para
#, no-c-format
msgid "Log all JDBC resource acquisition"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1270
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.hql.ast.AST"
+msgid "<literal>org.hibernate.hql. ast.AST</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1271
+#. Tag: para
#, no-c-format
msgid "Log HQL and SQL ASTs during query parsing"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1276
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.secure"
+msgid "<literal>org.hibernate.secure</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1277
+#. Tag: para
#, no-c-format
msgid "Log all JAAS authorization requests"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1280
+#. Tag: para
#, no-c-format
-msgid "org.hibernate"
+msgid "<literal>org.hibernate</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1281
+#. Tag: para
#, no-c-format
msgid "Log everything. This is a lot of information but it is useful for troubleshooting"
msgstr ""
#. Tag: para
-#: configuration.xml:1290
#, no-c-format
msgid "When developing applications with Hibernate, you should almost always work with <literal>debug</literal> enabled for the category <literal>org.hibernate.SQL</literal>, or, alternatively, the property <literal>hibernate.show_sql</literal> enabled."
msgstr ""
#. Tag: title
-#: configuration.xml:1300
#, no-c-format
msgid "Implementing a <literal>NamingStrategy</literal>"
msgstr ""
#. Tag: para
-#: configuration.xml:1302
#, no-c-format
msgid "The interface <literal>org.hibernate.cfg.NamingStrategy</literal> allows you to specify a \"naming standard\" for database objects and schema elements."
msgstr ""
#. Tag: para
-#: configuration.xml:1307
#, no-c-format
msgid "You can provide rules for automatically generating database identifiers from Java identifiers or for processing \"logical\" column and table names given in the mapping file into \"physical\" table and column names. This feature helps reduce the verbosity of the mapping document, eliminating repetitive noise (<literal>TBL_</literal> prefixes, for example). The default strategy used by Hibernate is quite minimal."
msgstr ""
#. Tag: para
-#: configuration.xml:1316
#, no-c-format
msgid "You can specify a different strategy by calling <literal>Configuration.setNamingStrategy()</literal> before adding mappings:"
msgstr ""
-#. Tag: programlisting
-#: configuration.xml:1321
-#, no-c-format
-msgid ""
- "<![CDATA[SessionFactory sf = new Configuration()\n"
- " .setNamingStrategy(ImprovedNamingStrategy.INSTANCE)\n"
- " .addFile(\"Item.hbm.xml\")\n"
- " .addFile(\"Bid.hbm.xml\")\n"
- " .buildSessionFactory();]]>"
-msgstr ""
-
#. Tag: para
-#: configuration.xml:1323
#, no-c-format
msgid "<literal>org.hibernate.cfg.ImprovedNamingStrategy</literal> is a built-in strategy that might be a useful starting point for some applications."
msgstr ""
#. Tag: title
-#: configuration.xml:1331
#, no-c-format
msgid "XML configuration file"
msgstr ""
#. Tag: para
-#: configuration.xml:1333
#, no-c-format
msgid "An alternative approach to configuration is to specify a full configuration in a file named <literal>hibernate.cfg.xml</literal>. This file can be used as a replacement for the <literal>hibernate.properties</literal> file or, if both are present, to override properties."
msgstr ""
#. Tag: para
-#: configuration.xml:1340
#, no-c-format
msgid "The XML configuration file is by default expected to be in the root of your <literal>CLASSPATH</literal>. Here is an example:"
msgstr ""
-#. Tag: programlisting
-#: configuration.xml:1345
-#, no-c-format
-msgid ""
- "<![CDATA[<?xml version='1.0' encoding='utf-8'?>\n"
- "<!DOCTYPE hibernate-configuration PUBLIC\n"
- " \"-//Hibernate/Hibernate Configuration DTD//EN\"\n"
- " \"http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd\">\n"
- "\n"
- "<hibernate-configuration>\n"
- "\n"
- " <!-- a SessionFactory instance listed as /jndi/name -->\n"
- " <session-factory\n"
- " name=\"java:hibernate/SessionFactory\">\n"
- "\n"
- " <!-- properties -->\n"
- " <property name=\"connection.datasource\">java:/comp/env/jdbc/MyDB</property>\n"
- " <property name=\"dialect\">org.hibernate.dialect.MySQLDialect</property>\n"
- " <property name=\"show_sql\">false</property>\n"
- " <property name=\"transaction.factory_class\">\n"
- " org.hibernate.transaction.JTATransactionFactory\n"
- " </property>\n"
- " <property name=\"jta.UserTransaction\">java:comp/UserTransaction</property>\n"
- "\n"
- " <!-- mapping files -->\n"
- " <mapping resource=\"org/hibernate/auction/Item.hbm.xml\"/>\n"
- " <mapping resource=\"org/hibernate/auction/Bid.hbm.xml\"/>\n"
- "\n"
- " <!-- cache settings -->\n"
- " <class-cache class=\"org.hibernate.auction.Item\" usage=\"read-write\"/>\n"
- " <class-cache class=\"org.hibernate.auction.Bid\" usage=\"read-only\"/>\n"
- " <collection-cache collection=\"org.hibernate.auction.Item.bids\" usage=\"read-write\"/>\n"
- "\n"
- " </session-factory>\n"
- "\n"
- "</hibernate-configuration>]]>"
-msgstr ""
-
#. Tag: para
-#: configuration.xml:1347
#, no-c-format
msgid "The advantage of this approach is the externalization of the mapping file names to configuration. The <literal>hibernate.cfg.xml</literal> is also more convenient once you have to tune the Hibernate cache. It is your choice to use either <literal>hibernate.properties</literal> or <literal>hibernate.cfg.xml</literal>. Both are equivalent, except for the above mentioned benefits of using the XML syntax."
msgstr ""
#. Tag: para
-#: configuration.xml:1356
#, no-c-format
msgid "With the XML configuration, starting Hibernate is then as simple as:"
msgstr ""
-#. Tag: programlisting
-#: configuration.xml:1360
-#, no-c-format
-msgid "<![CDATA[SessionFactory sf = new Configuration().configure().buildSessionFactory();]]>"
-msgstr ""
-
#. Tag: para
-#: configuration.xml:1362
#, no-c-format
msgid "You can select a different XML configuration file using:"
msgstr ""
-#. Tag: programlisting
-#: configuration.xml:1366
-#, no-c-format
-msgid ""
- "<![CDATA[SessionFactory sf = new Configuration()\n"
- " .configure(\"catdb.cfg.xml\")\n"
- " .buildSessionFactory();]]>"
-msgstr ""
-
#. Tag: title
-#: configuration.xml:1371
#, no-c-format
msgid "J2EE Application Server integration"
msgstr ""
#. Tag: para
-#: configuration.xml:1373
#, no-c-format
msgid "Hibernate has the following integration points for J2EE infrastructure:"
msgstr ""
#. Tag: para
-#: configuration.xml:1379
#, no-c-format
msgid "<emphasis>Container-managed datasources</emphasis>: Hibernate can use JDBC connections managed by the container and provided through JNDI. Usually, a JTA compatible <literal>TransactionManager</literal> and a <literal>ResourceManager</literal> take care of transaction management (CMT), especially distributed transaction handling across several datasources. You can also demarcate transaction boundaries programmatically (BMT), or you might want to use the optional Hibernate <literal>Transaction</literal> API for this to keep your code portable."
msgstr ""
#. Tag: para
-#: configuration.xml:1394
#, no-c-format
msgid "<emphasis>Automatic JNDI binding</emphasis>: Hibernate can bind its <literal>SessionFactory</literal> to JNDI after startup."
msgstr ""
#. Tag: para
-#: configuration.xml:1403
#, no-c-format
msgid "<emphasis>JTA Session binding:</emphasis> the Hibernate <literal>Session</literal> can be automatically bound to the scope of JTA transactions. Simply lookup the <literal>SessionFactory</literal> from JNDI and get the current <literal>Session</literal>. Let Hibernate manage flushing and closing the <literal>Session</literal> when your JTA transaction completes. Transaction demarcation is either declarative (CMT) or programmatic (BMT/UserTransaction)."
msgstr ""
#. Tag: para
-#: configuration.xml:1416
#, no-c-format
msgid "<emphasis>JMX deployment:</emphasis> if you have a JMX capable application server (e.g. JBoss AS), you can choose to deploy Hibernate as a managed MBean. This saves you the one line startup code to build your <literal>SessionFactory</literal> from a <literal>Configuration</literal>. The container will startup your <literal>HibernateService</literal> and also take care of service dependencies (datasource has to be available before Hibernate starts, etc)."
msgstr ""
#. Tag: para
-#: configuration.xml:1427
#, no-c-format
msgid "Depending on your environment, you might have to set the configuration option <literal>hibernate.connection.aggressive_release</literal> to true if your application server shows \"connection containment\" exceptions."
msgstr ""
#. Tag: title
-#: configuration.xml:1434
#, no-c-format
msgid "Transaction strategy configuration"
msgstr ""
#. Tag: para
-#: configuration.xml:1436
#, no-c-format
msgid "The Hibernate <literal>Session</literal> API is independent of any transaction demarcation system in your architecture. If you let Hibernate use JDBC directly through a connection pool, you can begin and end your transactions by calling the JDBC API. If you run in a J2EE application server, you might want to use bean-managed transactions and call the JTA API and <literal>UserTransaction</literal> when needed."
msgstr ""
#. Tag: para
-#: configuration.xml:1444
#, no-c-format
msgid "To keep your code portable between these two (and other) environments we recommend the optional Hibernate <literal>Transaction</literal> API, which wraps and hides the underlying system. You have to specify a factory class for <literal>Transaction</literal> instances by setting the Hibernate configuration property <literal>hibernate.transaction.factory_class</literal>."
msgstr ""
#. Tag: para
-#: configuration.xml:1451
#, no-c-format
msgid "There are three standard, or built-in, choices:"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1457
+#. Tag: term
#, no-c-format
-msgid "org.hibernate.transaction.JDBCTransactionFactory"
+msgid "<literal>org.hibernate.transaction.JDBCTransactionFactory</literal>"
msgstr ""
#. Tag: para
-#: configuration.xml:1459
#, no-c-format
msgid "delegates to database (JDBC) transactions (default)"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1463
+#. Tag: term
#, no-c-format
-msgid "org.hibernate.transaction.JTATransactionFactory"
+msgid "<literal>org.hibernate.transaction.JTATransactionFactory</literal>"
msgstr ""
#. Tag: para
-#: configuration.xml:1465
#, no-c-format
msgid "delegates to container-managed transactions if an existing transaction is underway in this context (for example, EJB session bean method). Otherwise, a new transaction is started and bean-managed transactions are used."
msgstr ""
-#. Tag: literal
-#: configuration.xml:1473
+#. Tag: term
#, no-c-format
-msgid "org.hibernate.transaction.CMTTransactionFactory"
+msgid "<literal>org.hibernate.transaction.CMTTransactionFactory</literal>"
msgstr ""
#. Tag: para
-#: configuration.xml:1475
#, no-c-format
msgid "delegates to container-managed JTA transactions"
msgstr ""
#. Tag: para
-#: configuration.xml:1480
#, no-c-format
msgid "You can also define your own transaction strategies (for a CORBA transaction service, for example)."
msgstr ""
#. Tag: para
-#: configuration.xml:1485
#, no-c-format
msgid "Some features in Hibernate (i.e., the second level cache, Contextual Sessions with JTA, etc.) require access to the JTA <literal>TransactionManager</literal> in a managed environment. In an application server, since J2EE does not standardize a single mechanism, you have to specify how Hibernate should obtain a reference to the <literal>TransactionManager</literal>:"
msgstr ""
#. Tag: title
-#: configuration.xml:1493
#, no-c-format
msgid "JTA TransactionManagers"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1499
+#. Tag: para
#, no-c-format
msgid "Transaction Factory"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1500
+#. Tag: para
#, no-c-format
msgid "Application Server"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1505
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.transaction.JBossTransactionManagerLookup"
+msgid "<literal>org.hibernate.transaction. JBossTransactionManagerLookup</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1506
+#. Tag: para
#, no-c-format
msgid "JBoss"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1509
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.transaction.WeblogicTransactionManagerLookup"
+msgid "<literal>org.hibernate.transaction. WeblogicTransactionManagerLookup</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1510
+#. Tag: para
#, no-c-format
msgid "Weblogic"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1513
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.transaction.WebSphereTransactionManagerLookup"
+msgid "<literal>org.hibernate.transaction. WebSphereTransactionManagerLookup</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1514
+#. Tag: para
#, no-c-format
msgid "WebSphere"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1517
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.transaction.WebSphereExtendedJTATransactionLookup"
+msgid "<literal>org.hibernate.transaction. WebSphereExtendedJTATransactionLookup</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1518
+#. Tag: para
#, no-c-format
msgid "WebSphere 6"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1521
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.transaction.OrionTransactionManagerLookup"
+msgid "<literal>org.hibernate.transaction. OrionTransactionManagerLookup</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1522
+#. Tag: para
#, no-c-format
msgid "Orion"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1525
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.transaction.ResinTransactionManagerLookup"
+msgid "<literal>org.hibernate.transaction. ResinTransactionManagerLookup</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1526
+#. Tag: para
#, no-c-format
msgid "Resin"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1529
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.transaction.JOTMTransactionManagerLookup"
+msgid "<literal>org.hibernate.transaction. JOTMTransactionManagerLookup</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1530
+#. Tag: para
#, no-c-format
msgid "JOTM"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1533
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.transaction.JOnASTransactionManagerLookup"
+msgid "<literal>org.hibernate.transaction. JOnASTransactionManagerLookup</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1534
+#. Tag: para
#, no-c-format
msgid "JOnAS"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1537
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.transaction.JRun4TransactionManagerLookup"
+msgid "<literal>org.hibernate.transaction. JRun4TransactionManagerLookup</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1538
+#. Tag: para
#, no-c-format
msgid "JRun4"
msgstr ""
-#. Tag: literal
-#: configuration.xml:1541
+#. Tag: para
#, no-c-format
-msgid "org.hibernate.transaction.BESTransactionManagerLookup"
+msgid "<literal>org.hibernate.transaction. BESTransactionManagerLookup</literal>"
msgstr ""
-#. Tag: entry
-#: configuration.xml:1542
+#. Tag: para
#, no-c-format
msgid "Borland ES"
msgstr ""
#. Tag: title
-#: configuration.xml:1551
#, no-c-format
msgid "JNDI-bound <literal>SessionFactory</literal>"
msgstr ""
#. Tag: para
-#: configuration.xml:1553
#, no-c-format
msgid "A JNDI-bound Hibernate <literal>SessionFactory</literal> can simplify the lookup function of the factory and create new <literal>Session</literal>s. This is not, however, related to a JNDI bound <literal>Datasource</literal>; both simply use the same registry."
msgstr ""
#. Tag: para
-#: configuration.xml:1560
#, no-c-format
msgid "If you wish to have the <literal>SessionFactory</literal> bound to a JNDI namespace, specify a name (e.g. <literal>java:hibernate/SessionFactory</literal>) using the property <literal>hibernate.session_factory_name</literal>. If this property is omitted, the <literal>SessionFactory</literal> will not be bound to JNDI. This is especially useful in environments with a read-only JNDI default implementation (in Tomcat, for example)."
msgstr ""
#. Tag: para
-#: configuration.xml:1568
#, no-c-format
msgid "When binding the <literal>SessionFactory</literal> to JNDI, Hibernate will use the values of <literal>hibernate.jndi.url</literal>, <literal>hibernate.jndi.class</literal> to instantiate an initial context. If they are not specified, the default <literal>InitialContext</literal> will be used."
msgstr ""
#. Tag: para
-#: configuration.xml:1575
#, no-c-format
msgid "Hibernate will automatically place the <literal>SessionFactory</literal> in JNDI after you call <literal>cfg.buildSessionFactory()</literal>. This means you will have this call in some startup code, or utility class in your application, unless you use JMX deployment with the <literal>HibernateService</literal> (this is discussed later in greater detail)."
msgstr ""
#. Tag: para
-#: configuration.xml:1582
#, no-c-format
msgid "If you use a JNDI <literal>SessionFactory</literal>, an EJB or any other class, you can obtain the <literal>SessionFactory</literal> using a JNDI lookup."
msgstr ""
#. Tag: para
-#: configuration.xml:1587
#, no-c-format
msgid "It is recommended that you bind the <literal>SessionFactory</literal> to JNDI in a managed environment and use a <literal>static</literal> singleton otherwise. To shield your application code from these details, we also recommend to hide the actual lookup code for a <literal>SessionFactory</literal> in a helper class, such as <literal>HibernateUtil.getSessionFactory()</literal>. Note that such a class is also a convenient way to startup Hibernate—see chapter 1."
msgstr ""
#. Tag: title
-#: configuration.xml:1599
#, no-c-format
msgid "Current Session context management with JTA"
msgstr ""
#. Tag: para
-#: configuration.xml:1601
#, no-c-format
-msgid "The easiest way to handle <literal>Sessions</literal> and transactions is Hibernate's automatic \"current\" <literal>Session</literal> management. For a discussion of contextual sessions see <xref linkend=\"architecture-current-session\"/>. Using the <literal>\"jta\"</literal> session context, if there is no Hibernate <literal>Session</literal> associated with the current JTA transaction, one will be started and associated with that JTA transaction the first time you call <literal>sessionFactory.getCurrentSession()</literal>. The <literal>Session</literal>s retrieved via <literal>getCurrentSession()</literal> in the<literal>\"jta\"</literal> context are set to automatically flush before the transaction completes, close after the transaction completes, and aggressively release JDBC connections after each statement. This allows the <literal>Session</literal>s to be managed by the life cycle of the JTA transaction to which it is associated, keeping user code clean of su!
ch management concerns. Your code can either use JTA programmatically through <literal>UserTransaction</literal>, or (recommended for portable code) use the Hibernate <literal>Transaction</literal> API to set transaction boundaries. If you run in an EJB container, declarative transaction demarcation with CMT is preferred."
+msgid "The easiest way to handle <literal>Sessions</literal> and transactions is Hibernate's automatic \"current\" <literal>Session</literal> management. For a discussion of contextual sessions see <xref linkend=\"architecture-current-session\" />. Using the <literal>\"jta\"</literal> session context, if there is no Hibernate <literal>Session</literal> associated with the current JTA transaction, one will be started and associated with that JTA transaction the first time you call <literal>sessionFactory.getCurrentSession()</literal>. The <literal>Session</literal>s retrieved via <literal>getCurrentSession()</literal> in the<literal>\"jta\"</literal> context are set to automatically flush before the transaction completes, close after the transaction completes, and aggressively release JDBC connections after each statement. This allows the <literal>Session</literal>s to be managed by the life cycle of the JTA transaction to which it is associated, keeping user code clean of s!
uch management concerns. Your code can either use JTA programmatically through <literal>UserTransaction</literal>, or (recommended for portable code) use the Hibernate <literal>Transaction</literal> API to set transaction boundaries. If you run in an EJB container, declarative transaction demarcation with CMT is preferred."
msgstr ""
#. Tag: title
-#: configuration.xml:1624
#, no-c-format
msgid "JMX deployment"
msgstr ""
#. Tag: para
-#: configuration.xml:1626
#, no-c-format
msgid "The line <literal>cfg.buildSessionFactory()</literal> still has to be executed somewhere to get a <literal>SessionFactory</literal> into JNDI. You can do this either in a <literal>static</literal> initializer block, like the one in <literal>HibernateUtil</literal>, or you can deploy Hibernate as a <emphasis>managed service</emphasis>."
msgstr ""
#. Tag: para
-#: configuration.xml:1634
#, no-c-format
msgid "Hibernate is distributed with <literal>org.hibernate.jmx.HibernateService</literal> for deployment on an application server with JMX capabilities, such as JBoss AS. The actual deployment and configuration is vendor-specific. Here is an example <literal>jboss-service.xml</literal> for JBoss 4.0.x:"
msgstr ""
-#. Tag: programlisting
-#: configuration.xml:1641
-#, no-c-format
-msgid ""
- "<![CDATA[<?xml version=\"1.0\"?>\n"
- "<server>\n"
- "\n"
- "<mbean code=\"org.hibernate.jmx.HibernateService\"\n"
- " name=\"jboss.jca:service=HibernateFactory,name=HibernateFactory\">\n"
- "\n"
- " <!-- Required services -->\n"
- " <depends>jboss.jca:service=RARDeployer</depends>\n"
- " <depends>jboss.jca:service=LocalTxCM,name=HsqlDS</depends>\n"
- "\n"
- " <!-- Bind the Hibernate service to JNDI -->\n"
- " <attribute name=\"JndiName\">java:/hibernate/SessionFactory</attribute>\n"
- "\n"
- " <!-- Datasource settings -->\n"
- " <attribute name=\"Datasource\">java:HsqlDS</attribute>\n"
- " <attribute name=\"Dialect\">org.hibernate.dialect.HSQLDialect</attribute>\n"
- "\n"
- " <!-- Transaction integration -->\n"
- " <attribute name=\"TransactionStrategy\">\n"
- " org.hibernate.transaction.JTATransactionFactory</attribute>\n"
- " <attribute name=\"TransactionManagerLookupStrategy\">\n"
- " org.hibernate.transaction.JBossTransactionManagerLookup</attribute>\n"
- " <attribute name=\"FlushBeforeCompletionEnabled\">true</attribute>\n"
- " <attribute name=\"AutoCloseSessionEnabled\">true</attribute>\n"
- "\n"
- " <!-- Fetching options -->\n"
- " <attribute name=\"MaximumFetchDepth\">5</attribute>\n"
- "\n"
- " <!-- Second-level caching -->\n"
- " <attribute name=\"SecondLevelCacheEnabled\">true</attribute>\n"
- " <attribute name=\"CacheProviderClass\">org.hibernate.cache.EhCacheProvider</attribute>\n"
- " <attribute name=\"QueryCacheEnabled\">true</attribute>\n"
- "\n"
- " <!-- Logging -->\n"
- " <attribute name=\"ShowSqlEnabled\">true</attribute>\n"
- "\n"
- " <!-- Mapping files -->\n"
- " <attribute name=\"MapResources\">auction/Item.hbm.xml,auction/Category.hbm.xml</attribute>\n"
- "\n"
- "</mbean>\n"
- "\n"
- "</server>]]>"
-msgstr ""
-
#. Tag: para
-#: configuration.xml:1643
#, no-c-format
msgid "This file is deployed in a directory called <literal>META-INF</literal> and packaged in a JAR file with the extension <literal>.sar</literal> (service archive). You also need to package Hibernate, its required third-party libraries, your compiled persistent classes, as well as your mapping files in the same archive. Your enterprise beans (usually session beans) can be kept in their own JAR file, but you can include this EJB JAR file in the main service archive to get a single (hot-)deployable unit. Consult the JBoss AS documentation for more information about JMX service and EJB deployment."
msgstr ""
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/events.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/events.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/events.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,310 +1,128 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-10 21:02+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:19\n"
+"PO-Revision-Date: 2010-01-08T04:07:19\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
-#: events.xml:29
#, no-c-format
msgid "Interceptors and events"
msgstr ""
#. Tag: para
-#: events.xml:31
#, no-c-format
msgid "It is useful for the application to react to certain events that occur inside Hibernate. This allows for the implementation of generic functionality and the extension of Hibernate functionality."
msgstr ""
#. Tag: title
-#: events.xml:38
#, no-c-format
msgid "Interceptors"
msgstr ""
#. Tag: para
-#: events.xml:40
#, no-c-format
msgid "The <literal>Interceptor</literal> interface provides callbacks from the session to the application, allowing the application to inspect and/or manipulate properties of a persistent object before it is saved, updated, deleted or loaded. One possible use for this is to track auditing information. For example, the following <literal>Interceptor</literal> automatically sets the <literal>createTimestamp</literal> when an <literal>Auditable</literal> is created and updates the <literal>lastUpdateTimestamp</literal> property when an <literal>Auditable</literal> is updated."
msgstr ""
#. Tag: para
-#: events.xml:51
#, no-c-format
msgid "You can either implement <literal>Interceptor</literal> directly or extend <literal>EmptyInterceptor</literal>."
msgstr ""
-#. Tag: programlisting
-#: events.xml:56
-#, no-c-format
-msgid ""
- "<![CDATA[package org.hibernate.test;\n"
- "\n"
- "import java.io.Serializable;\n"
- "import java.util.Date;\n"
- "import java.util.Iterator;\n"
- "\n"
- "import org.hibernate.EmptyInterceptor;\n"
- "import org.hibernate.Transaction;\n"
- "import org.hibernate.type.Type;\n"
- "\n"
- "public class AuditInterceptor extends EmptyInterceptor {\n"
- "\n"
- " private int updates;\n"
- " private int creates;\n"
- " private int loads;\n"
- "\n"
- " public void onDelete(Object entity,\n"
- " Serializable id,\n"
- " Object[] state,\n"
- " String[] propertyNames,\n"
- " Type[] types) {\n"
- " // do nothing\n"
- " }\n"
- "\n"
- " public boolean onFlushDirty(Object entity,\n"
- " Serializable id,\n"
- " Object[] currentState,\n"
- " Object[] previousState,\n"
- " String[] propertyNames,\n"
- " Type[] types) {\n"
- "\n"
- " if ( entity instanceof Auditable ) {\n"
- " updates++;\n"
- " for ( int i=0; i < propertyNames.length; i++ ) {\n"
- " if ( \"lastUpdateTimestamp\".equals( propertyNames[i] ) ) {\n"
- " currentState[i] = new Date();\n"
- " return true;\n"
- " }\n"
- " }\n"
- " }\n"
- " return false;\n"
- " }\n"
- "\n"
- " public boolean onLoad(Object entity,\n"
- " Serializable id,\n"
- " Object[] state,\n"
- " String[] propertyNames,\n"
- " Type[] types) {\n"
- " if ( entity instanceof Auditable ) {\n"
- " loads++;\n"
- " }\n"
- " return false;\n"
- " }\n"
- "\n"
- " public boolean onSave(Object entity,\n"
- " Serializable id,\n"
- " Object[] state,\n"
- " String[] propertyNames,\n"
- " Type[] types) {\n"
- "\n"
- " if ( entity instanceof Auditable ) {\n"
- " creates++;\n"
- " for ( int i=0; i<propertyNames.length; i++ ) {\n"
- " if ( \"createTimestamp\".equals( propertyNames[i] ) ) {\n"
- " state[i] = new Date();\n"
- " return true;\n"
- " }\n"
- " }\n"
- " }\n"
- " return false;\n"
- " }\n"
- "\n"
- " public void afterTransactionCompletion(Transaction tx) {\n"
- " if ( tx.wasCommitted() ) {\n"
- " System.out.println(\"Creations: \" + creates + \", Updates: \" + updates, \"Loads: \" + loads);\n"
- " }\n"
- " updates=0;\n"
- " creates=0;\n"
- " loads=0;\n"
- " }\n"
- "\n"
- "}]]>"
-msgstr ""
-
#. Tag: para
-#: events.xml:58
#, no-c-format
msgid "There are two kinds of inteceptors: <literal>Session</literal>-scoped and <literal>SessionFactory</literal>-scoped."
msgstr ""
#. Tag: para
-#: events.xml:63
#, no-c-format
msgid "A <literal>Session</literal>-scoped interceptor is specified when a session is opened using one of the overloaded SessionFactory.openSession() methods accepting an <literal>Interceptor</literal>."
msgstr ""
-#. Tag: programlisting
-#: events.xml:69
-#, no-c-format
-msgid "<![CDATA[Session session = sf.openSession( new AuditInterceptor() );]]>"
-msgstr ""
-
#. Tag: para
-#: events.xml:71
#, no-c-format
msgid "A <literal>SessionFactory</literal>-scoped interceptor is registered with the <literal>Configuration</literal> object prior to building the <literal>SessionFactory</literal>. Unless a session is opened explicitly specifying the interceptor to use, the supplied interceptor will be applied to all sessions opened from that <literal>SessionFactory</literal>. <literal>SessionFactory</literal>-scoped interceptors must be thread safe. Ensure that you do not store session-specific states, since multiple sessions will use this interceptor potentially concurrently."
msgstr ""
-#. Tag: programlisting
-#: events.xml:80
-#, no-c-format
-msgid "<![CDATA[new Configuration().setInterceptor( new AuditInterceptor() );]]>"
-msgstr ""
-
#. Tag: title
-#: events.xml:85
#, no-c-format
msgid "Event system"
msgstr ""
#. Tag: para
-#: events.xml:87
#, no-c-format
msgid "If you have to react to particular events in your persistence layer, you can also use the Hibernate3 <emphasis>event</emphasis> architecture. The event system can be used in addition, or as a replacement, for interceptors."
msgstr ""
#. Tag: para
-#: events.xml:93
#, no-c-format
msgid "All the methods of the <literal>Session</literal> interface correlate to an event. You have a <literal>LoadEvent</literal>, a <literal>FlushEvent</literal>, etc. Consult the XML configuration-file DTD or the <literal>org.hibernate.event</literal> package for the full list of defined event types. When a request is made of one of these methods, the Hibernate <literal>Session</literal> generates an appropriate event and passes it to the configured event listeners for that type. Out-of-the-box, these listeners implement the same processing in which those methods always resulted. However, you are free to implement a customization of one of the listener interfaces (i.e., the <literal>LoadEvent</literal> is processed by the registered implementation of the <literal>LoadEventListener</literal> interface), in which case their implementation would be responsible for processing any <literal>load()</literal> requests made of the <literal>Session</literal>."
msgstr ""
#. Tag: para
-#: events.xml:108
#, no-c-format
msgid "The listeners should be considered singletons. This means they are shared between requests, and should not save any state as instance variables."
msgstr ""
#. Tag: para
-#: events.xml:113
#, no-c-format
msgid "A custom listener implements the appropriate interface for the event it wants to process and/or extend one of the convenience base classes (or even the default event listeners used by Hibernate out-of-the-box as these are declared non-final for this purpose). Custom listeners can either be registered programmatically through the <literal>Configuration</literal> object, or specified in the Hibernate configuration XML. Declarative configuration through the properties file is not supported. Here is an example of a custom load event listener:"
msgstr ""
-#. Tag: programlisting
-#: events.xml:123
-#, no-c-format
-msgid ""
- "<![CDATA[public class MyLoadListener implements LoadEventListener {\n"
- " // this is the single method defined by the LoadEventListener interface\n"
- " public void onLoad(LoadEvent event, LoadEventListener.LoadType loadType)\n"
- " throws HibernateException {\n"
- " if ( !MySecurity.isAuthorized( event.getEntityClassName(), event.getEntityId() ) ) {\n"
- " throw MySecurityException(\"Unauthorized access\");\n"
- " }\n"
- " }\n"
- "}]]>"
-msgstr ""
-
#. Tag: para
-#: events.xml:125
#, no-c-format
msgid "You also need a configuration entry telling Hibernate to use the listener in addition to the default listener:"
msgstr ""
-#. Tag: programlisting
-#: events.xml:130
-#, no-c-format
-msgid ""
- "<![CDATA[<hibernate-configuration>\n"
- " <session-factory>\n"
- " ...\n"
- " <event type=\"load\">\n"
- " <listener class=\"com.eg.MyLoadListener\"/>\n"
- " <listener class=\"org.hibernate.event.def.DefaultLoadEventListener\"/>\n"
- " </event>\n"
- " </session-factory>\n"
- "</hibernate-configuration>]]>"
-msgstr ""
-
#. Tag: para
-#: events.xml:132
#, no-c-format
msgid "Instead, you can register it programmatically:"
msgstr ""
-#. Tag: programlisting
-#: events.xml:136
-#, no-c-format
-msgid ""
- "<![CDATA[Configuration cfg = new Configuration();\n"
- "LoadEventListener[] stack = { new MyLoadListener(), new DefaultLoadEventListener() };\n"
- "cfg.EventListeners().setLoadEventListeners(stack);]]>"
-msgstr ""
-
#. Tag: para
-#: events.xml:138
#, no-c-format
msgid "Listeners registered declaratively cannot share instances. If the same class name is used in multiple <literal><listener/></literal> elements, each reference will result in a separate instance of that class. If you need to share listener instances between listener types you must use the programmatic registration approach."
msgstr ""
#. Tag: para
-#: events.xml:146
#, no-c-format
msgid "Why implement an interface and define the specific type during configuration? A listener implementation could implement multiple event listener interfaces. Having the type additionally defined during registration makes it easier to turn custom listeners on or off during configuration."
msgstr ""
#. Tag: title
-#: events.xml:156
#, no-c-format
msgid "Hibernate declarative security"
msgstr ""
#. Tag: para
-#: events.xml:157
#, no-c-format
msgid "Usually, declarative security in Hibernate applications is managed in a session facade layer. Hibernate3 allows certain actions to be permissioned via JACC, and authorized via JAAS. This is an optional functionality that is built on top of the event architecture."
msgstr ""
#. Tag: para
-#: events.xml:163
#, no-c-format
msgid "First, you must configure the appropriate event listeners, to enable the use of JAAS authorization."
msgstr ""
-#. Tag: programlisting
-#: events.xml:168
-#, no-c-format
-msgid ""
- "<![CDATA[<listener type=\"pre-delete\" class=\"org.hibernate.secure.JACCPreDeleteEventListener\"/>\n"
- "<listener type=\"pre-update\" class=\"org.hibernate.secure.JACCPreUpdateEventListener\"/>\n"
- "<listener type=\"pre-insert\" class=\"org.hibernate.secure.JACCPreInsertEventListener\"/>\n"
- "<listener type=\"pre-load\" class=\"org.hibernate.secure.JACCPreLoadEventListener\"/>]]>"
-msgstr ""
-
#. Tag: para
-#: events.xml:170
#, no-c-format
msgid "Note that <literal><listener type=\"...\" class=\"...\"/></literal> is shorthand for <literal><event type=\"...\"><listener class=\"...\"/></event></literal> when there is exactly one listener for a particular event type."
msgstr ""
#. Tag: para
-#: events.xml:176
#, no-c-format
msgid "Next, while still in <literal>hibernate.cfg.xml</literal>, bind the permissions to roles:"
msgstr ""
-#. Tag: programlisting
-#: events.xml:180
-#, no-c-format
-msgid ""
- "<![CDATA[<grant role=\"admin\" entity-name=\"User\" actions=\"insert,update,read\"/>\n"
- "<grant role=\"su\" entity-name=\"User\" actions=\"*\"/>]]>"
-msgstr ""
-
#. Tag: para
-#: events.xml:182
#, no-c-format
msgid "The role names are the roles understood by your JACC provider."
msgstr ""
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/example_mappings.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/example_mappings.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/example_mappings.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,717 +1,119 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-10 21:02+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:19\n"
+"PO-Revision-Date: 2010-01-08T04:07:19\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
-#: example_mappings.xml:29
#, no-c-format
msgid "Example: Various Mappings"
msgstr ""
#. Tag: para
-#: example_mappings.xml:32
#, no-c-format
msgid "This chapters explores some more complex association mappings."
msgstr ""
#. Tag: title
-#: example_mappings.xml:37
#, no-c-format
msgid "Employer/Employee"
msgstr ""
#. Tag: para
-#: example_mappings.xml:39
#, no-c-format
msgid "The following model of the relationship between <literal>Employer</literal> and <literal>Employee</literal> uses an entity class (<literal>Employment</literal>) to represent the association. You can do this when there might be more than one period of employment for the same two parties. Components are used to model monetary values and employee names."
msgstr ""
#. Tag: para
-#: example_mappings.xml:56
#, no-c-format
msgid "Here is a possible mapping document:"
msgstr ""
-#. Tag: programlisting
-#: example_mappings.xml:60
-#, no-c-format
-msgid ""
- "<![CDATA[<hibernate-mapping>\n"
- " \n"
- " <class name=\"Employer\" table=\"employers\">\n"
- " <id name=\"id\">\n"
- " <generator class=\"sequence\">\n"
- " <param name=\"sequence\">employer_id_seq</param>\n"
- " </generator>\n"
- " </id>\n"
- " <property name=\"name\"/>\n"
- " </class>\n"
- "\n"
- " <class name=\"Employment\" table=\"employment_periods\">\n"
- "\n"
- " <id name=\"id\">\n"
- " <generator class=\"sequence\">\n"
- " <param name=\"sequence\">employment_id_seq</param>\n"
- " </generator>\n"
- " </id>\n"
- " <property name=\"startDate\" column=\"start_date\"/>\n"
- " <property name=\"endDate\" column=\"end_date\"/>\n"
- "\n"
- " <component name=\"hourlyRate\" class=\"MonetaryAmount\">\n"
- " <property name=\"amount\">\n"
- " <column name=\"hourly_rate\" sql-type=\"NUMERIC(12, 2)\"/>\n"
- " </property>\n"
- " <property name=\"currency\" length=\"12\"/>\n"
- " </component>\n"
- "\n"
- " <many-to-one name=\"employer\" column=\"employer_id\" not-null=\"true\"/>\n"
- " <many-to-one name=\"employee\" column=\"employee_id\" not-null=\"true\"/>\n"
- "\n"
- " </class>\n"
- "\n"
- " <class name=\"Employee\" table=\"employees\">\n"
- " <id name=\"id\">\n"
- " <generator class=\"sequence\">\n"
- " <param name=\"sequence\">employee_id_seq</param>\n"
- " </generator>\n"
- " </id>\n"
- " <property name=\"taxfileNumber\"/>\n"
- " <component name=\"name\" class=\"Name\">\n"
- " <property name=\"firstName\"/>\n"
- " <property name=\"initial\"/>\n"
- " <property name=\"lastName\"/>\n"
- " </component>\n"
- " </class>\n"
- "\n"
- "</hibernate-mapping>]]>"
-msgstr ""
-
#. Tag: para
-#: example_mappings.xml:62
#, no-c-format
msgid "Here is the table schema generated by <literal>SchemaExport</literal>."
msgstr ""
-#. Tag: programlisting
-#: example_mappings.xml:66
-#, no-c-format
-msgid ""
- "<![CDATA[create table employers (\n"
- " id BIGINT not null, \n"
- " name VARCHAR(255), \n"
- " primary key (id)\n"
- ")\n"
- "\n"
- "create table employment_periods (\n"
- " id BIGINT not null,\n"
- " hourly_rate NUMERIC(12, 2),\n"
- " currency VARCHAR(12), \n"
- " employee_id BIGINT not null, \n"
- " employer_id BIGINT not null, \n"
- " end_date TIMESTAMP, \n"
- " start_date TIMESTAMP, \n"
- " primary key (id)\n"
- ")\n"
- "\n"
- "create table employees (\n"
- " id BIGINT not null, \n"
- " firstName VARCHAR(255), \n"
- " initial CHAR(1), \n"
- " lastName VARCHAR(255), \n"
- " taxfileNumber VARCHAR(255), \n"
- " primary key (id)\n"
- ")\n"
- "\n"
- "alter table employment_periods \n"
- " add constraint employment_periodsFK0 foreign key (employer_id) references employers\n"
- "alter table employment_periods \n"
- " add constraint employment_periodsFK1 foreign key (employee_id) references employees\n"
- "create sequence employee_id_seq\n"
- "create sequence employment_id_seq\n"
- "create sequence employer_id_seq]]>"
-msgstr ""
-
#. Tag: title
-#: example_mappings.xml:71
#, no-c-format
msgid "Author/Work"
msgstr ""
#. Tag: para
-#: example_mappings.xml:73
#, no-c-format
msgid "Consider the following model of the relationships between <literal>Work</literal>, <literal>Author</literal> and <literal>Person</literal>. In the example, the relationship between <literal>Work</literal> and <literal>Author</literal> is represented as a many-to-many association and the relationship between <literal>Author</literal> and <literal>Person</literal> is represented as one-to-one association. Another possibility would be to have <literal>Author</literal> extend <literal>Person</literal>."
msgstr ""
#. Tag: para
-#: example_mappings.xml:91
#, no-c-format
msgid "The following mapping document correctly represents these relationships:"
msgstr ""
-#. Tag: programlisting
-#: example_mappings.xml:95
-#, no-c-format
-msgid ""
- "<![CDATA[<hibernate-mapping>\n"
- "\n"
- " <class name=\"Work\" table=\"works\" discriminator-value=\"W\">\n"
- "\n"
- " <id name=\"id\" column=\"id\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <discriminator column=\"type\" type=\"character\"/>\n"
- "\n"
- " <property name=\"title\"/>\n"
- " <set name=\"authors\" table=\"author_work\">\n"
- " <key column name=\"work_id\"/>\n"
- " <many-to-many class=\"Author\" column name=\"author_id\"/>\n"
- " </set>\n"
- "\n"
- " <subclass name=\"Book\" discriminator-value=\"B\">\n"
- " <property name=\"text\"/>\n"
- " </subclass>\n"
- "\n"
- " <subclass name=\"Song\" discriminator-value=\"S\">\n"
- " <property name=\"tempo\"/>\n"
- " <property name=\"genre\"/>\n"
- " </subclass>\n"
- "\n"
- " </class>\n"
- "\n"
- " <class name=\"Author\" table=\"authors\">\n"
- "\n"
- " <id name=\"id\" column=\"id\">\n"
- " <!-- The Author must have the same identifier as the Person -->\n"
- " <generator class=\"assigned\"/> \n"
- " </id>\n"
- "\n"
- " <property name=\"alias\"/>\n"
- " <one-to-one name=\"person\" constrained=\"true\"/>\n"
- "\n"
- " <set name=\"works\" table=\"author_work\" inverse=\"true\">\n"
- " <key column=\"author_id\"/>\n"
- " <many-to-many class=\"Work\" column=\"work_id\"/>\n"
- " </set>\n"
- "\n"
- " </class>\n"
- "\n"
- " <class name=\"Person\" table=\"persons\">\n"
- " <id name=\"id\" column=\"id\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <property name=\"name\"/>\n"
- " </class>\n"
- "\n"
- "</hibernate-mapping>]]>"
-msgstr ""
-
#. Tag: para
-#: example_mappings.xml:97
#, no-c-format
msgid "There are four tables in this mapping: <literal>works</literal>, <literal>authors</literal> and <literal>persons</literal> hold work, author and person data respectively. <literal>author_work</literal> is an association table linking authors to works. Here is the table schema, as generated by <literal>SchemaExport</literal>:"
msgstr ""
-#. Tag: programlisting
-#: example_mappings.xml:105
-#, no-c-format
-msgid ""
- "<![CDATA[create table works (\n"
- " id BIGINT not null generated by default as identity, \n"
- " tempo FLOAT, \n"
- " genre VARCHAR(255), \n"
- " text INTEGER, \n"
- " title VARCHAR(255), \n"
- " type CHAR(1) not null, \n"
- " primary key (id)\n"
- ")\n"
- "\n"
- "create table author_work (\n"
- " author_id BIGINT not null, \n"
- " work_id BIGINT not null, \n"
- " primary key (work_id, author_id)\n"
- ")\n"
- "\n"
- "create table authors (\n"
- " id BIGINT not null generated by default as identity, \n"
- " alias VARCHAR(255), \n"
- " primary key (id)\n"
- ")\n"
- "\n"
- "create table persons (\n"
- " id BIGINT not null generated by default as identity, \n"
- " name VARCHAR(255), \n"
- " primary key (id)\n"
- ")\n"
- "\n"
- "alter table authors \n"
- " add constraint authorsFK0 foreign key (id) references persons\n"
- "alter table author_work \n"
- " add constraint author_workFK0 foreign key (author_id) references authors\n"
- "alter table author_work\n"
- " add constraint author_workFK1 foreign key (work_id) references works]]>"
-msgstr ""
-
#. Tag: title
-#: example_mappings.xml:110
#, no-c-format
msgid "Customer/Order/Product"
msgstr ""
#. Tag: para
-#: example_mappings.xml:112
#, no-c-format
msgid "In this section we consider a model of the relationships between <literal>Customer</literal>, <literal>Order</literal>, <literal>Line Item</literal> and <literal>Product</literal>. There is a one-to-many association between <literal>Customer</literal> and <literal>Order</literal>, but how can you represent <literal>Order</literal> / <literal>LineItem</literal> / <literal>Product</literal>? In the example, <literal>LineItem</literal> is mapped as an association class representing the many-to-many association between <literal>Order</literal> and <literal>Product</literal>. In Hibernate this is called a composite element."
msgstr ""
#. Tag: para
-#: example_mappings.xml:132
#, no-c-format
msgid "The mapping document will look like this:"
msgstr ""
-#. Tag: programlisting
-#: example_mappings.xml:136
-#, no-c-format
-msgid ""
- "<![CDATA[<hibernate-mapping>\n"
- "\n"
- " <class name=\"Customer\" table=\"customers\">\n"
- " <id name=\"id\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <property name=\"name\"/>\n"
- " <set name=\"orders\" inverse=\"true\">\n"
- " <key column=\"customer_id\"/>\n"
- " <one-to-many class=\"Order\"/>\n"
- " </set>\n"
- " </class>\n"
- "\n"
- " <class name=\"Order\" table=\"orders\">\n"
- " <id name=\"id\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <property name=\"date\"/>\n"
- " <many-to-one name=\"customer\" column=\"customer_id\"/>\n"
- " <list name=\"lineItems\" table=\"line_items\">\n"
- " <key column=\"order_id\"/>\n"
- " <list-index column=\"line_number\"/>\n"
- " <composite-element class=\"LineItem\">\n"
- " <property name=\"quantity\"/>\n"
- " <many-to-one name=\"product\" column=\"product_id\"/>\n"
- " </composite-element>\n"
- " </list>\n"
- " </class>\n"
- "\n"
- " <class name=\"Product\" table=\"products\">\n"
- " <id name=\"id\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <property name=\"serialNumber\"/>\n"
- " </class>\n"
- "\n"
- "</hibernate-mapping>]]>"
-msgstr ""
-
#. Tag: para
-#: example_mappings.xml:138
#, no-c-format
msgid "<literal>customers</literal>, <literal>orders</literal>, <literal>line_items</literal> and <literal>products</literal> hold customer, order, order line item and product data respectively. <literal>line_items</literal> also acts as an association table linking orders with products."
msgstr ""
-#. Tag: programlisting
-#: example_mappings.xml:145
-#, no-c-format
-msgid ""
- "<![CDATA[create table customers (\n"
- " id BIGINT not null generated by default as identity, \n"
- " name VARCHAR(255), \n"
- " primary key (id)\n"
- ")\n"
- "\n"
- "create table orders (\n"
- " id BIGINT not null generated by default as identity, \n"
- " customer_id BIGINT, \n"
- " date TIMESTAMP, \n"
- " primary key (id)\n"
- ")\n"
- "\n"
- "create table line_items (\n"
- " line_number INTEGER not null, \n"
- " order_id BIGINT not null, \n"
- " product_id BIGINT, \n"
- " quantity INTEGER, \n"
- " primary key (order_id, line_number)\n"
- ")\n"
- "\n"
- "create table products (\n"
- " id BIGINT not null generated by default as identity, \n"
- " serialNumber VARCHAR(255), \n"
- " primary key (id)\n"
- ")\n"
- "\n"
- "alter table orders \n"
- " add constraint ordersFK0 foreign key (customer_id) references customers\n"
- "alter table line_items\n"
- " add constraint line_itemsFK0 foreign key (product_id) references products\n"
- "alter table line_items\n"
- " add constraint line_itemsFK1 foreign key (order_id) references orders]]>"
-msgstr ""
-
#. Tag: title
-#: example_mappings.xml:150
#, no-c-format
msgid "Miscellaneous example mappings"
msgstr ""
#. Tag: para
-#: example_mappings.xml:152
#, no-c-format
msgid "These examples are available from the Hibernate test suite. You will find many other useful example mappings there by searching in the <literal>test</literal> folder of the Hibernate distribution."
msgstr ""
#. Tag: title
-#: example_mappings.xml:161
#, no-c-format
msgid "\"Typed\" one-to-one association"
msgstr ""
-#. Tag: programlisting
-#: example_mappings.xml:162
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Person\">\n"
- " <id name=\"name\"/>\n"
- " <one-to-one name=\"address\" \n"
- " cascade=\"all\">\n"
- " <formula>name</formula>\n"
- " <formula>'HOME'</formula>\n"
- " </one-to-one>\n"
- " <one-to-one name=\"mailingAddress\" \n"
- " cascade=\"all\">\n"
- " <formula>name</formula>\n"
- " <formula>'MAILING'</formula>\n"
- " </one-to-one>\n"
- "</class>\n"
- "\n"
- "<class name=\"Address\" batch-size=\"2\" \n"
- " check=\"addressType in ('MAILING', 'HOME', 'BUSINESS')\">\n"
- " <composite-id>\n"
- " <key-many-to-one name=\"person\" \n"
- " column=\"personName\"/>\n"
- " <key-property name=\"type\" \n"
- " column=\"addressType\"/>\n"
- " </composite-id>\n"
- " <property name=\"street\" type=\"text\"/>\n"
- " <property name=\"state\"/>\n"
- " <property name=\"zip\"/>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: title
-#: example_mappings.xml:166
#, no-c-format
msgid "Composite key example"
msgstr ""
-#. Tag: programlisting
-#: example_mappings.xml:167
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Customer\">\n"
- "\n"
- " <id name=\"customerId\"\n"
- " length=\"10\">\n"
- " <generator class=\"assigned\"/>\n"
- " </id>\n"
- "\n"
- " <property name=\"name\" not-null=\"true\" length=\"100\"/>\n"
- " <property name=\"address\" not-null=\"true\" length=\"200\"/>\n"
- "\n"
- " <list name=\"orders\"\n"
- " inverse=\"true\"\n"
- " cascade=\"save-update\">\n"
- " <key column=\"customerId\"/>\n"
- " <index column=\"orderNumber\"/>\n"
- " <one-to-many class=\"Order\"/>\n"
- " </list>\n"
- "\n"
- "</class>\n"
- "\n"
- "<class name=\"Order\" table=\"CustomerOrder\" lazy=\"true\">\n"
- " <synchronize table=\"LineItem\"/>\n"
- " <synchronize table=\"Product\"/>\n"
- " \n"
- " <composite-id name=\"id\" \n"
- " class=\"Order$Id\">\n"
- " <key-property name=\"customerId\" length=\"10\"/>\n"
- " <key-property name=\"orderNumber\"/>\n"
- " </composite-id>\n"
- " \n"
- " <property name=\"orderDate\" \n"
- " type=\"calendar_date\"\n"
- " not-null=\"true\"/>\n"
- " \n"
- " <property name=\"total\">\n"
- " <formula>\n"
- " ( select sum(li.quantity*p.price) \n"
- " from LineItem li, Product p \n"
- " where li.productId = p.productId \n"
- " and li.customerId = customerId \n"
- " and li.orderNumber = orderNumber )\n"
- " </formula>\n"
- " </property>\n"
- " \n"
- " <many-to-one name=\"customer\"\n"
- " column=\"customerId\"\n"
- " insert=\"false\"\n"
- " update=\"false\" \n"
- " not-null=\"true\"/>\n"
- " \n"
- " <bag name=\"lineItems\"\n"
- " fetch=\"join\" \n"
- " inverse=\"true\"\n"
- " cascade=\"save-update\">\n"
- " <key>\n"
- " <column name=\"customerId\"/>\n"
- " <column name=\"orderNumber\"/>\n"
- " </key>\n"
- " <one-to-many class=\"LineItem\"/>\n"
- " </bag>\n"
- " \n"
- "</class>\n"
- " \n"
- "<class name=\"LineItem\">\n"
- " \n"
- " <composite-id name=\"id\" \n"
- " class=\"LineItem$Id\">\n"
- " <key-property name=\"customerId\" length=\"10\"/>\n"
- " <key-property name=\"orderNumber\"/>\n"
- " <key-property name=\"productId\" length=\"10\"/>\n"
- " </composite-id>\n"
- " \n"
- " <property name=\"quantity\"/>\n"
- " \n"
- " <many-to-one name=\"order\"\n"
- " insert=\"false\"\n"
- " update=\"false\" \n"
- " not-null=\"true\">\n"
- " <column name=\"customerId\"/>\n"
- " <column name=\"orderNumber\"/>\n"
- " </many-to-one>\n"
- " \n"
- " <many-to-one name=\"product\"\n"
- " insert=\"false\"\n"
- " update=\"false\" \n"
- " not-null=\"true\"\n"
- " column=\"productId\"/>\n"
- " \n"
- "</class>\n"
- "\n"
- "<class name=\"Product\">\n"
- " <synchronize table=\"LineItem\"/>\n"
- "\n"
- " <id name=\"productId\"\n"
- " length=\"10\">\n"
- " <generator class=\"assigned\"/>\n"
- " </id>\n"
- " \n"
- " <property name=\"description\" \n"
- " not-null=\"true\" \n"
- " length=\"200\"/>\n"
- " <property name=\"price\" length=\"3\"/>\n"
- " <property name=\"numberAvailable\"/>\n"
- " \n"
- " <property name=\"numberOrdered\">\n"
- " <formula>\n"
- " ( select sum(li.quantity) \n"
- " from LineItem li \n"
- " where li.productId = productId )\n"
- " </formula>\n"
- " </property>\n"
- " \n"
- "</class>]]>"
-msgstr ""
-
#. Tag: title
-#: example_mappings.xml:171
#, no-c-format
msgid "Many-to-many with shared composite key attribute"
msgstr ""
-#. Tag: programlisting
-#: example_mappings.xml:172
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"User\" table=\"`User`\">\n"
- " <composite-id>\n"
- " <key-property name=\"name\"/>\n"
- " <key-property name=\"org\"/>\n"
- " </composite-id>\n"
- " <set name=\"groups\" table=\"UserGroup\">\n"
- " <key>\n"
- " <column name=\"userName\"/>\n"
- " <column name=\"org\"/>\n"
- " </key>\n"
- " <many-to-many class=\"Group\">\n"
- " <column name=\"groupName\"/>\n"
- " <formula>org</formula>\n"
- " </many-to-many>\n"
- " </set>\n"
- "</class>\n"
- " \n"
- "<class name=\"Group\" table=\"`Group`\">\n"
- " <composite-id>\n"
- " <key-property name=\"name\"/>\n"
- " <key-property name=\"org\"/>\n"
- " </composite-id>\n"
- " <property name=\"description\"/>\n"
- " <set name=\"users\" table=\"UserGroup\" inverse=\"true\">\n"
- " <key>\n"
- " <column name=\"groupName\"/>\n"
- " <column name=\"org\"/>\n"
- " </key>\n"
- " <many-to-many class=\"User\">\n"
- " <column name=\"userName\"/>\n"
- " <formula>org</formula>\n"
- " </many-to-many>\n"
- " </set>\n"
- "</class>\n"
- "]]>"
-msgstr ""
-
#. Tag: title
-#: example_mappings.xml:176
#, no-c-format
msgid "Content based discrimination"
msgstr ""
-#. Tag: programlisting
-#: example_mappings.xml:177
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Person\"\n"
- " discriminator-value=\"P\">\n"
- " \n"
- " <id name=\"id\" \n"
- " column=\"person_id\" \n"
- " unsaved-value=\"0\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " \n"
- " \n"
- " <discriminator \n"
- " type=\"character\">\n"
- " <formula>\n"
- " case \n"
- " when title is not null then 'E' \n"
- " when salesperson is not null then 'C' \n"
- " else 'P' \n"
- " end\n"
- " </formula>\n"
- " </discriminator>\n"
- "\n"
- " <property name=\"name\" \n"
- " not-null=\"true\"\n"
- " length=\"80\"/>\n"
- " \n"
- " <property name=\"sex\" \n"
- " not-null=\"true\"\n"
- " update=\"false\"/>\n"
- " \n"
- " <component name=\"address\">\n"
- " <property name=\"address\"/>\n"
- " <property name=\"zip\"/>\n"
- " <property name=\"country\"/>\n"
- " </component>\n"
- " \n"
- " <subclass name=\"Employee\" \n"
- " discriminator-value=\"E\">\n"
- " <property name=\"title\"\n"
- " length=\"20\"/>\n"
- " <property name=\"salary\"/>\n"
- " <many-to-one name=\"manager\"/>\n"
- " </subclass>\n"
- " \n"
- " <subclass name=\"Customer\" \n"
- " discriminator-value=\"C\">\n"
- " <property name=\"comments\"/>\n"
- " <many-to-one name=\"salesperson\"/>\n"
- " </subclass>\n"
- " \n"
- "</class>]]>"
-msgstr ""
-
#. Tag: title
-#: example_mappings.xml:181
#, no-c-format
msgid "Associations on alternate keys"
msgstr ""
-#. Tag: programlisting
-#: example_mappings.xml:182
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Person\">\n"
- " \n"
- " <id name=\"id\">\n"
- " <generator class=\"hilo\"/>\n"
- " </id>\n"
- " \n"
- " <property name=\"name\" length=\"100\"/>\n"
- " \n"
- " <one-to-one name=\"address\" \n"
- " property-ref=\"person\"\n"
- " cascade=\"all\"\n"
- " fetch=\"join\"/>\n"
- " \n"
- " <set name=\"accounts\" \n"
- " inverse=\"true\">\n"
- " <key column=\"userId\"\n"
- " property-ref=\"userId\"/>\n"
- " <one-to-many class=\"Account\"/>\n"
- " </set>\n"
- " \n"
- " <property name=\"userId\" length=\"8\"/>\n"
- "\n"
- "</class>\n"
- "\n"
- "<class name=\"Address\">\n"
- "\n"
- " <id name=\"id\">\n"
- " <generator class=\"hilo\"/>\n"
- " </id>\n"
- "\n"
- " <property name=\"address\" length=\"300\"/>\n"
- " <property name=\"zip\" length=\"5\"/>\n"
- " <property name=\"country\" length=\"25\"/>\n"
- " <many-to-one name=\"person\" unique=\"true\" not-null=\"true\"/>\n"
- "\n"
- "</class>\n"
- "\n"
- "<class name=\"Account\">\n"
- " <id name=\"accountId\" length=\"32\">\n"
- " <generator class=\"uuid\"/>\n"
- " </id>\n"
- " \n"
- " <many-to-one name=\"user\"\n"
- " column=\"userId\"\n"
- " property-ref=\"userId\"/>\n"
- " \n"
- " <property name=\"type\" not-null=\"true\"/>\n"
- " \n"
- "</class>]]>"
-msgstr ""
-
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/example_parentchild.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/example_parentchild.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/example_parentchild.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,396 +1,203 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-10 21:02+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:19\n"
+"PO-Revision-Date: 2010-01-08T04:07:19\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
-#: example_parentchild.xml:29
#, no-c-format
msgid "Example: Parent/Child"
msgstr ""
#. Tag: para
-#: example_parentchild.xml:31
#, no-c-format
msgid "One of the first things that new users want to do with Hibernate is to model a parent/child type relationship. There are two different approaches to this. The most convenient approach, especially for new users, is to model both <literal>Parent</literal> and <literal>Child</literal> as entity classes with a <literal><one-to-many></literal> association from <literal>Parent</literal> to <literal>Child</literal>. The alternative approach is to declare the <literal>Child</literal> as a <literal><composite-element></literal>. The default semantics of a one-to-many association in Hibernate are much less close to the usual semantics of a parent/child relationship than those of a composite element mapping. We will explain how to use a <emphasis>bidirectional one-to-many association with cascades</emphasis> to model a parent/child relationship efficiently and elegantly."
msgstr ""
#. Tag: title
-#: example_parentchild.xml:45
#, no-c-format
msgid "A note about collections"
msgstr ""
#. Tag: para
-#: example_parentchild.xml:47
#, no-c-format
msgid "Hibernate collections are considered to be a logical part of their owning entity and not of the contained entities. Be aware that this is a critical distinction that has the following consequences:"
msgstr ""
#. Tag: para
-#: example_parentchild.xml:54
#, no-c-format
msgid "When you remove/add an object from/to a collection, the version number of the collection owner is incremented."
msgstr ""
#. Tag: para
-#: example_parentchild.xml:60
#, no-c-format
msgid "If an object that was removed from a collection is an instance of a value type (e.g. a composite element), that object will cease to be persistent and its state will be completely removed from the database. Likewise, adding a value type instance to the collection will cause its state to be immediately persistent."
msgstr ""
#. Tag: para
-#: example_parentchild.xml:68
#, no-c-format
msgid "Conversely, if an entity is removed from a collection (a one-to-many or many-to-many association), it will not be deleted by default. This behavior is completely consistent; a change to the internal state of another entity should not cause the associated entity to vanish. Likewise, adding an entity to a collection does not cause that entity to become persistent, by default."
msgstr ""
#. Tag: para
-#: example_parentchild.xml:78
#, no-c-format
msgid "Adding an entity to a collection, by default, merely creates a link between the two entities. Removing the entity will remove the link. This is appropriate for all sorts of cases. However, it is not appropriate in the case of a parent/child relationship. In this case, the life of the child is bound to the life cycle of the parent."
msgstr ""
#. Tag: title
-#: example_parentchild.xml:88
#, no-c-format
msgid "Bidirectional one-to-many"
msgstr ""
#. Tag: para
-#: example_parentchild.xml:90
#, no-c-format
msgid "Suppose we start with a simple <literal><one-to-many></literal> association from <literal>Parent</literal> to <literal>Child</literal>."
msgstr ""
-#. Tag: programlisting
-#: example_parentchild.xml:95
-#, no-c-format
-msgid ""
- "<![CDATA[<set name=\"children\">\n"
- " <key column=\"parent_id\"/>\n"
- " <one-to-many class=\"Child\"/>\n"
- "</set>]]>"
-msgstr ""
-
#. Tag: para
-#: example_parentchild.xml:97
#, no-c-format
msgid "If we were to execute the following code:"
msgstr ""
-#. Tag: programlisting
-#: example_parentchild.xml:101
-#, no-c-format
-msgid ""
- "<![CDATA[Parent p = .....;\n"
- "Child c = new Child();\n"
- "p.getChildren().add(c);\n"
- "session.save(c);\n"
- "session.flush();]]>"
-msgstr ""
-
#. Tag: para
-#: example_parentchild.xml:103
#, no-c-format
msgid "Hibernate would issue two SQL statements:"
msgstr ""
#. Tag: para
-#: example_parentchild.xml:109
#, no-c-format
msgid "an <literal>INSERT</literal> to create the record for <literal>c</literal>"
msgstr ""
#. Tag: para
-#: example_parentchild.xml:112
#, no-c-format
msgid "an <literal>UPDATE</literal> to create the link from <literal>p</literal> to <literal>c</literal>"
msgstr ""
#. Tag: para
-#: example_parentchild.xml:119
#, no-c-format
msgid "This is not only inefficient, but also violates any <literal>NOT NULL</literal> constraint on the <literal>parent_id</literal> column. You can fix the nullability constraint violation by specifying <literal>not-null=\"true\"</literal> in the collection mapping:"
msgstr ""
-#. Tag: programlisting
-#: example_parentchild.xml:125
-#, no-c-format
-msgid ""
- "<![CDATA[<set name=\"children\">\n"
- " <key column=\"parent_id\" not-null=\"true\"/>\n"
- " <one-to-many class=\"Child\"/>\n"
- "</set>]]>"
-msgstr ""
-
#. Tag: para
-#: example_parentchild.xml:127
#, no-c-format
msgid "However, this is not the recommended solution."
msgstr ""
#. Tag: para
-#: example_parentchild.xml:130
#, no-c-format
msgid "The underlying cause of this behavior is that the link (the foreign key <literal>parent_id</literal>) from <literal>p</literal> to <literal>c</literal> is not considered part of the state of the <literal>Child</literal> object and is therefore not created in the <literal>INSERT</literal>. The solution is to make the link part of the <literal>Child</literal> mapping."
msgstr ""
-#. Tag: programlisting
-#: example_parentchild.xml:137
-#, no-c-format
-msgid "<![CDATA[<many-to-one name=\"parent\" column=\"parent_id\" not-null=\"true\"/>]]>"
-msgstr ""
-
#. Tag: para
-#: example_parentchild.xml:139
#, no-c-format
msgid "You also need to add the <literal>parent</literal> property to the <literal>Child</literal> class."
msgstr ""
#. Tag: para
-#: example_parentchild.xml:143
#, no-c-format
msgid "Now that the <literal>Child</literal> entity is managing the state of the link, we tell the collection not to update the link. We use the <literal>inverse</literal> attribute to do this:"
msgstr ""
-#. Tag: programlisting
-#: example_parentchild.xml:148
-#, no-c-format
-msgid ""
- "<![CDATA[<set name=\"children\" inverse=\"true\">\n"
- " <key column=\"parent_id\"/>\n"
- " <one-to-many class=\"Child\"/>\n"
- "</set>]]>"
-msgstr ""
-
#. Tag: para
-#: example_parentchild.xml:150
#, no-c-format
msgid "The following code would be used to add a new <literal>Child</literal>:"
msgstr ""
-#. Tag: programlisting
-#: example_parentchild.xml:154
-#, no-c-format
-msgid ""
- "<![CDATA[Parent p = (Parent) session.load(Parent.class, pid);\n"
- "Child c = new Child();\n"
- "c.setParent(p);\n"
- "p.getChildren().add(c);\n"
- "session.save(c);\n"
- "session.flush();]]>"
-msgstr ""
-
#. Tag: para
-#: example_parentchild.xml:156
#, no-c-format
msgid "Only one SQL <literal>INSERT</literal> would now be issued."
msgstr ""
#. Tag: para
-#: example_parentchild.xml:160
#, no-c-format
msgid "You could also create an <literal>addChild()</literal> method of <literal>Parent</literal>."
msgstr ""
-#. Tag: programlisting
-#: example_parentchild.xml:165
-#, no-c-format
-msgid ""
- "<![CDATA[public void addChild(Child c) {\n"
- " c.setParent(this);\n"
- " children.add(c);\n"
- "}]]>"
-msgstr ""
-
#. Tag: para
-#: example_parentchild.xml:167
#, no-c-format
msgid "The code to add a <literal>Child</literal> looks like this:"
msgstr ""
-#. Tag: programlisting
-#: example_parentchild.xml:171
-#, no-c-format
-msgid ""
- "<![CDATA[Parent p = (Parent) session.load(Parent.class, pid);\n"
- "Child c = new Child();\n"
- "p.addChild(c);\n"
- "session.save(c);\n"
- "session.flush();]]>"
-msgstr ""
-
#. Tag: title
-#: example_parentchild.xml:176
#, no-c-format
msgid "Cascading life cycle"
msgstr ""
#. Tag: para
-#: example_parentchild.xml:178
#, no-c-format
msgid "You can address the frustrations of the explicit call to <literal>save()</literal> by using cascades."
msgstr ""
-#. Tag: programlisting
-#: example_parentchild.xml:183
-#, no-c-format
-msgid ""
- "<![CDATA[<set name=\"children\" inverse=\"true\" cascade=\"all\">\n"
- " <key column=\"parent_id\"/>\n"
- " <one-to-many class=\"Child\"/>\n"
- "</set>]]>"
-msgstr ""
-
#. Tag: para
-#: example_parentchild.xml:185
#, no-c-format
msgid "This simplifies the code above to:"
msgstr ""
-#. Tag: programlisting
-#: example_parentchild.xml:189
-#, no-c-format
-msgid ""
- "<![CDATA[Parent p = (Parent) session.load(Parent.class, pid);\n"
- "Child c = new Child();\n"
- "p.addChild(c);\n"
- "session.flush();]]>"
-msgstr ""
-
#. Tag: para
-#: example_parentchild.xml:191
#, no-c-format
msgid "Similarly, we do not need to iterate over the children when saving or deleting a <literal>Parent</literal>. The following removes <literal>p</literal> and all its children from the database."
msgstr ""
-#. Tag: programlisting
-#: example_parentchild.xml:196
-#, no-c-format
-msgid ""
- "<![CDATA[Parent p = (Parent) session.load(Parent.class, pid);\n"
- "session.delete(p);\n"
- "session.flush();]]>"
-msgstr ""
-
#. Tag: para
-#: example_parentchild.xml:198
#, no-c-format
msgid "However, the following code:"
msgstr ""
-#. Tag: programlisting
-#: example_parentchild.xml:202
-#, no-c-format
-msgid ""
- "<![CDATA[Parent p = (Parent) session.load(Parent.class, pid);\n"
- "Child c = (Child) p.getChildren().iterator().next();\n"
- "p.getChildren().remove(c);\n"
- "c.setParent(null);\n"
- "session.flush();]]>"
-msgstr ""
-
#. Tag: para
-#: example_parentchild.xml:204
#, no-c-format
msgid "will not remove <literal>c</literal> from the database. In this case, it will only remove the link to <literal>p</literal> and cause a <literal>NOT NULL</literal> constraint violation. You need to explicitly <literal>delete()</literal> the <literal>Child</literal>."
msgstr ""
-#. Tag: programlisting
-#: example_parentchild.xml:210
-#, no-c-format
-msgid ""
- "<![CDATA[Parent p = (Parent) session.load(Parent.class, pid);\n"
- "Child c = (Child) p.getChildren().iterator().next();\n"
- "p.getChildren().remove(c);\n"
- "session.delete(c);\n"
- "session.flush();]]>"
-msgstr ""
-
#. Tag: para
-#: example_parentchild.xml:212
#, no-c-format
msgid "In our case, a <literal>Child</literal> cannot exist without its parent. So if we remove a <literal>Child</literal> from the collection, we do want it to be deleted. To do this, we must use <literal>cascade=\"all-delete-orphan\"</literal>."
msgstr ""
-#. Tag: programlisting
-#: example_parentchild.xml:218
-#, no-c-format
-msgid ""
- "<![CDATA[<set name=\"children\" inverse=\"true\" cascade=\"all-delete-orphan\">\n"
- " <key column=\"parent_id\"/>\n"
- " <one-to-many class=\"Child\"/>\n"
- "</set>]]>"
-msgstr ""
-
#. Tag: para
-#: example_parentchild.xml:220
#, no-c-format
msgid "Even though the collection mapping specifies <literal>inverse=\"true\"</literal>, cascades are still processed by iterating the collection elements. If you need an object be saved, deleted or updated by cascade, you must add it to the collection. It is not enough to simply call <literal>setParent()</literal>."
msgstr ""
#. Tag: title
-#: example_parentchild.xml:230
#, no-c-format
msgid "Cascades and <literal>unsaved-value</literal>"
msgstr ""
#. Tag: para
-#: example_parentchild.xml:232
#, no-c-format
-msgid "Suppose we loaded up a <literal>Parent</literal> in one <literal>Session</literal>, made some changes in a UI action and wanted to persist these changes in a new session by calling <literal>update()</literal>. The <literal>Parent</literal> will contain a collection of children and, since the cascading update is enabled, Hibernate needs to know which children are newly instantiated and which represent existing rows in the database. We will also assume that both <literal>Parent</literal> and <literal>Child</literal> have generated identifier properties of type <literal>Long</literal>. Hibernate will use the identifier and version/timestamp property value to determine which of the children are new. (See <xref linkend=\"objectstate-saveorupdate\"/>.) <emphasis>In Hibernate3, it is no longer necessary to specify an <literal>unsaved-value</literal> explicitly.</emphasis>"
+msgid "Suppose we loaded up a <literal>Parent</literal> in one <literal>Session</literal>, made some changes in a UI action and wanted to persist these changes in a new session by calling <literal>update()</literal>. The <literal>Parent</literal> will contain a collection of children and, since the cascading update is enabled, Hibernate needs to know which children are newly instantiated and which represent existing rows in the database. We will also assume that both <literal>Parent</literal> and <literal>Child</literal> have generated identifier properties of type <literal>Long</literal>. Hibernate will use the identifier and version/timestamp property value to determine which of the children are new. (See <xref linkend=\"objectstate-saveorupdate\" />.) <emphasis>In Hibernate3, it is no longer necessary to specify an <literal>unsaved-value</literal> explicitly.</emphasis>"
msgstr ""
#. Tag: para
-#: example_parentchild.xml:244
#, no-c-format
msgid "The following code will update <literal>parent</literal> and <literal>child</literal> and insert <literal>newChild</literal>:"
msgstr ""
-#. Tag: programlisting
-#: example_parentchild.xml:249
-#, no-c-format
-msgid ""
- "<![CDATA[//parent and child were both loaded in a previous session\n"
- "parent.addChild(child);\n"
- "Child newChild = new Child();\n"
- "parent.addChild(newChild);\n"
- "session.update(parent);\n"
- "session.flush();]]>"
-msgstr ""
-
#. Tag: para
-#: example_parentchild.xml:251
#, no-c-format
msgid "This may be suitable for the case of a generated identifier, but what about assigned identifiers and composite identifiers? This is more difficult, since Hibernate cannot use the identifier property to distinguish between a newly instantiated object, with an identifier assigned by the user, and an object loaded in a previous session. In this case, Hibernate will either use the timestamp or version property, or will actually query the second-level cache or, worst case, the database, to see if the row exists."
msgstr ""
#. Tag: title
-#: example_parentchild.xml:284
#, no-c-format
msgid "Conclusion"
msgstr ""
#. Tag: para
-#: example_parentchild.xml:286
#, no-c-format
msgid "The sections we have just covered can be a bit confusing. However, in practice, it all works out nicely. Most Hibernate applications use the parent/child pattern in many places."
msgstr ""
#. Tag: para
-#: example_parentchild.xml:291
#, no-c-format
msgid "We mentioned an alternative in the first paragraph. None of the above issues exist in the case of <literal><composite-element></literal> mappings, which have exactly the semantics of a parent/child relationship. Unfortunately, there are two big limitations with composite element classes: composite elements cannot own collections and they should not be the child of any entity other than the unique parent."
msgstr ""
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/example_weblog.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/example_weblog.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/example_weblog.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,478 +1,49 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-10 21:02+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:19\n"
+"PO-Revision-Date: 2010-01-08T04:07:19\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
-#: example_weblog.xml:29
#, no-c-format
msgid "Example: Weblog Application"
msgstr ""
#. Tag: title
-#: example_weblog.xml:32
#, no-c-format
msgid "Persistent Classes"
msgstr ""
#. Tag: para
-#: example_weblog.xml:34
#, no-c-format
msgid "The persistent classes here represent a weblog and an item posted in a weblog. They are to be modelled as a standard parent/child relationship, but we will use an ordered bag, instead of a set:"
msgstr ""
-#. Tag: programlisting
-#: example_weblog.xml:40
-#, no-c-format
-msgid ""
- "<![CDATA[package eg;\n"
- "\n"
- "import java.util.List;\n"
- "\n"
- "public class Blog {\n"
- " private Long _id;\n"
- " private String _name;\n"
- " private List _items;\n"
- "\n"
- " public Long getId() {\n"
- " return _id;\n"
- " }\n"
- " public List getItems() {\n"
- " return _items;\n"
- " }\n"
- " public String getName() {\n"
- " return _name;\n"
- " }\n"
- " public void setId(Long long1) {\n"
- " _id = long1;\n"
- " }\n"
- " public void setItems(List list) {\n"
- " _items = list;\n"
- " }\n"
- " public void setName(String string) {\n"
- " _name = string;\n"
- " }\n"
- "}]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: example_weblog.xml:42
-#, no-c-format
-msgid ""
- "<![CDATA[package eg;\n"
- "\n"
- "import java.text.DateFormat;\n"
- "import java.util.Calendar;\n"
- "\n"
- "public class BlogItem {\n"
- " private Long _id;\n"
- " private Calendar _datetime;\n"
- " private String _text;\n"
- " private String _title;\n"
- " private Blog _blog;\n"
- "\n"
- " public Blog getBlog() {\n"
- " return _blog;\n"
- " }\n"
- " public Calendar getDatetime() {\n"
- " return _datetime;\n"
- " }\n"
- " public Long getId() {\n"
- " return _id;\n"
- " }\n"
- " public String getText() {\n"
- " return _text;\n"
- " }\n"
- " public String getTitle() {\n"
- " return _title;\n"
- " }\n"
- " public void setBlog(Blog blog) {\n"
- " _blog = blog;\n"
- " }\n"
- " public void setDatetime(Calendar calendar) {\n"
- " _datetime = calendar;\n"
- " }\n"
- " public void setId(Long long1) {\n"
- " _id = long1;\n"
- " }\n"
- " public void setText(String string) {\n"
- " _text = string;\n"
- " }\n"
- " public void setTitle(String string) {\n"
- " _title = string;\n"
- " }\n"
- "}]]>"
-msgstr ""
-
#. Tag: title
-#: example_weblog.xml:47
#, no-c-format
msgid "Hibernate Mappings"
msgstr ""
#. Tag: para
-#: example_weblog.xml:49
#, no-c-format
msgid "The XML mappings are now straightforward. For example:"
msgstr ""
-#. Tag: programlisting
-#: example_weblog.xml:53
-#, no-c-format
-msgid ""
- "<![CDATA[<?xml version=\"1.0\"?>\n"
- "<!DOCTYPE hibernate-mapping PUBLIC\n"
- " \"-//Hibernate/Hibernate Mapping DTD 3.0//EN\"\n"
- " \"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd\">\n"
- "\n"
- "<hibernate-mapping package=\"eg\">\n"
- "\n"
- " <class\n"
- " name=\"Blog\"\n"
- " table=\"BLOGS\">\n"
- "\n"
- " <id\n"
- " name=\"id\"\n"
- " column=\"BLOG_ID\">\n"
- "\n"
- " <generator class=\"native\"/>\n"
- "\n"
- " </id>\n"
- "\n"
- " <property\n"
- " name=\"name\"\n"
- " column=\"NAME\"\n"
- " not-null=\"true\"\n"
- " unique=\"true\"/>\n"
- "\n"
- " <bag\n"
- " name=\"items\"\n"
- " inverse=\"true\"\n"
- " order-by=\"DATE_TIME\"\n"
- " cascade=\"all\">\n"
- "\n"
- " <key column=\"BLOG_ID\"/>\n"
- " <one-to-many class=\"BlogItem\"/>\n"
- "\n"
- " </bag>\n"
- "\n"
- " </class>\n"
- "\n"
- "</hibernate-mapping>]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: example_weblog.xml:55
-#, no-c-format
-msgid ""
- "<![CDATA[<?xml version=\"1.0\"?>\n"
- "<!DOCTYPE hibernate-mapping PUBLIC\n"
- " \"-//Hibernate/Hibernate Mapping DTD 3.0//EN\"\n"
- " \"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd\">\n"
- "\n"
- "<hibernate-mapping package=\"eg\">\n"
- "\n"
- " <class\n"
- " name=\"BlogItem\"\n"
- " table=\"BLOG_ITEMS\"\n"
- " dynamic-update=\"true\">\n"
- "\n"
- " <id\n"
- " name=\"id\"\n"
- " column=\"BLOG_ITEM_ID\">\n"
- "\n"
- " <generator class=\"native\"/>\n"
- "\n"
- " </id>\n"
- "\n"
- " <property\n"
- " name=\"title\"\n"
- " column=\"TITLE\"\n"
- " not-null=\"true\"/>\n"
- "\n"
- " <property\n"
- " name=\"text\"\n"
- " column=\"TEXT\"\n"
- " not-null=\"true\"/>\n"
- "\n"
- " <property\n"
- " name=\"datetime\"\n"
- " column=\"DATE_TIME\"\n"
- " not-null=\"true\"/>\n"
- "\n"
- " <many-to-one\n"
- " name=\"blog\"\n"
- " column=\"BLOG_ID\"\n"
- " not-null=\"true\"/>\n"
- "\n"
- " </class>\n"
- "\n"
- "</hibernate-mapping>]]>"
-msgstr ""
-
#. Tag: title
-#: example_weblog.xml:60
#, no-c-format
msgid "Hibernate Code"
msgstr ""
#. Tag: para
-#: example_weblog.xml:62
#, no-c-format
msgid "The following class demonstrates some of the kinds of things we can do with these classes using Hibernate:"
msgstr ""
-#. Tag: programlisting
-#: example_weblog.xml:67
-#, no-c-format
-msgid ""
- "<![CDATA[package eg;\n"
- "\n"
- "import java.util.ArrayList;\n"
- "import java.util.Calendar;\n"
- "import java.util.Iterator;\n"
- "import java.util.List;\n"
- "\n"
- "import org.hibernate.HibernateException;\n"
- "import org.hibernate.Query;\n"
- "import org.hibernate.Session;\n"
- "import org.hibernate.SessionFactory;\n"
- "import org.hibernate.Transaction;\n"
- "import org.hibernate.cfg.Configuration;\n"
- "import org.hibernate.tool.hbm2ddl.SchemaExport;\n"
- "\n"
- "public class BlogMain {\n"
- " \n"
- " private SessionFactory _sessions;\n"
- " \n"
- " public void configure() throws HibernateException {\n"
- " _sessions = new Configuration()\n"
- " .addClass(Blog.class)\n"
- " .addClass(BlogItem.class)\n"
- " .buildSessionFactory();\n"
- " }\n"
- " \n"
- " public void exportTables() throws HibernateException {\n"
- " Configuration cfg = new Configuration()\n"
- " .addClass(Blog.class)\n"
- " .addClass(BlogItem.class);\n"
- " new SchemaExport(cfg).create(true, true);\n"
- " }\n"
- " \n"
- " public Blog createBlog(String name) throws HibernateException {\n"
- " \n"
- " Blog blog = new Blog();\n"
- " blog.setName(name);\n"
- " blog.setItems( new ArrayList() );\n"
- " \n"
- " Session session = _sessions.openSession();\n"
- " Transaction tx = null;\n"
- " try {\n"
- " tx = session.beginTransaction();\n"
- " session.persist(blog);\n"
- " tx.commit();\n"
- " }\n"
- " catch (HibernateException he) {\n"
- " if (tx!=null) tx.rollback();\n"
- " throw he;\n"
- " }\n"
- " finally {\n"
- " session.close();\n"
- " }\n"
- " return blog;\n"
- " }\n"
- " \n"
- " public BlogItem createBlogItem(Blog blog, String title, String text)\n"
- " throws HibernateException {\n"
- " \n"
- " BlogItem item = new BlogItem();\n"
- " item.setTitle(title);\n"
- " item.setText(text);\n"
- " item.setBlog(blog);\n"
- " item.setDatetime( Calendar.getInstance() );\n"
- " blog.getItems().add(item);\n"
- " \n"
- " Session session = _sessions.openSession();\n"
- " Transaction tx = null;\n"
- " try {\n"
- " tx = session.beginTransaction();\n"
- " session.update(blog);\n"
- " tx.commit();\n"
- " }\n"
- " catch (HibernateException he) {\n"
- " if (tx!=null) tx.rollback();\n"
- " throw he;\n"
- " }\n"
- " finally {\n"
- " session.close();\n"
- " }\n"
- " return item;\n"
- " }\n"
- " \n"
- " public BlogItem createBlogItem(Long blogid, String title, String text)\n"
- " throws HibernateException {\n"
- " \n"
- " BlogItem item = new BlogItem();\n"
- " item.setTitle(title);\n"
- " item.setText(text);\n"
- " item.setDatetime( Calendar.getInstance() );\n"
- " \n"
- " Session session = _sessions.openSession();\n"
- " Transaction tx = null;\n"
- " try {\n"
- " tx = session.beginTransaction();\n"
- " Blog blog = (Blog) session.load(Blog.class, blogid);\n"
- " item.setBlog(blog);\n"
- " blog.getItems().add(item);\n"
- " tx.commit();\n"
- " }\n"
- " catch (HibernateException he) {\n"
- " if (tx!=null) tx.rollback();\n"
- " throw he;\n"
- " }\n"
- " finally {\n"
- " session.close();\n"
- " }\n"
- " return item;\n"
- " }\n"
- " \n"
- " public void updateBlogItem(BlogItem item, String text)\n"
- " throws HibernateException {\n"
- " \n"
- " item.setText(text);\n"
- " \n"
- " Session session = _sessions.openSession();\n"
- " Transaction tx = null;\n"
- " try {\n"
- " tx = session.beginTransaction();\n"
- " session.update(item);\n"
- " tx.commit();\n"
- " }\n"
- " catch (HibernateException he) {\n"
- " if (tx!=null) tx.rollback();\n"
- " throw he;\n"
- " }\n"
- " finally {\n"
- " session.close();\n"
- " }\n"
- " }\n"
- " \n"
- " public void updateBlogItem(Long itemid, String text)\n"
- " throws HibernateException {\n"
- " \n"
- " Session session = _sessions.openSession();\n"
- " Transaction tx = null;\n"
- " try {\n"
- " tx = session.beginTransaction();\n"
- " BlogItem item = (BlogItem) session.load(BlogItem.class, itemid);\n"
- " item.setText(text);\n"
- " tx.commit();\n"
- " }\n"
- " catch (HibernateException he) {\n"
- " if (tx!=null) tx.rollback();\n"
- " throw he;\n"
- " }\n"
- " finally {\n"
- " session.close();\n"
- " }\n"
- " }\n"
- " \n"
- " public List listAllBlogNamesAndItemCounts(int max)\n"
- " throws HibernateException {\n"
- " \n"
- " Session session = _sessions.openSession();\n"
- " Transaction tx = null;\n"
- " List result = null;\n"
- " try {\n"
- " tx = session.beginTransaction();\n"
- " Query q = session.createQuery(\n"
- " \"select blog.id, blog.name, count(blogItem) \" +\n"
- " \"from Blog as blog \" +\n"
- " \"left outer join blog.items as blogItem \" +\n"
- " \"group by blog.name, blog.id \" +\n"
- " \"order by max(blogItem.datetime)\"\n"
- " );\n"
- " q.setMaxResults(max);\n"
- " result = q.list();\n"
- " tx.commit();\n"
- " }\n"
- " catch (HibernateException he) {\n"
- " if (tx!=null) tx.rollback();\n"
- " throw he;\n"
- " }\n"
- " finally {\n"
- " session.close();\n"
- " }\n"
- " return result;\n"
- " }\n"
- " \n"
- " public Blog getBlogAndAllItems(Long blogid)\n"
- " throws HibernateException {\n"
- " \n"
- " Session session = _sessions.openSession();\n"
- " Transaction tx = null;\n"
- " Blog blog = null;\n"
- " try {\n"
- " tx = session.beginTransaction();\n"
- " Query q = session.createQuery(\n"
- " \"from Blog as blog \" +\n"
- " \"left outer join fetch blog.items \" +\n"
- " \"where blog.id = :blogid\"\n"
- " );\n"
- " q.setParameter(\"blogid\", blogid);\n"
- " blog = (Blog) q.uniqueResult();\n"
- " tx.commit();\n"
- " }\n"
- " catch (HibernateException he) {\n"
- " if (tx!=null) tx.rollback();\n"
- " throw he;\n"
- " }\n"
- " finally {\n"
- " session.close();\n"
- " }\n"
- " return blog;\n"
- " }\n"
- " \n"
- " public List listBlogsAndRecentItems() throws HibernateException {\n"
- " \n"
- " Session session = _sessions.openSession();\n"
- " Transaction tx = null;\n"
- " List result = null;\n"
- " try {\n"
- " tx = session.beginTransaction();\n"
- " Query q = session.createQuery(\n"
- " \"from Blog as blog \" +\n"
- " \"inner join blog.items as blogItem \" +\n"
- " \"where blogItem.datetime > :minDate\"\n"
- " );\n"
- "\n"
- " Calendar cal = Calendar.getInstance();\n"
- " cal.roll(Calendar.MONTH, false);\n"
- " q.setCalendar(\"minDate\", cal);\n"
- " \n"
- " result = q.list();\n"
- " tx.commit();\n"
- " }\n"
- " catch (HibernateException he) {\n"
- " if (tx!=null) tx.rollback();\n"
- " throw he;\n"
- " }\n"
- " finally {\n"
- " session.close();\n"
- " }\n"
- " return result;\n"
- " }\n"
- "}]]>"
-msgstr ""
-
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/filters.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/filters.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/filters.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,198 +1,93 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-10 21:02+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:19\n"
+"PO-Revision-Date: 2010-01-08T04:07:19\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
-#: filters.xml:29
#, no-c-format
msgid "Filtering data"
msgstr ""
#. Tag: para
-#: filters.xml:31
#, no-c-format
msgid "Hibernate3 provides an innovative new approach to handling data with \"visibility\" rules. A <emphasis>Hibernate filter</emphasis> is a global, named, parameterized filter that can be enabled or disabled for a particular Hibernate session."
msgstr ""
#. Tag: title
-#: filters.xml:38
#, no-c-format
msgid "Hibernate filters"
msgstr ""
#. Tag: para
-#: filters.xml:40
#, no-c-format
msgid "Hibernate3 has the ability to pre-define filter criteria and attach those filters at both a class level and a collection level. A filter criteria allows you to define a restriction clause similar to the existing \"where\" attribute available on the class and various collection elements. These filter conditions, however, can be parameterized. The application can then decide at runtime whether certain filters should be enabled and what their parameter values should be. Filters can be used like database views, but they are parameterized inside the application."
msgstr ""
#. Tag: para
-#: filters.xml:50
#, no-c-format
msgid "In order to use filters, they must first be defined and then attached to the appropriate mapping elements. To define a filter, use the <literal><filter-def/></literal> element within a <literal><hibernate-mapping/></literal> element:"
msgstr ""
-#. Tag: programlisting
-#: filters.xml:56
-#, no-c-format
-msgid ""
- "<![CDATA[<filter-def name=\"myFilter\">\n"
- " <filter-param name=\"myFilterParam\" type=\"string\"/>\n"
- "</filter-def>]]>"
-msgstr ""
-
#. Tag: para
-#: filters.xml:58
#, no-c-format
msgid "This filter can then be attached to a class:"
msgstr ""
-#. Tag: programlisting
-#: filters.xml:62
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"myClass\" ...>\n"
- " ...\n"
- " <filter name=\"myFilter\" condition=\":myFilterParam = MY_FILTERED_COLUMN\"/>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: filters.xml:64
#, no-c-format
msgid "Or, to a collection:"
msgstr ""
-#. Tag: programlisting
-#: filters.xml:68
-#, no-c-format
-msgid ""
- "<![CDATA[<set ...>\n"
- " <filter name=\"myFilter\" condition=\":myFilterParam = MY_FILTERED_COLUMN\"/>\n"
- "</set>]]>"
-msgstr ""
-
#. Tag: para
-#: filters.xml:70
#, no-c-format
msgid "Or, to both or multiples of each at the same time."
msgstr ""
#. Tag: para
-#: filters.xml:74
#, no-c-format
msgid "The methods on <literal>Session</literal> are: <literal>enableFilter(String filterName)</literal>, <literal>getEnabledFilter(String filterName)</literal>, and <literal>disableFilter(String filterName)</literal>. By default, filters are <emphasis>not</emphasis> enabled for a given session. Filters must be enabled through use of the <literal>Session.enableFilter()</literal> method, which returns an instance of the <literal>Filter</literal> interface. If you used the simple filter defined above, it would look like this:"
msgstr ""
-#. Tag: programlisting
-#: filters.xml:83
-#, no-c-format
-msgid "<![CDATA[session.enableFilter(\"myFilter\").setParameter(\"myFilterParam\", \"some-value\");]]>"
-msgstr ""
-
#. Tag: para
-#: filters.xml:85
#, no-c-format
msgid "Methods on the org.hibernate.Filter interface do allow the method-chaining common to much of Hibernate."
msgstr ""
#. Tag: para
-#: filters.xml:89
#, no-c-format
msgid "The following is a full example, using temporal data with an effective record date pattern:"
msgstr ""
-#. Tag: programlisting
-#: filters.xml:93
-#, no-c-format
-msgid ""
- "<![CDATA[<filter-def name=\"effectiveDate\">\n"
- " <filter-param name=\"asOfDate\" type=\"date\"/>\n"
- "</filter-def>\n"
- "\n"
- "<class name=\"Employee\" ...>\n"
- "...\n"
- " <many-to-one name=\"department\" column=\"dept_id\" class=\"Department\"/>\n"
- " <property name=\"effectiveStartDate\" type=\"date\" column=\"eff_start_dt\"/>\n"
- " <property name=\"effectiveEndDate\" type=\"date\" column=\"eff_end_dt\"/>\n"
- "...\n"
- " <!--\n"
- " Note that this assumes non-terminal records have an eff_end_dt set to\n"
- " a max db date for simplicity-sake\n"
- " -->\n"
- " <filter name=\"effectiveDate\"\n"
- " condition=\":asOfDate BETWEEN eff_start_dt and eff_end_dt\"/>\n"
- "</class>\n"
- "\n"
- "<class name=\"Department\" ...>\n"
- "...\n"
- " <set name=\"employees\" lazy=\"true\">\n"
- " <key column=\"dept_id\"/>\n"
- " <one-to-many class=\"Employee\"/>\n"
- " <filter name=\"effectiveDate\"\n"
- " condition=\":asOfDate BETWEEN eff_start_dt and eff_end_dt\"/>\n"
- " </set>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: filters.xml:95
#, no-c-format
msgid "In order to ensure that you are provided with currently effective records, enable the filter on the session prior to retrieving employee data:"
msgstr ""
-#. Tag: programlisting
-#: filters.xml:100
-#, no-c-format
-msgid ""
- "<![CDATA[Session session = ...;\n"
- "session.enableFilter(\"effectiveDate\").setParameter(\"asOfDate\", new Date());\n"
- "List results = session.createQuery(\"from Employee as e where e.salary > :targetSalary\")\n"
- " .setLong(\"targetSalary\", new Long(1000000))\n"
- " .list();\n"
- "]]>"
-msgstr ""
-
#. Tag: para
-#: filters.xml:102
#, no-c-format
msgid "Even though a salary constraint was mentioned explicitly on the results in the above HQL, because of the enabled filter, the query will return only currently active employees who have a salary greater than one million dollars."
msgstr ""
#. Tag: para
-#: filters.xml:108
#, no-c-format
msgid "If you want to use filters with outer joining, either through HQL or load fetching, be careful of the direction of the condition expression. It is safest to set this up for left outer joining. Place the parameter first followed by the column name(s) after the operator."
msgstr ""
#. Tag: para
-#: filters.xml:115
#, no-c-format
msgid "After being defined, a filter might be attached to multiple entities and/or collections each with its own condition. This can be problematic when the conditions are the same each time. Using <literal><filter-def/></literal> allows you to definine a default condition, either as an attribute or CDATA:"
msgstr ""
-#. Tag: programlisting
-#: filters.xml:122
-#, no-c-format
-msgid ""
- "<![CDATA[<filter-def name=\"myFilter\" condition=\"abc > xyz\">...</filter-def>\n"
- "<filter-def name=\"myOtherFilter\">abc=xyz</filter-def>]]>"
-msgstr ""
-
#. Tag: para
-#: filters.xml:124
#, no-c-format
msgid "This default condition will be used whenever the filter is attached to something without specifying a condition. This means you can give a specific condition as part of the attachment of the filter that overrides the default condition in that particular case."
msgstr ""
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/inheritance_mapping.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/inheritance_mapping.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/inheritance_mapping.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,631 +1,279 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-16 18:47+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:19\n"
+"PO-Revision-Date: 2010-01-08T04:07:19\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
-#: inheritance_mapping.xml:29
#, no-c-format
msgid "Inheritance mapping"
msgstr ""
#. Tag: title
-#: inheritance_mapping.xml:32
#, no-c-format
msgid "The three strategies"
msgstr ""
#. Tag: para
-#: inheritance_mapping.xml:34
#, no-c-format
msgid "Hibernate supports the three basic inheritance mapping strategies:"
msgstr ""
#. Tag: para
-#: inheritance_mapping.xml:40
#, no-c-format
msgid "table per class hierarchy"
msgstr ""
#. Tag: para
-#: inheritance_mapping.xml:45
#, no-c-format
-msgid "<para>table per subclass</para>"
+msgid "table per subclass"
msgstr ""
#. Tag: para
-#: inheritance_mapping.xml:50
#, no-c-format
msgid "table per concrete class"
msgstr ""
#. Tag: para
-#: inheritance_mapping.xml:56
#, no-c-format
msgid "In addition, Hibernate supports a fourth, slightly different kind of polymorphism:"
msgstr ""
#. Tag: para
-#: inheritance_mapping.xml:63
#, no-c-format
msgid "implicit polymorphism"
msgstr ""
#. Tag: para
-#: inheritance_mapping.xml:69
#, no-c-format
msgid "It is possible to use different mapping strategies for different branches of the same inheritance hierarchy. You can then make use of implicit polymorphism to achieve polymorphism across the whole hierarchy. However, Hibernate does not support mixing <literal><subclass></literal>, <literal><joined-subclass></literal> and <literal><union-subclass></literal> mappings under the same root <literal><class></literal> element. It is possible to mix together the table per hierarchy and table per subclass strategies under the the same <literal><class></literal> element, by combining the <literal><subclass></literal> and <literal><join></literal> elements (see below for an example)."
msgstr ""
#. Tag: para
-#: inheritance_mapping.xml:83
#, no-c-format
msgid "It is possible to define <literal>subclass</literal>, <literal>union-subclass</literal>, and <literal>joined-subclass</literal> mappings in separate mapping documents directly beneath <literal>hibernate-mapping</literal>. This allows you to extend a class hierarchy by adding a new mapping file. You must specify an <literal>extends</literal> attribute in the subclass mapping, naming a previously mapped superclass. Previously this feature made the ordering of the mapping documents important. Since Hibernate3, the ordering of mapping files is irrelevant when using the extends keyword. The ordering inside a single mapping file still needs to be defined as superclasses before subclasses."
msgstr ""
-#. Tag: programlisting
-#: inheritance_mapping.xml:94
-#, no-c-format
-msgid ""
- "<![CDATA[\n"
- " <hibernate-mapping>\n"
- " <subclass name=\"DomesticCat\" extends=\"Cat\" discriminator-value=\"D\">\n"
- " <property name=\"name\" type=\"string\"/>\n"
- " </subclass>\n"
- " </hibernate-mapping>]]>"
-msgstr ""
-
#. Tag: title
-#: inheritance_mapping.xml:98
#, no-c-format
msgid "Table per class hierarchy"
msgstr ""
#. Tag: para
-#: inheritance_mapping.xml:100
#, no-c-format
msgid "Suppose we have an interface <literal>Payment</literal> with the implementors <literal>CreditCardPayment</literal>, <literal>CashPayment</literal>, and <literal>ChequePayment</literal>. The table per hierarchy mapping would display in the following way:"
msgstr ""
-#. Tag: programlisting
-#: inheritance_mapping.xml:107
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Payment\" table=\"PAYMENT\">\n"
- " <id name=\"id\" type=\"long\" column=\"PAYMENT_ID\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <discriminator column=\"PAYMENT_TYPE\" type=\"string\"/>\n"
- " <property name=\"amount\" column=\"AMOUNT\"/>\n"
- " ...\n"
- " <subclass name=\"CreditCardPayment\" discriminator-value=\"CREDIT\">\n"
- " <property name=\"creditCardType\" column=\"CCTYPE\"/>\n"
- " ...\n"
- " </subclass>\n"
- " <subclass name=\"CashPayment\" discriminator-value=\"CASH\">\n"
- " ...\n"
- " </subclass>\n"
- " <subclass name=\"ChequePayment\" discriminator-value=\"CHEQUE\">\n"
- " ...\n"
- " </subclass>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: inheritance_mapping.xml:109
#, no-c-format
msgid "Exactly one table is required. There is a limitation of this mapping strategy: columns declared by the subclasses, such as <literal>CCTYPE</literal>, cannot have <literal>NOT NULL</literal> constraints."
msgstr ""
#. Tag: title
-#: inheritance_mapping.xml:118
#, no-c-format
msgid "Table per subclass"
msgstr ""
#. Tag: para
-#: inheritance_mapping.xml:120
#, no-c-format
msgid "A table per subclass mapping looks like this:"
msgstr ""
-#. Tag: programlisting
-#: inheritance_mapping.xml:124
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Payment\" table=\"PAYMENT\">\n"
- " <id name=\"id\" type=\"long\" column=\"PAYMENT_ID\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <property name=\"amount\" column=\"AMOUNT\"/>\n"
- " ...\n"
- " <joined-subclass name=\"CreditCardPayment\" table=\"CREDIT_PAYMENT\">\n"
- " <key column=\"PAYMENT_ID\"/>\n"
- " <property name=\"creditCardType\" column=\"CCTYPE\"/>\n"
- " ...\n"
- " </joined-subclass>\n"
- " <joined-subclass name=\"CashPayment\" table=\"CASH_PAYMENT\">\n"
- " <key column=\"PAYMENT_ID\"/>\n"
- " ...\n"
- " </joined-subclass>\n"
- " <joined-subclass name=\"ChequePayment\" table=\"CHEQUE_PAYMENT\">\n"
- " <key column=\"PAYMENT_ID\"/>\n"
- " ...\n"
- " </joined-subclass>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: inheritance_mapping.xml:126
#, no-c-format
msgid "Four tables are required. The three subclass tables have primary key associations to the superclass table so the relational model is actually a one-to-one association."
msgstr ""
#. Tag: title
-#: inheritance_mapping.xml:135
#, no-c-format
msgid "Table per subclass: using a discriminator"
msgstr ""
#. Tag: para
-#: inheritance_mapping.xml:137
#, no-c-format
msgid "Hibernate's implementation of table per subclass does not require a discriminator column. Other object/relational mappers use a different implementation of table per subclass that requires a type discriminator column in the superclass table. The approach taken by Hibernate is much more difficult to implement, but arguably more correct from a relational point of view. If you want to use a discriminator column with the table per subclass strategy, you can combine the use of <literal><subclass></literal> and <literal><join></literal>, as follows:"
msgstr ""
-#. Tag: programlisting
-#: inheritance_mapping.xml:149
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Payment\" table=\"PAYMENT\">\n"
- " <id name=\"id\" type=\"long\" column=\"PAYMENT_ID\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <discriminator column=\"PAYMENT_TYPE\" type=\"string\"/>\n"
- " <property name=\"amount\" column=\"AMOUNT\"/>\n"
- " ...\n"
- " <subclass name=\"CreditCardPayment\" discriminator-value=\"CREDIT\">\n"
- " <join table=\"CREDIT_PAYMENT\">\n"
- " <key column=\"PAYMENT_ID\"/>\n"
- " <property name=\"creditCardType\" column=\"CCTYPE\"/>\n"
- " ...\n"
- " </join>\n"
- " </subclass>\n"
- " <subclass name=\"CashPayment\" discriminator-value=\"CASH\">\n"
- " <join table=\"CASH_PAYMENT\">\n"
- " <key column=\"PAYMENT_ID\"/>\n"
- " ...\n"
- " </join>\n"
- " </subclass>\n"
- " <subclass name=\"ChequePayment\" discriminator-value=\"CHEQUE\">\n"
- " <join table=\"CHEQUE_PAYMENT\" fetch=\"select\">\n"
- " <key column=\"PAYMENT_ID\"/>\n"
- " ...\n"
- " </join>\n"
- " </subclass>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: inheritance_mapping.xml:151
#, no-c-format
msgid "The optional <literal>fetch=\"select\"</literal> declaration tells Hibernate not to fetch the <literal>ChequePayment</literal> subclass data using an outer join when querying the superclass."
msgstr ""
#. Tag: title
-#: inheritance_mapping.xml:160
#, no-c-format
msgid "Mixing table per class hierarchy with table per subclass"
msgstr ""
#. Tag: para
-#: inheritance_mapping.xml:162
#, no-c-format
msgid "You can even mix the table per hierarchy and table per subclass strategies using the following approach:"
msgstr ""
-#. Tag: programlisting
-#: inheritance_mapping.xml:167
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Payment\" table=\"PAYMENT\">\n"
- " <id name=\"id\" type=\"long\" column=\"PAYMENT_ID\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <discriminator column=\"PAYMENT_TYPE\" type=\"string\"/>\n"
- " <property name=\"amount\" column=\"AMOUNT\"/>\n"
- " ...\n"
- " <subclass name=\"CreditCardPayment\" discriminator-value=\"CREDIT\">\n"
- " <join table=\"CREDIT_PAYMENT\">\n"
- " <property name=\"creditCardType\" column=\"CCTYPE\"/>\n"
- " ...\n"
- " </join>\n"
- " </subclass>\n"
- " <subclass name=\"CashPayment\" discriminator-value=\"CASH\">\n"
- " ...\n"
- " </subclass>\n"
- " <subclass name=\"ChequePayment\" discriminator-value=\"CHEQUE\">\n"
- " ...\n"
- " </subclass>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: inheritance_mapping.xml:169
#, no-c-format
msgid "For any of these mapping strategies, a polymorphic association to the root <literal>Payment</literal> class is mapped using <literal><many-to-one></literal>."
msgstr ""
-#. Tag: programlisting
-#: inheritance_mapping.xml:175
-#, no-c-format
-msgid "<![CDATA[<many-to-one name=\"payment\" column=\"PAYMENT_ID\" class=\"Payment\"/>]]>"
-msgstr ""
-
#. Tag: title
-#: inheritance_mapping.xml:180
#, no-c-format
msgid "Table per concrete class"
msgstr ""
#. Tag: para
-#: inheritance_mapping.xml:182
#, no-c-format
msgid "There are two ways we can map the table per concrete class strategy. First, you can use <literal><union-subclass></literal>."
msgstr ""
-#. Tag: programlisting
-#: inheritance_mapping.xml:187
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Payment\">\n"
- " <id name=\"id\" type=\"long\" column=\"PAYMENT_ID\">\n"
- " <generator class=\"sequence\"/>\n"
- " </id>\n"
- " <property name=\"amount\" column=\"AMOUNT\"/>\n"
- " ...\n"
- " <union-subclass name=\"CreditCardPayment\" table=\"CREDIT_PAYMENT\">\n"
- " <property name=\"creditCardType\" column=\"CCTYPE\"/>\n"
- " ...\n"
- " </union-subclass>\n"
- " <union-subclass name=\"CashPayment\" table=\"CASH_PAYMENT\">\n"
- " ...\n"
- " </union-subclass>\n"
- " <union-subclass name=\"ChequePayment\" table=\"CHEQUE_PAYMENT\">\n"
- " ...\n"
- " </union-subclass>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: inheritance_mapping.xml:189
#, no-c-format
msgid "Three tables are involved for the subclasses. Each table defines columns for all properties of the class, including inherited properties."
msgstr ""
#. Tag: para
-#: inheritance_mapping.xml:194
#, no-c-format
msgid "The limitation of this approach is that if a property is mapped on the superclass, the column name must be the same on all subclass tables. The identity generator strategy is not allowed in union subclass inheritance. The primary key seed has to be shared across all unioned subclasses of a hierarchy."
msgstr ""
#. Tag: para
-#: inheritance_mapping.xml:203
#, no-c-format
msgid "If your superclass is abstract, map it with <literal>abstract=\"true\"</literal>. If it is not abstract, an additional table (it defaults to <literal>PAYMENT</literal> in the example above), is needed to hold instances of the superclass."
msgstr ""
#. Tag: title
-#: inheritance_mapping.xml:213
#, no-c-format
msgid "Table per concrete class using implicit polymorphism"
msgstr ""
#. Tag: para
-#: inheritance_mapping.xml:215
#, no-c-format
msgid "An alternative approach is to make use of implicit polymorphism:"
msgstr ""
-#. Tag: programlisting
-#: inheritance_mapping.xml:219
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"CreditCardPayment\" table=\"CREDIT_PAYMENT\">\n"
- " <id name=\"id\" type=\"long\" column=\"CREDIT_PAYMENT_ID\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <property name=\"amount\" column=\"CREDIT_AMOUNT\"/>\n"
- " ...\n"
- "</class>\n"
- "\n"
- "<class name=\"CashPayment\" table=\"CASH_PAYMENT\">\n"
- " <id name=\"id\" type=\"long\" column=\"CASH_PAYMENT_ID\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <property name=\"amount\" column=\"CASH_AMOUNT\"/>\n"
- " ...\n"
- "</class>\n"
- "\n"
- "<class name=\"ChequePayment\" table=\"CHEQUE_PAYMENT\">\n"
- " <id name=\"id\" type=\"long\" column=\"CHEQUE_PAYMENT_ID\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <property name=\"amount\" column=\"CHEQUE_AMOUNT\"/>\n"
- " ...\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: inheritance_mapping.xml:221
#, no-c-format
-msgid "Notice that the <literal>Payment</literal> interface is not mentioned explicitly. Also notice that properties of <literal>Payment</literal> are mapped in each of the subclasses. If you want to avoid duplication, consider using XML entities (for example, <literal>[ <!ENTITY allproperties SYSTEM \"allproperties.xml\"> ]</literal> in the <literal>DOCTYPE</literal> declaration and <literal>&allproperties;</literal> in the mapping)."
+msgid "Notice that the <literal>Payment</literal> interface is not mentioned explicitly. Also notice that properties of <literal>Payment</literal> are mapped in each of the subclasses. If you want to avoid duplication, consider using XML entities (for example, <literal>[ <!ENTITY allproperties SYSTEM \"allproperties.xml\"> ]</literal> in the <literal>DOCTYPE</literal> declaration and <literal>&allproperties;</literal> in the mapping)."
msgstr ""
#. Tag: para
-#: inheritance_mapping.xml:231
#, no-c-format
msgid "The disadvantage of this approach is that Hibernate does not generate SQL <literal>UNION</literal>s when performing polymorphic queries."
msgstr ""
#. Tag: para
-#: inheritance_mapping.xml:236
#, no-c-format
msgid "For this mapping strategy, a polymorphic association to <literal>Payment</literal> is usually mapped using <literal><any></literal>."
msgstr ""
-#. Tag: programlisting
-#: inheritance_mapping.xml:241
-#, no-c-format
-msgid ""
- "<![CDATA[<any name=\"payment\" meta-type=\"string\" id-type=\"long\">\n"
- " <meta-value value=\"CREDIT\" class=\"CreditCardPayment\"/>\n"
- " <meta-value value=\"CASH\" class=\"CashPayment\"/>\n"
- " <meta-value value=\"CHEQUE\" class=\"ChequePayment\"/>\n"
- " <column name=\"PAYMENT_CLASS\"/>\n"
- " <column name=\"PAYMENT_ID\"/>\n"
- "</any>]]>"
-msgstr ""
-
#. Tag: title
-#: inheritance_mapping.xml:246
#, no-c-format
msgid "Mixing implicit polymorphism with other inheritance mappings"
msgstr ""
#. Tag: para
-#: inheritance_mapping.xml:248
#, no-c-format
msgid "Since the subclasses are each mapped in their own <literal><class></literal> element, and since <literal>Payment</literal> is just an interface), each of the subclasses could easily be part of another inheritance hierarchy. You can still use polymorphic queries against the <literal>Payment</literal> interface."
msgstr ""
-#. Tag: programlisting
-#: inheritance_mapping.xml:256
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"CreditCardPayment\" table=\"CREDIT_PAYMENT\">\n"
- " <id name=\"id\" type=\"long\" column=\"CREDIT_PAYMENT_ID\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <discriminator column=\"CREDIT_CARD\" type=\"string\"/>\n"
- " <property name=\"amount\" column=\"CREDIT_AMOUNT\"/>\n"
- " ...\n"
- " <subclass name=\"MasterCardPayment\" discriminator-value=\"MDC\"/>\n"
- " <subclass name=\"VisaPayment\" discriminator-value=\"VISA\"/>\n"
- "</class>\n"
- "\n"
- "<class name=\"NonelectronicTransaction\" table=\"NONELECTRONIC_TXN\">\n"
- " <id name=\"id\" type=\"long\" column=\"TXN_ID\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " ...\n"
- " <joined-subclass name=\"CashPayment\" table=\"CASH_PAYMENT\">\n"
- " <key column=\"PAYMENT_ID\"/>\n"
- " <property name=\"amount\" column=\"CASH_AMOUNT\"/>\n"
- " ...\n"
- " </joined-subclass>\n"
- " <joined-subclass name=\"ChequePayment\" table=\"CHEQUE_PAYMENT\">\n"
- " <key column=\"PAYMENT_ID\"/>\n"
- " <property name=\"amount\" column=\"CHEQUE_AMOUNT\"/>\n"
- " ...\n"
- " </joined-subclass>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: inheritance_mapping.xml:258
#, no-c-format
msgid "Once again, <literal>Payment</literal> is not mentioned explicitly. If we execute a query against the <literal>Payment</literal> interface, for example <literal>from Payment</literal>, Hibernate automatically returns instances of <literal>CreditCardPayment</literal> (and its subclasses, since they also implement <literal>Payment</literal>), <literal>CashPayment</literal> and <literal>ChequePayment</literal>, but not instances of <literal>NonelectronicTransaction</literal>."
msgstr ""
#. Tag: title
-#: inheritance_mapping.xml:273
#, no-c-format
msgid "Limitations"
msgstr ""
#. Tag: para
-#: inheritance_mapping.xml:275
#, no-c-format
msgid "There are limitations to the \"implicit polymorphism\" approach to the table per concrete-class mapping strategy. There are somewhat less restrictive limitations to <literal><union-subclass></literal> mappings."
msgstr ""
#. Tag: para
-#: inheritance_mapping.xml:282
#, no-c-format
-msgid "The following table shows the limitations of table per concrete-class mappings, and of implicit polymorphism, in Hibernate."
+msgid "The following list shows the limitations of table per concrete-class mappings, and of implicit polymorphism, in Hibernate."
msgstr ""
-#. Tag: title
-#: inheritance_mapping.xml:288
+#. Tag: term
#, no-c-format
-msgid "Features of inheritance mappings"
+msgid "table per class-heirarchy"
msgstr ""
-#. Tag: entry
-#: inheritance_mapping.xml:301
+#. Tag: para
#, no-c-format
-msgid "Inheritance strategy"
+msgid "Polymorphic many-to-one: <code><many-to-one></code>"
msgstr ""
-#. Tag: entry
-#: inheritance_mapping.xml:302
+#. Tag: para
#, no-c-format
-msgid "Polymorphic many-to-one"
+msgid "Polymorphic one-to-one: <code><one-to-one></code>"
msgstr ""
-#. Tag: entry
-#: inheritance_mapping.xml:303
+#. Tag: para
#, no-c-format
-msgid "Polymorphic one-to-one"
+msgid "Polymorphic one-to-many: <code><one-to-many></code>"
msgstr ""
-#. Tag: entry
-#: inheritance_mapping.xml:304
+#. Tag: para
#, no-c-format
-msgid "Polymorphic one-to-many"
+msgid "Polymorphic many-to-many: <code><many-to-many></code>"
msgstr ""
-#. Tag: entry
-#: inheritance_mapping.xml:305
+#. Tag: para
#, no-c-format
-msgid "Polymorphic many-to-many"
+msgid "Polymorphic <literal>load()</literal> or <literal>get()</literal>: <code>s.get(Payment.class, id)</code>"
msgstr ""
-#. Tag: entry
-#: inheritance_mapping.xml:306
+#. Tag: para
#, no-c-format
-msgid "Polymorphic <literal>load()/get()</literal>"
+msgid "Polymorphic queries: <code>from Payment p</code>"
msgstr ""
-#. Tag: entry
-#: inheritance_mapping.xml:307
+#. Tag: para
#, no-c-format
-msgid "Polymorphic queries"
+msgid "Polymorphic joins: <code>from Order o join o.payment p</code>"
msgstr ""
-#. Tag: entry
-#: inheritance_mapping.xml:308
+#. Tag: para
#, no-c-format
-msgid "Polymorphic joins"
+msgid "Outer join fetching is supported."
msgstr ""
-#. Tag: entry
-#: inheritance_mapping.xml:309
+#. Tag: term
#, no-c-format
-msgid "Outer join fetching"
-msgstr ""
-
-#. Tag: entry
-#: inheritance_mapping.xml:314
-#, no-c-format
-msgid "table per class-hierarchy"
-msgstr ""
-
-#. Tag: literal
-#: inheritance_mapping.xml:315 inheritance_mapping.xml:326 inheritance_mapping.xml:337
-#, no-c-format
-msgid "<many-to-one>"
-msgstr ""
-
-#. Tag: literal
-#: inheritance_mapping.xml:316 inheritance_mapping.xml:327 inheritance_mapping.xml:338
-#, no-c-format
-msgid "<one-to-one>"
-msgstr ""
-
-#. Tag: literal
-#: inheritance_mapping.xml:317 inheritance_mapping.xml:328
-#, no-c-format
-msgid "<one-to-many>"
-msgstr ""
-
-#. Tag: literal
-#: inheritance_mapping.xml:318 inheritance_mapping.xml:329 inheritance_mapping.xml:340
-#, no-c-format
-msgid "<many-to-many>"
-msgstr ""
-
-#. Tag: literal
-#: inheritance_mapping.xml:319 inheritance_mapping.xml:330 inheritance_mapping.xml:341
-#, no-c-format
-msgid "s.get(Payment.class, id)"
-msgstr ""
-
-#. Tag: literal
-#: inheritance_mapping.xml:320 inheritance_mapping.xml:331 inheritance_mapping.xml:342 inheritance_mapping.xml:353
-#, no-c-format
-msgid "from Payment p"
-msgstr ""
-
-#. Tag: literal
-#: inheritance_mapping.xml:321 inheritance_mapping.xml:332 inheritance_mapping.xml:343
-#, no-c-format
-msgid "from Order o join o.payment p"
-msgstr ""
-
-#. Tag: emphasis
-#: inheritance_mapping.xml:322 inheritance_mapping.xml:333 inheritance_mapping.xml:344
-#, no-c-format
-msgid "supported"
-msgstr ""
-
-#. Tag: entry
-#: inheritance_mapping.xml:325
-#, no-c-format
-msgid "<entry>table per subclass</entry>"
-msgstr ""
-
-#. Tag: entry
-#: inheritance_mapping.xml:336
-#, no-c-format
msgid "table per concrete-class (union-subclass)"
msgstr ""
-#. Tag: entry
-#: inheritance_mapping.xml:339
+#. Tag: para
#, no-c-format
-msgid "<literal><one-to-many></literal> (for <literal>inverse=\"true\"</literal> only)"
+msgid "Polymorphic one-to-many: <code><one-to-many></code> (for <code>inverse=\"true\"</code> only)"
msgstr ""
-#. Tag: entry
-#: inheritance_mapping.xml:347
+#. Tag: term
#, no-c-format
-msgid "table per concrete class (implicit polymorphism)"
+msgid "table per concrete class (implicit polymorphism"
msgstr ""
-#. Tag: literal
-#: inheritance_mapping.xml:348
+#. Tag: para
#, no-c-format
-msgid "<any>"
+msgid "Polymorphic many-to-one: <code><any></code>"
msgstr ""
-#. Tag: emphasis
-#: inheritance_mapping.xml:349 inheritance_mapping.xml:350 inheritance_mapping.xml:354 inheritance_mapping.xml:355
+#. Tag: para
#, no-c-format
-msgid "not supported"
+msgid "Polymorphic <literal>load()</literal> or <literal>get()</literal>: <code>s.createCriteria(Payment.class).add( Restrictions.idEq(id) ).uniqueResult()</code>"
msgstr ""
-#. Tag: literal
-#: inheritance_mapping.xml:351
+#. Tag: para
#, no-c-format
-msgid "<many-to-any>"
+msgid "Polymorphic one-to-one, polymorphic one-to-many, polymorphic joins, and outer join fetching are not supported."
msgstr ""
-#. Tag: literal
-#: inheritance_mapping.xml:352
-#, no-c-format
-msgid "s.createCriteria(Payment.class).add( Restrictions.idEq(id) ).uniqueResult()"
-msgstr ""
-
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/performance.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/performance.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/performance.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,1561 +1,1033 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-10 21:02+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:19\n"
+"PO-Revision-Date: 2010-01-08T04:07:19\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
-#: performance.xml:29
#, no-c-format
msgid "Improving performance"
msgstr ""
#. Tag: title
-#: performance.xml:32
#, no-c-format
msgid "Fetching strategies"
msgstr ""
#. Tag: para
-#: performance.xml:34
#, no-c-format
msgid "Hibernate uses a <emphasis>fetching strategy</emphasis> to retrieve associated objects if the application needs to navigate the association. Fetch strategies can be declared in the O/R mapping metadata, or over-ridden by a particular HQL or <literal>Criteria</literal> query."
msgstr ""
#. Tag: para
-#: performance.xml:41
#, no-c-format
msgid "Hibernate3 defines the following fetching strategies:"
msgstr ""
#. Tag: para
-#: performance.xml:47
#, no-c-format
msgid "<emphasis>Join fetching</emphasis>: Hibernate retrieves the associated instance or collection in the same <literal>SELECT</literal>, using an <literal>OUTER JOIN</literal>."
msgstr ""
#. Tag: para
-#: performance.xml:54
#, no-c-format
msgid "<emphasis>Select fetching</emphasis>: a second <literal>SELECT</literal> is used to retrieve the associated entity or collection. Unless you explicitly disable lazy fetching by specifying <literal>lazy=\"false\"</literal>, this second select will only be executed when you access the association."
msgstr ""
#. Tag: para
-#: performance.xml:63
#, no-c-format
msgid "<emphasis>Subselect fetching</emphasis>: a second <literal>SELECT</literal> is used to retrieve the associated collections for all entities retrieved in a previous query or fetch. Unless you explicitly disable lazy fetching by specifying <literal>lazy=\"false\"</literal>, this second select will only be executed when you access the association."
msgstr ""
#. Tag: para
-#: performance.xml:72
#, no-c-format
msgid "<emphasis>Batch fetching</emphasis>: an optimization strategy for select fetching. Hibernate retrieves a batch of entity instances or collections in a single <literal>SELECT</literal> by specifying a list of primary or foreign keys."
msgstr ""
#. Tag: para
-#: performance.xml:81
#, no-c-format
msgid "Hibernate also distinguishes between:"
msgstr ""
#. Tag: para
-#: performance.xml:87
#, no-c-format
msgid "<emphasis>Immediate fetching</emphasis>: an association, collection or attribute is fetched immediately when the owner is loaded."
msgstr ""
#. Tag: para
-#: performance.xml:93
#, no-c-format
msgid "<emphasis>Lazy collection fetching</emphasis>: a collection is fetched when the application invokes an operation upon that collection. This is the default for collections."
msgstr ""
#. Tag: para
-#: performance.xml:100
#, no-c-format
msgid "<emphasis>\"Extra-lazy\" collection fetching</emphasis>: individual elements of the collection are accessed from the database as needed. Hibernate tries not to fetch the whole collection into memory unless absolutely needed. It is suitable for large collections."
msgstr ""
#. Tag: para
-#: performance.xml:108
#, no-c-format
msgid "<emphasis>Proxy fetching</emphasis>: a single-valued association is fetched when a method other than the identifier getter is invoked upon the associated object."
msgstr ""
#. Tag: para
-#: performance.xml:115
#, no-c-format
msgid "<emphasis>\"No-proxy\" fetching</emphasis>: a single-valued association is fetched when the instance variable is accessed. Compared to proxy fetching, this approach is less lazy; the association is fetched even when only the identifier is accessed. It is also more transparent, since no proxy is visible to the application. This approach requires buildtime bytecode instrumentation and is rarely necessary."
msgstr ""
#. Tag: para
-#: performance.xml:125
#, no-c-format
msgid "<emphasis>Lazy attribute fetching</emphasis>: an attribute or single valued association is fetched when the instance variable is accessed. This approach requires buildtime bytecode instrumentation and is rarely necessary."
msgstr ""
#. Tag: para
-#: performance.xml:134
#, no-c-format
msgid "We have two orthogonal notions here: <emphasis>when</emphasis> is the association fetched and <emphasis>how</emphasis> is it fetched. It is important that you do not confuse them. We use <literal>fetch</literal> to tune performance. We can use <literal>lazy</literal> to define a contract for what data is always available in any detached instance of a particular class."
msgstr ""
#. Tag: title
-#: performance.xml:143
#, no-c-format
msgid "Working with lazy associations"
msgstr ""
#. Tag: para
-#: performance.xml:145
#, no-c-format
msgid "By default, Hibernate3 uses lazy select fetching for collections and lazy proxy fetching for single-valued associations. These defaults make sense for most associations in the majority of applications."
msgstr ""
#. Tag: para
-#: performance.xml:151
#, no-c-format
msgid "If you set <literal>hibernate.default_batch_fetch_size</literal>, Hibernate will use the batch fetch optimization for lazy fetching. This optimization can also be enabled at a more granular level."
msgstr ""
#. Tag: para
-#: performance.xml:158
#, no-c-format
msgid "Please be aware that access to a lazy association outside of the context of an open Hibernate session will result in an exception. For example:"
msgstr ""
-#. Tag: programlisting
-#: performance.xml:164
-#, no-c-format
-msgid ""
- "<![CDATA[s = sessions.openSession();\n"
- "Transaction tx = s.beginTransaction();\n"
- " \n"
- "User u = (User) s.createQuery(\"from User u where u.name=:userName\")\n"
- " .setString(\"userName\", userName).uniqueResult();\n"
- "Map permissions = u.getPermissions();\n"
- "\n"
- "tx.commit();\n"
- "s.close();\n"
- "\n"
- "Integer accessLevel = (Integer) permissions.get(\"accounts\"); // Error!]]>"
-msgstr ""
-
#. Tag: para
-#: performance.xml:166
#, no-c-format
msgid "Since the permissions collection was not initialized when the <literal>Session</literal> was closed, the collection will not be able to load its state. <emphasis>Hibernate does not support lazy initialization for detached objects</emphasis>. This can be fixed by moving the code that reads from the collection to just before the transaction is committed."
msgstr ""
#. Tag: para
-#: performance.xml:174
#, no-c-format
msgid "Alternatively, you can use a non-lazy collection or association, by specifying <literal>lazy=\"false\"</literal> for the association mapping. However, it is intended that lazy initialization be used for almost all collections and associations. If you define too many non-lazy associations in your object model, Hibernate will fetch the entire database into memory in every transaction."
msgstr ""
#. Tag: para
-#: performance.xml:183
#, no-c-format
msgid "On the other hand, you can use join fetching, which is non-lazy by nature, instead of select fetching in a particular transaction. We will now explain how to customize the fetching strategy. In Hibernate3, the mechanisms for choosing a fetch strategy are identical for single-valued associations and collections."
msgstr ""
#. Tag: title
-#: performance.xml:194
#, no-c-format
msgid "Tuning fetch strategies"
msgstr ""
#. Tag: para
-#: performance.xml:196
#, no-c-format
msgid "Select fetching (the default) is extremely vulnerable to N+1 selects problems, so we might want to enable join fetching in the mapping document:"
msgstr ""
-#. Tag: programlisting
-#: performance.xml:201
-#, no-c-format
-msgid ""
- "<![CDATA[<set name=\"permissions\" \n"
- " fetch=\"join\">\n"
- " <key column=\"userId\"/>\n"
- " <one-to-many class=\"Permission\"/>\n"
- "</set]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: performance.xml:203
-#, no-c-format
-msgid "<![CDATA[<many-to-one name=\"mother\" class=\"Cat\" fetch=\"join\"/>]]>"
-msgstr ""
-
#. Tag: para
-#: performance.xml:205
#, no-c-format
msgid "The <literal>fetch</literal> strategy defined in the mapping document affects:"
msgstr ""
#. Tag: para
-#: performance.xml:211
#, no-c-format
msgid "retrieval via <literal>get()</literal> or <literal>load()</literal>"
msgstr ""
#. Tag: para
-#: performance.xml:216
#, no-c-format
msgid "retrieval that happens implicitly when an association is navigated"
msgstr ""
#. Tag: para
-#: performance.xml:221
#, no-c-format
msgid "<literal>Criteria</literal> queries"
msgstr ""
#. Tag: para
-#: performance.xml:226
#, no-c-format
msgid "HQL queries if <literal>subselect</literal> fetching is used"
msgstr ""
#. Tag: para
-#: performance.xml:232
#, no-c-format
msgid "Irrespective of the fetching strategy you use, the defined non-lazy graph is guaranteed to be loaded into memory. This might, however, result in several immediate selects being used to execute a particular HQL query."
msgstr ""
#. Tag: para
-#: performance.xml:238
#, no-c-format
msgid "Usually, the mapping document is not used to customize fetching. Instead, we keep the default behavior, and override it for a particular transaction, using <literal>left join fetch</literal> in HQL. This tells Hibernate to fetch the association eagerly in the first select, using an outer join. In the <literal>Criteria</literal> query API, you would use <literal>setFetchMode(FetchMode.JOIN)</literal>."
msgstr ""
#. Tag: para
-#: performance.xml:247
#, no-c-format
msgid "If you want to change the fetching strategy used by <literal>get()</literal> or <literal>load()</literal>, you can use a <literal>Criteria</literal> query. For example:"
msgstr ""
-#. Tag: programlisting
-#: performance.xml:253
-#, no-c-format
-msgid ""
- "<![CDATA[User user = (User) session.createCriteria(User.class)\n"
- " .setFetchMode(\"permissions\", FetchMode.JOIN)\n"
- " .add( Restrictions.idEq(userId) )\n"
- " .uniqueResult();]]>"
-msgstr ""
-
#. Tag: para
-#: performance.xml:255
#, no-c-format
msgid "This is Hibernate's equivalent of what some ORM solutions call a \"fetch plan\"."
msgstr ""
#. Tag: para
-#: performance.xml:259
#, no-c-format
msgid "A completely different approach to problems with N+1 selects is to use the second-level cache."
msgstr ""
#. Tag: title
-#: performance.xml:267
#, no-c-format
msgid "Single-ended association proxies"
msgstr ""
#. Tag: para
-#: performance.xml:269
#, no-c-format
msgid "Lazy fetching for collections is implemented using Hibernate's own implementation of persistent collections. However, a different mechanism is needed for lazy behavior in single-ended associations. The target entity of the association must be proxied. Hibernate implements lazy initializing proxies for persistent objects using runtime bytecode enhancement which is accessed via the CGLIB library."
msgstr ""
#. Tag: para
-#: performance.xml:277
#, no-c-format
msgid "At startup, Hibernate3 generates proxies by default for all persistent classes and uses them to enable lazy fetching of <literal>many-to-one</literal> and <literal>one-to-one</literal> associations."
msgstr ""
#. Tag: para
-#: performance.xml:283
#, no-c-format
msgid "The mapping file may declare an interface to use as the proxy interface for that class, with the <literal>proxy</literal> attribute. By default, Hibernate uses a subclass of the class. <emphasis>The proxied class must implement a default constructor with at least package visibility. This constructor is recommended for all persistent classes</emphasis>."
msgstr ""
#. Tag: para
-#: performance.xml:290
#, no-c-format
msgid "There are potential problems to note when extending this approach to polymorphic classes.For example:"
msgstr ""
-#. Tag: programlisting
-#: performance.xml:294
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Cat\" proxy=\"Cat\">\n"
- " ......\n"
- " <subclass name=\"DomesticCat\">\n"
- " .....\n"
- " </subclass>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: performance.xml:296
#, no-c-format
msgid "Firstly, instances of <literal>Cat</literal> will never be castable to <literal>DomesticCat</literal>, even if the underlying instance is an instance of <literal>DomesticCat</literal>:"
msgstr ""
-#. Tag: programlisting
-#: performance.xml:302
-#, no-c-format
-msgid ""
- "<![CDATA[Cat cat = (Cat) session.load(Cat.class, id); // instantiate a proxy (does not hit the db)\n"
- "if ( cat.isDomesticCat() ) { // hit the db to initialize the proxy\n"
- " DomesticCat dc = (DomesticCat) cat; // Error!\n"
- " ....\n"
- "}]]>"
-msgstr ""
-
#. Tag: para
-#: performance.xml:304
#, no-c-format
msgid "Secondly, it is possible to break proxy <literal>==</literal>:"
msgstr ""
-#. Tag: programlisting
-#: performance.xml:308
-#, no-c-format
-msgid ""
- "<![CDATA[Cat cat = (Cat) session.load(Cat.class, id); // instantiate a Cat proxy\n"
- "DomesticCat dc = \n"
- " (DomesticCat) session.load(DomesticCat.class, id); // acquire new DomesticCat proxy!\n"
- "System.out.println(cat==dc); // false]]>"
-msgstr ""
-
#. Tag: para
-#: performance.xml:310
#, no-c-format
msgid "However, the situation is not quite as bad as it looks. Even though we now have two references to different proxy objects, the underlying instance will still be the same object:"
msgstr ""
-#. Tag: programlisting
-#: performance.xml:315
-#, no-c-format
-msgid ""
- "<![CDATA[cat.setWeight(11.0); // hit the db to initialize the proxy\n"
- "System.out.println( dc.getWeight() ); // 11.0]]>"
-msgstr ""
-
#. Tag: para
-#: performance.xml:317
#, no-c-format
msgid "Third, you cannot use a CGLIB proxy for a <literal>final</literal> class or a class with any <literal>final</literal> methods."
msgstr ""
#. Tag: para
-#: performance.xml:322
#, no-c-format
msgid "Finally, if your persistent object acquires any resources upon instantiation (e.g. in initializers or default constructor), then those resources will also be acquired by the proxy. The proxy class is an actual subclass of the persistent class."
msgstr ""
#. Tag: para
-#: performance.xml:328
#, no-c-format
msgid "These problems are all due to fundamental limitations in Java's single inheritance model. To avoid these problems your persistent classes must each implement an interface that declares its business methods. You should specify these interfaces in the mapping file where <literal>CatImpl</literal> implements the interface <literal>Cat</literal> and <literal>DomesticCatImpl</literal> implements the interface <literal>DomesticCat</literal>. For example:"
msgstr ""
-#. Tag: programlisting
-#: performance.xml:336
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"CatImpl\" proxy=\"Cat\">\n"
- " ......\n"
- " <subclass name=\"DomesticCatImpl\" proxy=\"DomesticCat\">\n"
- " .....\n"
- " </subclass>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: performance.xml:338
#, no-c-format
msgid "Then proxies for instances of <literal>Cat</literal> and <literal>DomesticCat</literal> can be returned by <literal>load()</literal> or <literal>iterate()</literal>."
msgstr ""
-#. Tag: programlisting
-#: performance.xml:343
-#, no-c-format
-msgid ""
- "<![CDATA[Cat cat = (Cat) session.load(CatImpl.class, catid);\n"
- "Iterator iter = session.createQuery(\"from CatImpl as cat where cat.name='fritz'\").iterate();\n"
- "Cat fritz = (Cat) iter.next();]]>"
-msgstr ""
-
#. Tag: title
-#: performance.xml:346
#, no-c-format
msgid "Note"
msgstr ""
#. Tag: para
-#: performance.xml:347
#, no-c-format
msgid "<literal>list()</literal> does not usually return proxies."
msgstr ""
#. Tag: para
-#: performance.xml:352
#, no-c-format
msgid "Relationships are also lazily initialized. This means you must declare any properties to be of type <literal>Cat</literal>, not <literal>CatImpl</literal>."
msgstr ""
#. Tag: para
-#: performance.xml:357
#, no-c-format
msgid "Certain operations do <emphasis>not</emphasis> require proxy initialization:"
msgstr ""
#. Tag: para
-#: performance.xml:363
#, no-c-format
msgid "<literal>equals()</literal>: if the persistent class does not override <literal>equals()</literal>"
msgstr ""
#. Tag: para
-#: performance.xml:369
#, no-c-format
msgid "<literal>hashCode()</literal>: if the persistent class does not override <literal>hashCode()</literal>"
msgstr ""
#. Tag: para
-#: performance.xml:375
#, no-c-format
msgid "The identifier getter method"
msgstr ""
#. Tag: para
-#: performance.xml:381
#, no-c-format
msgid "Hibernate will detect persistent classes that override <literal>equals()</literal> or <literal>hashCode()</literal>."
msgstr ""
#. Tag: para
-#: performance.xml:386
#, no-c-format
msgid "By choosing <literal>lazy=\"no-proxy\"</literal> instead of the default <literal>lazy=\"proxy\"</literal>, you can avoid problems associated with typecasting. However, buildtime bytecode instrumentation is required, and all operations will result in immediate proxy initialization."
msgstr ""
#. Tag: title
-#: performance.xml:396
#, no-c-format
msgid "Initializing collections and proxies"
msgstr ""
#. Tag: para
-#: performance.xml:398
#, no-c-format
msgid "A <literal>LazyInitializationException</literal> will be thrown by Hibernate if an uninitialized collection or proxy is accessed outside of the scope of the <literal>Session</literal>, i.e., when the entity owning the collection or having the reference to the proxy is in the detached state."
msgstr ""
#. Tag: para
-#: performance.xml:404
#, no-c-format
msgid "Sometimes a proxy or collection needs to be initialized before closing the <literal>Session</literal>. You can force initialization by calling <literal>cat.getSex()</literal> or <literal>cat.getKittens().size()</literal>, for example. However, this can be confusing to readers of the code and it is not convenient for generic code."
msgstr ""
#. Tag: para
-#: performance.xml:411
#, no-c-format
msgid "The static methods <literal>Hibernate.initialize()</literal> and <literal>Hibernate.isInitialized()</literal>, provide the application with a convenient way of working with lazily initialized collections or proxies. <literal>Hibernate.initialize(cat)</literal> will force the initialization of a proxy, <literal>cat</literal>, as long as its <literal>Session</literal> is still open. <literal>Hibernate.initialize( cat.getKittens() )</literal> has a similar effect for the collection of kittens."
msgstr ""
#. Tag: para
-#: performance.xml:420
#, no-c-format
msgid "Another option is to keep the <literal>Session</literal> open until all required collections and proxies have been loaded. In some application architectures, particularly where the code that accesses data using Hibernate, and the code that uses it are in different application layers or different physical processes, it can be a problem to ensure that the <literal>Session</literal> is open when a collection is initialized. There are two basic ways to deal with this issue:"
msgstr ""
#. Tag: para
-#: performance.xml:431
#, no-c-format
msgid "In a web-based application, a servlet filter can be used to close the <literal>Session</literal> only at the end of a user request, once the rendering of the view is complete (the <emphasis>Open Session in View</emphasis> pattern). Of course, this places heavy demands on the correctness of the exception handling of your application infrastructure. It is vitally important that the <literal>Session</literal> is closed and the transaction ended before returning to the user, even when an exception occurs during rendering of the view. See the Hibernate Wiki for examples of this \"Open Session in View\" pattern."
msgstr ""
#. Tag: para
-#: performance.xml:444
#, no-c-format
msgid "In an application with a separate business tier, the business logic must \"prepare\" all collections that the web tier needs before returning. This means that the business tier should load all the data and return all the data already initialized to the presentation/web tier that is required for a particular use case. Usually, the application calls <literal>Hibernate.initialize()</literal> for each collection that will be needed in the web tier (this call must occur before the session is closed) or retrieves the collection eagerly using a Hibernate query with a <literal>FETCH</literal> clause or a <literal>FetchMode.JOIN</literal> in <literal>Criteria</literal>. This is usually easier if you adopt the <emphasis>Command</emphasis> pattern instead of a <emphasis>Session Facade</emphasis>."
msgstr ""
#. Tag: para
-#: performance.xml:459
#, no-c-format
msgid "You can also attach a previously loaded object to a new <literal>Session</literal> with <literal>merge()</literal> or <literal>lock()</literal> before accessing uninitialized collections or other proxies. Hibernate does not, and certainly <emphasis>should</emphasis> not, do this automatically since it would introduce impromptu transaction semantics."
msgstr ""
#. Tag: para
-#: performance.xml:469
#, no-c-format
msgid "Sometimes you do not want to initialize a large collection, but still need some information about it, like its size, for example, or a subset of the data."
msgstr ""
#. Tag: para
-#: performance.xml:474
#, no-c-format
msgid "You can use a collection filter to get the size of a collection without initializing it:"
msgstr ""
-#. Tag: programlisting
-#: performance.xml:478
-#, no-c-format
-msgid "<![CDATA[( (Integer) s.createFilter( collection, \"select count(*)\" ).list().get(0) ).intValue()]]>"
-msgstr ""
-
#. Tag: para
-#: performance.xml:480
#, no-c-format
msgid "The <literal>createFilter()</literal> method is also used to efficiently retrieve subsets of a collection without needing to initialize the whole collection:"
msgstr ""
-#. Tag: programlisting
-#: performance.xml:485
-#, no-c-format
-msgid "<![CDATA[s.createFilter( lazyCollection, \"\").setFirstResult(0).setMaxResults(10).list();]]>"
-msgstr ""
-
#. Tag: title
-#: performance.xml:490
#, no-c-format
msgid "Using batch fetching"
msgstr ""
#. Tag: para
-#: performance.xml:492
#, no-c-format
msgid "Using batch fetching, Hibernate can load several uninitialized proxies if one proxy is accessed. Batch fetching is an optimization of the lazy select fetching strategy. There are two ways you can configure batch fetching: on the class level and the collection level."
msgstr ""
#. Tag: para
-#: performance.xml:498
#, no-c-format
msgid "Batch fetching for classes/entities is easier to understand. Consider the following example: at runtime you have 25 <literal>Cat</literal> instances loaded in a <literal>Session</literal>, and each <literal>Cat</literal> has a reference to its <literal>owner</literal>, a <literal>Person</literal>. The <literal>Person</literal> class is mapped with a proxy, <literal>lazy=\"true\"</literal>. If you now iterate through all cats and call <literal>getOwner()</literal> on each, Hibernate will, by default, execute 25 <literal>SELECT</literal> statements to retrieve the proxied owners. You can tune this behavior by specifying a <literal>batch-size</literal> in the mapping of <literal>Person</literal>:"
msgstr ""
-#. Tag: programlisting
-#: performance.xml:508
-#, no-c-format
-msgid "<![CDATA[<class name=\"Person\" batch-size=\"10\">...</class>]]>"
-msgstr ""
-
#. Tag: para
-#: performance.xml:510
#, no-c-format
msgid "Hibernate will now execute only three queries: the pattern is 10, 10, 5."
msgstr ""
#. Tag: para
-#: performance.xml:514
#, no-c-format
msgid "You can also enable batch fetching of collections. For example, if each <literal>Person</literal> has a lazy collection of <literal>Cat</literal>s, and 10 persons are currently loaded in the <literal>Session</literal>, iterating through all persons will generate 10 <literal>SELECT</literal>s, one for every call to <literal>getCats()</literal>. If you enable batch fetching for the <literal>cats</literal> collection in the mapping of <literal>Person</literal>, Hibernate can pre-fetch collections:"
msgstr ""
-#. Tag: programlisting
-#: performance.xml:523
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Person\">\n"
- " <set name=\"cats\" batch-size=\"3\">\n"
- " ...\n"
- " </set>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: performance.xml:525
#, no-c-format
msgid "With a <literal>batch-size</literal> of 3, Hibernate will load 3, 3, 3, 1 collections in four <literal>SELECT</literal>s. Again, the value of the attribute depends on the expected number of uninitialized collections in a particular <literal>Session</literal>."
msgstr ""
#. Tag: para
-#: performance.xml:531
#, no-c-format
msgid "Batch fetching of collections is particularly useful if you have a nested tree of items, i.e. the typical bill-of-materials pattern. However, a <emphasis>nested set</emphasis> or a <emphasis>materialized path</emphasis> might be a better option for read-mostly trees."
msgstr ""
#. Tag: title
-#: performance.xml:540
#, no-c-format
msgid "Using subselect fetching"
msgstr ""
#. Tag: para
-#: performance.xml:542
#, no-c-format
msgid "If one lazy collection or single-valued proxy has to be fetched, Hibernate will load all of them, re-running the original query in a subselect. This works in the same way as batch-fetching but without the piecemeal loading."
msgstr ""
#. Tag: title
-#: performance.xml:553
#, no-c-format
msgid "Using lazy property fetching"
msgstr ""
#. Tag: para
-#: performance.xml:555
#, no-c-format
msgid "Hibernate3 supports the lazy fetching of individual properties. This optimization technique is also known as <emphasis>fetch groups</emphasis>. Please note that this is mostly a marketing feature; optimizing row reads is much more important than optimization of column reads. However, only loading some properties of a class could be useful in extreme cases. For example, when legacy tables have hundreds of columns and the data model cannot be improved."
msgstr ""
#. Tag: para
-#: performance.xml:564
#, no-c-format
msgid "To enable lazy property loading, set the <literal>lazy</literal> attribute on your particular property mappings:"
msgstr ""
-#. Tag: programlisting
-#: performance.xml:569
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Document\">\n"
- " <id name=\"id\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <property name=\"name\" not-null=\"true\" length=\"50\"/>\n"
- " <property name=\"summary\" not-null=\"true\" length=\"200\" lazy=\"true\"/>\n"
- " <property name=\"text\" not-null=\"true\" length=\"2000\" lazy=\"true\"/>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: performance.xml:571
#, no-c-format
msgid "Lazy property loading requires buildtime bytecode instrumentation. If your persistent classes are not enhanced, Hibernate will ignore lazy property settings and return to immediate fetching."
msgstr ""
#. Tag: para
-#: performance.xml:577
#, no-c-format
msgid "For bytecode instrumentation, use the following Ant task:"
msgstr ""
-#. Tag: programlisting
-#: performance.xml:581
-#, no-c-format
-msgid ""
- "<![CDATA[<target name=\"instrument\" depends=\"compile\">\n"
- " <taskdef name=\"instrument\" classname=\"org.hibernate.tool.instrument.InstrumentTask\">\n"
- " <classpath path=\"${jar.path}\"/>\n"
- " <classpath path=\"${classes.dir}\"/>\n"
- " <classpath refid=\"lib.class.path\"/>\n"
- " </taskdef>\n"
- "\n"
- " <instrument verbose=\"true\">\n"
- " <fileset dir=\"${testclasses.dir}/org/hibernate/auction/model\">\n"
- " <include name=\"*.class\"/>\n"
- " </fileset>\n"
- " </instrument>\n"
- "</target>]]>"
-msgstr ""
-
#. Tag: para
-#: performance.xml:583
#, no-c-format
msgid "A different way of avoiding unnecessary column reads, at least for read-only transactions, is to use the projection features of HQL or Criteria queries. This avoids the need for buildtime bytecode processing and is certainly a preferred solution."
msgstr ""
#. Tag: para
-#: performance.xml:590
#, no-c-format
msgid "You can force the usual eager fetching of properties using <literal>fetch all properties</literal> in HQL."
msgstr ""
#. Tag: title
-#: performance.xml:600
#, no-c-format
msgid "The Second Level Cache"
msgstr ""
#. Tag: para
-#: performance.xml:602
#, no-c-format
msgid "A Hibernate <literal>Session</literal> is a transaction-level cache of persistent data. It is possible to configure a cluster or JVM-level (<literal>SessionFactory</literal>-level) cache on a class-by-class and collection-by-collection basis. You can even plug in a clustered cache. Be aware that caches are not aware of changes made to the persistent store by another application. They can, however, be configured to regularly expire cached data."
msgstr ""
#. Tag: para
-#: performance.xml:610
#, no-c-format
msgid "You have the option to tell Hibernate which caching implementation to use by specifying the name of a class that implements <literal>org.hibernate.cache.CacheProvider</literal> using the property <literal>hibernate.cache.provider_class</literal>. Hibernate is bundled with a number of built-in integrations with the open-source cache providers that are listed below. You can also implement your own and plug it in as outlined above. Note that versions prior to 3.2 use EhCache as the default cache provider."
msgstr ""
#. Tag: title
-#: performance.xml:621
#, no-c-format
msgid "Cache Providers"
msgstr ""
#. Tag: entry
-#: performance.xml:630 performance.xml:818
#, no-c-format
msgid "Cache"
msgstr ""
#. Tag: entry
-#: performance.xml:631
#, no-c-format
msgid "Provider class"
msgstr ""
#. Tag: entry
-#: performance.xml:632
#, no-c-format
msgid "Type"
msgstr ""
#. Tag: entry
-#: performance.xml:633
#, no-c-format
msgid "Cluster Safe"
msgstr ""
#. Tag: entry
-#: performance.xml:634
#, no-c-format
msgid "Query Cache Supported"
msgstr ""
#. Tag: entry
-#: performance.xml:639 performance.xml:827
#, no-c-format
msgid "Hashtable (not intended for production use)"
msgstr ""
-#. Tag: literal
-#: performance.xml:640
+#. Tag: entry
#, no-c-format
-msgid "org.hibernate.cache.HashtableCacheProvider"
+msgid "<literal>org.hibernate.cache.HashtableCacheProvider</literal>"
msgstr ""
#. Tag: entry
-#: performance.xml:641
#, no-c-format
msgid "memory"
msgstr ""
#. Tag: entry
-#: performance.xml:643 performance.xml:650 performance.xml:657 performance.xml:828 performance.xml:829 performance.xml:830 performance.xml:835 performance.xml:836 performance.xml:837 performance.xml:842 performance.xml:843 performance.xml:844 performance.xml:849 performance.xml:850 performance.xml:856 performance.xml:859 performance.xml:863 performance.xml:866
#, no-c-format
-msgid "<entry>yes</entry>"
+msgid "yes"
msgstr ""
#. Tag: entry
-#: performance.xml:646 performance.xml:834
#, no-c-format
msgid "EHCache"
msgstr ""
-#. Tag: literal
-#: performance.xml:647
+#. Tag: entry
#, no-c-format
-msgid "org.hibernate.cache.EhCacheProvider"
+msgid "<literal>org.hibernate.cache.EhCacheProvider</literal>"
msgstr ""
#. Tag: entry
-#: performance.xml:648 performance.xml:655
#, no-c-format
msgid "memory, disk"
msgstr ""
#. Tag: entry
-#: performance.xml:653 performance.xml:841
#, no-c-format
msgid "OSCache"
msgstr ""
-#. Tag: literal
-#: performance.xml:654
+#. Tag: entry
#, no-c-format
-msgid "org.hibernate.cache.OSCacheProvider"
+msgid "<literal>org.hibernate.cache.OSCacheProvider</literal>"
msgstr ""
#. Tag: entry
-#: performance.xml:660 performance.xml:848
#, no-c-format
msgid "SwarmCache"
msgstr ""
-#. Tag: literal
-#: performance.xml:661
+#. Tag: entry
#, no-c-format
-msgid "org.hibernate.cache.SwarmCacheProvider"
+msgid "<literal>org.hibernate.cache.SwarmCacheProvider</literal>"
msgstr ""
#. Tag: entry
-#: performance.xml:662
#, no-c-format
msgid "clustered (ip multicast)"
msgstr ""
#. Tag: entry
-#: performance.xml:663
#, no-c-format
msgid "yes (clustered invalidation)"
msgstr ""
#. Tag: entry
-#: performance.xml:667 performance.xml:855
#, no-c-format
msgid "JBoss Cache 1.x"
msgstr ""
-#. Tag: literal
-#: performance.xml:668
+#. Tag: entry
#, no-c-format
-msgid "org.hibernate.cache.TreeCacheProvider"
+msgid "<literal>org.hibernate.cache.TreeCacheProvider</literal>"
msgstr ""
#. Tag: entry
-#: performance.xml:669 performance.xml:676
#, no-c-format
msgid "clustered (ip multicast), transactional"
msgstr ""
#. Tag: entry
-#: performance.xml:670
#, no-c-format
msgid "yes (replication)"
msgstr ""
#. Tag: entry
-#: performance.xml:671 performance.xml:678
#, no-c-format
msgid "yes (clock sync req.)"
msgstr ""
#. Tag: entry
-#: performance.xml:674 performance.xml:862
#, no-c-format
msgid "JBoss Cache 2"
msgstr ""
-#. Tag: literal
-#: performance.xml:675
+#. Tag: entry
#, no-c-format
-msgid "org.hibernate.cache.jbc2.JBossCacheRegionFactory"
+msgid "<literal>org.hibernate.cache.jbc2.JBossCacheRegionFactory</literal>"
msgstr ""
#. Tag: entry
-#: performance.xml:677
#, no-c-format
msgid "yes (replication or invalidation)"
msgstr ""
#. Tag: title
-#: performance.xml:685
#, no-c-format
msgid "Cache mappings"
msgstr ""
#. Tag: para
-#: performance.xml:687
#, no-c-format
msgid "The <literal><cache></literal> element of a class or collection mapping has the following form:"
msgstr ""
-#. Tag: programlisting
-#: performance.xml:698
-#, no-c-format
-msgid ""
- "<![CDATA[<cache \n"
- " usage=\"transactional|read-write|nonstrict-read-write|read-only\"\n"
- " region=\"RegionName\"\n"
- " include=\"all|non-lazy\"\n"
- "/>]]>"
-msgstr ""
-
#. Tag: para
-#: performance.xml:701
#, no-c-format
msgid "<literal>usage</literal> (required) specifies the caching strategy: <literal>transactional</literal>, <literal>read-write</literal>, <literal>nonstrict-read-write</literal> or <literal>read-only</literal>"
msgstr ""
#. Tag: para
-#: performance.xml:710
#, no-c-format
msgid "<literal>region</literal> (optional: defaults to the class or collection role name): specifies the name of the second level cache region"
msgstr ""
#. Tag: para
-#: performance.xml:717
#, no-c-format
msgid "<literal>include</literal> (optional: defaults to <literal>all</literal>) <literal>non-lazy</literal>: specifies that properties of the entity mapped with <literal>lazy=\"true\"</literal> cannot be cached when attribute-level lazy fetching is enabled"
msgstr ""
#. Tag: para
-#: performance.xml:727
#, no-c-format
msgid "Alternatively, you can specify <literal><class-cache></literal> and <literal><collection-cache></literal> elements in <literal>hibernate.cfg.xml</literal>."
msgstr ""
#. Tag: para
-#: performance.xml:732
#, no-c-format
msgid "The <literal>usage</literal> attribute specifies a <emphasis>cache concurrency strategy</emphasis>."
msgstr ""
#. Tag: title
-#: performance.xml:739
#, no-c-format
msgid "Strategy: read only"
msgstr ""
#. Tag: para
-#: performance.xml:741
#, no-c-format
msgid "If your application needs to read, but not modify, instances of a persistent class, a <literal>read-only</literal> cache can be used. This is the simplest and optimal performing strategy. It is even safe for use in a cluster."
msgstr ""
-#. Tag: programlisting
-#: performance.xml:747
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"eg.Immutable\" mutable=\"false\">\n"
- " <cache usage=\"read-only\"/>\n"
- " ....\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: title
-#: performance.xml:753
#, no-c-format
msgid "Strategy: read/write"
msgstr ""
#. Tag: para
-#: performance.xml:755
#, no-c-format
msgid "If the application needs to update data, a <literal>read-write</literal> cache might be appropriate. This cache strategy should never be used if serializable transaction isolation level is required. If the cache is used in a JTA environment, you must specify the property <literal>hibernate.transaction.manager_lookup_class</literal> and naming a strategy for obtaining the JTA <literal>TransactionManager</literal>. In other environments, you should ensure that the transaction is completed when <literal>Session.close()</literal> or <literal>Session.disconnect()</literal> is called. If you want to use this strategy in a cluster, you should ensure that the underlying cache implementation supports locking. The built-in cache providers <emphasis>do not</emphasis> support locking."
msgstr ""
-#. Tag: programlisting
-#: performance.xml:766
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"eg.Cat\" .... >\n"
- " <cache usage=\"read-write\"/>\n"
- " ....\n"
- " <set name=\"kittens\" ... >\n"
- " <cache usage=\"read-write\"/>\n"
- " ....\n"
- " </set>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: title
-#: performance.xml:771
#, no-c-format
msgid "Strategy: nonstrict read/write"
msgstr ""
#. Tag: para
-#: performance.xml:773
#, no-c-format
msgid "If the application only occasionally needs to update data (i.e. if it is extremely unlikely that two transactions would try to update the same item simultaneously), and strict transaction isolation is not required, a <literal>nonstrict-read-write</literal> cache might be appropriate. If the cache is used in a JTA environment, you must specify <literal>hibernate.transaction.manager_lookup_class</literal>. In other environments, you should ensure that the transaction is completed when <literal>Session.close()</literal> or <literal>Session.disconnect()</literal> is called."
msgstr ""
#. Tag: title
-#: performance.xml:785
#, no-c-format
msgid "Strategy: transactional"
msgstr ""
#. Tag: para
-#: performance.xml:787
#, no-c-format
msgid "The <literal>transactional</literal> cache strategy provides support for fully transactional cache providers such as JBoss TreeCache. Such a cache can only be used in a JTA environment and you must specify <literal>hibernate.transaction.manager_lookup_class</literal>."
msgstr ""
#. Tag: title
-#: performance.xml:796
#, no-c-format
msgid "Cache-provider/concurrency-strategy compatibility"
msgstr ""
#. Tag: para
-#: performance.xml:799
#, no-c-format
msgid "None of the cache providers support all of the cache concurrency strategies."
msgstr ""
#. Tag: para
-#: performance.xml:804
#, no-c-format
msgid "The following table shows which providers are compatible with which concurrency strategies."
msgstr ""
#. Tag: title
-#: performance.xml:809
#, no-c-format
msgid "Cache Concurrency Strategy Support"
msgstr ""
#. Tag: entry
-#: performance.xml:819
#, no-c-format
msgid "read-only"
msgstr ""
#. Tag: entry
-#: performance.xml:820
#, no-c-format
msgid "nonstrict-read-write"
msgstr ""
#. Tag: entry
-#: performance.xml:821
#, no-c-format
msgid "read-write"
msgstr ""
#. Tag: entry
-#: performance.xml:822
#, no-c-format
msgid "transactional"
msgstr ""
#. Tag: title
-#: performance.xml:877
#, no-c-format
msgid "Managing the caches"
msgstr ""
#. Tag: para
-#: performance.xml:879
#, no-c-format
msgid "Whenever you pass an object to <literal>save()</literal>, <literal>update()</literal> or <literal>saveOrUpdate()</literal>, and whenever you retrieve an object using <literal>load()</literal>, <literal>get()</literal>, <literal>list()</literal>, <literal>iterate()</literal> or <literal>scroll()</literal>, that object is added to the internal cache of the <literal>Session</literal>."
msgstr ""
#. Tag: para
-#: performance.xml:886
#, no-c-format
msgid "When <literal>flush()</literal> is subsequently called, the state of that object will be synchronized with the database. If you do not want this synchronization to occur, or if you are processing a huge number of objects and need to manage memory efficiently, the <literal>evict()</literal> method can be used to remove the object and its collections from the first-level cache."
msgstr ""
-#. Tag: programlisting
-#: performance.xml:894
-#, no-c-format
-msgid ""
- "<![CDATA[ScrollableResult cats = sess.createQuery(\"from Cat as cat\").scroll(); //a huge result set\n"
- "while ( cats.next() ) {\n"
- " Cat cat = (Cat) cats.get(0);\n"
- " doSomethingWithACat(cat);\n"
- " sess.evict(cat);\n"
- "}]]>"
-msgstr ""
-
#. Tag: para
-#: performance.xml:896
#, no-c-format
msgid "The <literal>Session</literal> also provides a <literal>contains()</literal> method to determine if an instance belongs to the session cache."
msgstr ""
#. Tag: para
-#: performance.xml:901
#, no-c-format
msgid "To evict all objects from the session cache, call <literal>Session.clear()</literal>"
msgstr ""
#. Tag: para
-#: performance.xml:905
#, no-c-format
msgid "For the second-level cache, there are methods defined on <literal>SessionFactory</literal> for evicting the cached state of an instance, entire class, collection instance or entire collection role."
msgstr ""
-#. Tag: programlisting
-#: performance.xml:911
-#, no-c-format
-msgid ""
- "<![CDATA[sessionFactory.evict(Cat.class, catId); //evict a particular Cat\n"
- "sessionFactory.evict(Cat.class); //evict all Cats\n"
- "sessionFactory.evictCollection(\"Cat.kittens\", catId); //evict a particular collection of kittens\n"
- "sessionFactory.evictCollection(\"Cat.kittens\"); //evict all kitten collections]]>"
-msgstr ""
-
#. Tag: para
-#: performance.xml:913
#, no-c-format
msgid "The <literal>CacheMode</literal> controls how a particular session interacts with the second-level cache:"
msgstr ""
#. Tag: para
-#: performance.xml:920
#, no-c-format
msgid "<literal>CacheMode.NORMAL</literal>: will read items from and write items to the second-level cache"
msgstr ""
#. Tag: para
-#: performance.xml:925
#, no-c-format
msgid "<literal>CacheMode.GET</literal>: will read items from the second-level cache. Do not write to the second-level cache except when updating data"
msgstr ""
#. Tag: para
-#: performance.xml:931
#, no-c-format
msgid "<literal>CacheMode.PUT</literal>: will write items to the second-level cache. Do not read from the second-level cache"
msgstr ""
#. Tag: para
-#: performance.xml:937
#, no-c-format
msgid "<literal>CacheMode.REFRESH</literal>: will write items to the second-level cache. Do not read from the second-level cache. Bypass the effect of <literal>hibernate.cache.use_minimal_puts</literal> forcing a refresh of the second-level cache for all items read from the database"
msgstr ""
#. Tag: para
-#: performance.xml:945
#, no-c-format
msgid "To browse the contents of a second-level or query cache region, use the <literal>Statistics</literal> API:"
msgstr ""
-#. Tag: programlisting
-#: performance.xml:950
-#, no-c-format
-msgid ""
- "<![CDATA[Map cacheEntries = sessionFactory.getStatistics()\n"
- " .getSecondLevelCacheStatistics(regionName)\n"
- " .getEntries();]]>"
-msgstr ""
-
#. Tag: para
-#: performance.xml:952
#, no-c-format
msgid "You will need to enable statistics and, optionally, force Hibernate to keep the cache entries in a more readable format:"
msgstr ""
-#. Tag: programlisting
-#: performance.xml:957
-#, no-c-format
-msgid ""
- "<![CDATA[hibernate.generate_statistics true\n"
- "hibernate.cache.use_structured_entries true]]>"
-msgstr ""
-
#. Tag: title
-#: performance.xml:962
#, no-c-format
msgid "The Query Cache"
msgstr ""
#. Tag: para
-#: performance.xml:964
#, no-c-format
msgid "Query result sets can also be cached. This is only useful for queries that are run frequently with the same parameters. You will first need to enable the query cache:"
msgstr ""
-#. Tag: programlisting
-#: performance.xml:969
-#, no-c-format
-msgid "<![CDATA[hibernate.cache.use_query_cache true]]>"
-msgstr ""
-
#. Tag: para
-#: performance.xml:971
#, no-c-format
msgid "This setting creates two new cache regions: one holding cached query result sets (<literal>org.hibernate.cache.StandardQueryCache</literal>), the other holding timestamps of the most recent updates to queryable tables (<literal>org.hibernate.cache.UpdateTimestampsCache</literal>). Note that the query cache does not cache the state of the actual entities in the result set; it caches only identifier values and results of value type. The query cache should always be used in conjunction with the second-level cache."
msgstr ""
#. Tag: para
-#: performance.xml:981
#, no-c-format
msgid "Most queries do not benefit from caching, so by default, queries are not cached. To enable caching, call <literal>Query.setCacheable(true)</literal>. This call allows the query to look for existing cache results or add its results to the cache when it is executed."
msgstr ""
#. Tag: para
-#: performance.xml:988
#, no-c-format
msgid "If you require fine-grained control over query cache expiration policies, you can specify a named cache region for a particular query by calling <literal>Query.setCacheRegion()</literal>."
msgstr ""
-#. Tag: programlisting
-#: performance.xml:994
-#, no-c-format
-msgid ""
- "<![CDATA[List blogs = sess.createQuery(\"from Blog blog where blog.blogger = :blogger\")\n"
- " .setEntity(\"blogger\", blogger)\n"
- " .setMaxResults(15)\n"
- " .setCacheable(true)\n"
- " .setCacheRegion(\"frontpages\")\n"
- " .list();]]>"
-msgstr ""
-
#. Tag: para
-#: performance.xml:996
#, no-c-format
msgid "If the query should force a refresh of its query cache region, you should call <literal>Query.setCacheMode(CacheMode.REFRESH)</literal>. This is particularly useful in cases where underlying data may have been updated via a separate process (i.e., not modified through Hibernate) and allows the application to selectively refresh particular query result sets. This is a more efficient alternative to eviction of a query cache region via <literal>SessionFactory.evictQueries()</literal>."
msgstr ""
#. Tag: title
-#: performance.xml:1008
#, no-c-format
msgid "Understanding Collection performance"
msgstr ""
#. Tag: para
-#: performance.xml:1010
#, no-c-format
msgid "In the previous sections we have covered collections and their applications. In this section we explore some more issues in relation to collections at runtime."
msgstr ""
#. Tag: title
-#: performance.xml:1017
#, no-c-format
msgid "Taxonomy"
msgstr ""
#. Tag: para
-#: performance.xml:1019
#, no-c-format
msgid "Hibernate defines three basic kinds of collections:"
msgstr ""
#. Tag: para
-#: performance.xml:1023
#, no-c-format
msgid "collections of values"
msgstr ""
#. Tag: para
-#: performance.xml:1026
#, no-c-format
msgid "one-to-many associations"
msgstr ""
#. Tag: para
-#: performance.xml:1029
#, no-c-format
msgid "many-to-many associations"
msgstr ""
#. Tag: para
-#: performance.xml:1033
#, no-c-format
msgid "This classification distinguishes the various table and foreign key relationships but does not tell us quite everything we need to know about the relational model. To fully understand the relational structure and performance characteristics, we must also consider the structure of the primary key that is used by Hibernate to update or delete collection rows. This suggests the following classification:"
msgstr ""
#. Tag: para
-#: performance.xml:1044
#, no-c-format
msgid "indexed collections"
msgstr ""
#. Tag: para
-#: performance.xml:1047
#, no-c-format
msgid "sets"
msgstr ""
#. Tag: para
-#: performance.xml:1050
#, no-c-format
msgid "bags"
msgstr ""
#. Tag: para
-#: performance.xml:1054
#, no-c-format
msgid "All indexed collections (maps, lists, and arrays) have a primary key consisting of the <literal><key></literal> and <literal><index></literal> columns. In this case, collection updates are extremely efficient. The primary key can be efficiently indexed and a particular row can be efficiently located when Hibernate tries to update or delete it."
msgstr ""
#. Tag: para
-#: performance.xml:1062
#, no-c-format
msgid "Sets have a primary key consisting of <literal><key></literal> and element columns. This can be less efficient for some types of collection element, particularly composite elements or large text or binary fields, as the database may not be able to index a complex primary key as efficiently. However, for one-to-many or many-to-many associations, particularly in the case of synthetic identifiers, it is likely to be just as efficient. If you want <literal>SchemaExport</literal> to actually create the primary key of a <literal><set></literal>, you must declare all columns as <literal>not-null=\"true\"</literal>."
msgstr ""
#. Tag: para
-#: performance.xml:1073
#, no-c-format
msgid "<literal><idbag></literal> mappings define a surrogate key, so they are efficient to update. In fact, they are the best case."
msgstr ""
#. Tag: para
-#: performance.xml:1078
#, no-c-format
msgid "Bags are the worst case since they permit duplicate element values and, as they have no index column, no primary key can be defined. Hibernate has no way of distinguishing between duplicate rows. Hibernate resolves this problem by completely removing in a single <literal>DELETE</literal> and recreating the collection whenever it changes. This can be inefficient."
msgstr ""
#. Tag: para
-#: performance.xml:1086
#, no-c-format
msgid "For a one-to-many association, the \"primary key\" may not be the physical primary key of the database table. Even in this case, the above classification is still useful. It reflects how Hibernate \"locates\" individual rows of the collection."
msgstr ""
#. Tag: title
-#: performance.xml:1096
#, no-c-format
msgid "Lists, maps, idbags and sets are the most efficient collections to update"
msgstr ""
#. Tag: para
-#: performance.xml:1098
#, no-c-format
msgid "From the discussion above, it should be clear that indexed collections and sets allow the most efficient operation in terms of adding, removing and updating elements."
msgstr ""
#. Tag: para
-#: performance.xml:1104
#, no-c-format
msgid "There is, arguably, one more advantage that indexed collections have over sets for many-to-many associations or collections of values. Because of the structure of a <literal>Set</literal>, Hibernate does not <literal>UPDATE</literal> a row when an element is \"changed\". Changes to a <literal>Set</literal> always work via <literal>INSERT</literal> and <literal>DELETE</literal> of individual rows. Once again, this consideration does not apply to one-to-many associations."
msgstr ""
#. Tag: para
-#: performance.xml:1113
#, no-c-format
msgid "After observing that arrays cannot be lazy, you can conclude that lists, maps and idbags are the most performant (non-inverse) collection types, with sets not far behind. You can expect sets to be the most common kind of collection in Hibernate applications. This is because the \"set\" semantics are most natural in the relational model."
msgstr ""
#. Tag: para
-#: performance.xml:1121
#, no-c-format
msgid "However, in well-designed Hibernate domain models, most collections are in fact one-to-many associations with <literal>inverse=\"true\"</literal>. For these associations, the update is handled by the many-to-one end of the association, and so considerations of collection update performance simply do not apply."
msgstr ""
#. Tag: title
-#: performance.xml:1131
#, no-c-format
msgid "Bags and lists are the most efficient inverse collections"
msgstr ""
#. Tag: para
-#: performance.xml:1133
#, no-c-format
msgid "There is a particular case, however, in which bags, and also lists, are much more performant than sets. For a collection with <literal>inverse=\"true\"</literal>, the standard bidirectional one-to-many relationship idiom, for example, we can add elements to a bag or list without needing to initialize (fetch) the bag elements. This is because, unlike a <literal>set</literal>, <literal>Collection.add()</literal> or <literal>Collection.addAll()</literal> must always return true for a bag or <literal>List</literal>. This can make the following common code much faster:"
msgstr ""
-#. Tag: programlisting
-#: performance.xml:1143
-#, no-c-format
-msgid ""
- "<![CDATA[Parent p = (Parent) sess.load(Parent.class, id);\n"
- "Child c = new Child();\n"
- "c.setParent(p);\n"
- "p.getChildren().add(c); //no need to fetch the collection!\n"
- "sess.flush();]]>"
-msgstr ""
-
#. Tag: title
-#: performance.xml:1148
#, no-c-format
msgid "One shot delete"
msgstr ""
#. Tag: para
-#: performance.xml:1150
#, no-c-format
msgid "Deleting collection elements one by one can sometimes be extremely inefficient. Hibernate knows not to do that in the case of an newly-empty collection (if you called <literal>list.clear()</literal>, for example). In this case, Hibernate will issue a single <literal>DELETE</literal>."
msgstr ""
#. Tag: para
-#: performance.xml:1157
#, no-c-format
msgid "Suppose you added a single element to a collection of size twenty and then remove two elements. Hibernate will issue one <literal>INSERT</literal> statement and two <literal>DELETE</literal> statements, unless the collection is a bag. This is certainly desirable."
msgstr ""
#. Tag: para
-#: performance.xml:1163
#, no-c-format
msgid "However, suppose that we remove eighteen elements, leaving two and then add thee new elements. There are two possible ways to proceed"
msgstr ""
#. Tag: para
-#: performance.xml:1170
#, no-c-format
msgid "delete eighteen rows one by one and then insert three rows"
msgstr ""
#. Tag: para
-#: performance.xml:1173
#, no-c-format
msgid "remove the whole collection in one SQL <literal>DELETE</literal> and insert all five current elements one by one"
msgstr ""
#. Tag: para
-#: performance.xml:1178
#, no-c-format
msgid "Hibernate cannot know that the second option is probably quicker. It would probably be undesirable for Hibernate to be that intuitive as such behavior might confuse database triggers, etc."
msgstr ""
#. Tag: para
-#: performance.xml:1184
#, no-c-format
msgid "Fortunately, you can force this behavior (i.e. the second strategy) at any time by discarding (i.e. dereferencing) the original collection and returning a newly instantiated collection with all the current elements."
msgstr ""
#. Tag: para
-#: performance.xml:1190
#, no-c-format
msgid "One-shot-delete does not apply to collections mapped <literal>inverse=\"true\"</literal>."
msgstr ""
#. Tag: title
-#: performance.xml:1199
#, no-c-format
msgid "Monitoring performance"
msgstr ""
#. Tag: para
-#: performance.xml:1201
#, no-c-format
msgid "Optimization is not much use without monitoring and access to performance numbers. Hibernate provides a full range of figures about its internal operations. Statistics in Hibernate are available per <literal>SessionFactory</literal>."
msgstr ""
#. Tag: title
-#: performance.xml:1208
#, no-c-format
msgid "Monitoring a SessionFactory"
msgstr ""
#. Tag: para
-#: performance.xml:1210
#, no-c-format
msgid "You can access <literal>SessionFactory</literal> metrics in two ways. Your first option is to call <literal>sessionFactory.getStatistics()</literal> and read or display the <literal>Statistics</literal> yourself."
msgstr ""
#. Tag: para
-#: performance.xml:1216
#, no-c-format
msgid "Hibernate can also use JMX to publish metrics if you enable the <literal>StatisticsService</literal> MBean. You can enable a single MBean for all your <literal>SessionFactory</literal> or one per factory. See the following code for minimalistic configuration examples:"
msgstr ""
-#. Tag: programlisting
-#: performance.xml:1223
-#, no-c-format
-msgid ""
- "<![CDATA[// MBean service registration for a specific SessionFactory\n"
- "Hashtable tb = new Hashtable();\n"
- "tb.put(\"type\", \"statistics\");\n"
- "tb.put(\"sessionFactory\", \"myFinancialApp\");\n"
- "ObjectName on = new ObjectName(\"hibernate\", tb); // MBean object name\n"
- "\n"
- "StatisticsService stats = new StatisticsService(); // MBean implementation\n"
- "stats.setSessionFactory(sessionFactory); // Bind the stats to a SessionFactory\n"
- "server.registerMBean(stats, on); // Register the Mbean on the server]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: performance.xml:1226
-#, no-c-format
-msgid ""
- "<![CDATA[// MBean service registration for all SessionFactory's\n"
- "Hashtable tb = new Hashtable();\n"
- "tb.put(\"type\", \"statistics\");\n"
- "tb.put(\"sessionFactory\", \"all\");\n"
- "ObjectName on = new ObjectName(\"hibernate\", tb); // MBean object name\n"
- "\n"
- "StatisticsService stats = new StatisticsService(); // MBean implementation\n"
- "server.registerMBean(stats, on); // Register the MBean on the server]]>"
-msgstr ""
-
#. Tag: para
-#: performance.xml:1233
#, no-c-format
msgid "You can activate and deactivate the monitoring for a <literal>SessionFactory</literal>:"
msgstr ""
#. Tag: para
-#: performance.xml:1238
#, no-c-format
msgid "at configuration time, set <literal>hibernate.generate_statistics</literal> to <literal>false</literal>"
msgstr ""
#. Tag: para
-#: performance.xml:1245
#, no-c-format
msgid "at runtime: <literal>sf.getStatistics().setStatisticsEnabled(true)</literal> or <literal>hibernateStatsBean.setStatisticsEnabled(true)</literal>"
msgstr ""
#. Tag: para
-#: performance.xml:1252
#, no-c-format
msgid "Statistics can be reset programmatically using the <literal>clear()</literal> method. A summary can be sent to a logger (info level) using the <literal>logSummary()</literal> method."
msgstr ""
#. Tag: title
-#: performance.xml:1261
#, no-c-format
msgid "Metrics"
msgstr ""
#. Tag: para
-#: performance.xml:1263
#, no-c-format
msgid "Hibernate provides a number of metrics, from basic information to more specialized information that is only relevant in certain scenarios. All available counters are described in the <literal>Statistics</literal> interface API, in three categories:"
msgstr ""
#. Tag: para
-#: performance.xml:1270
#, no-c-format
msgid "Metrics related to the general <literal>Session</literal> usage, such as number of open sessions, retrieved JDBC connections, etc."
msgstr ""
#. Tag: para
-#: performance.xml:1276
#, no-c-format
msgid "Metrics related to the entities, collections, queries, and caches as a whole (aka global metrics)."
msgstr ""
#. Tag: para
-#: performance.xml:1282
#, no-c-format
msgid "Detailed metrics related to a particular entity, collection, query or cache region."
msgstr ""
#. Tag: para
-#: performance.xml:1289
#, no-c-format
msgid "For example, you can check the cache hit, miss, and put ratio of entities, collections and queries, and the average time a query needs. Be aware that the number of milliseconds is subject to approximation in Java. Hibernate is tied to the JVM precision and on some platforms this might only be accurate to 10 seconds."
msgstr ""
#. Tag: para
-#: performance.xml:1296
#, no-c-format
msgid "Simple getters are used to access the global metrics (i.e. not tied to a particular entity, collection, cache region, etc.). You can access the metrics of a particular entity, collection or cache region through its name, and through its HQL or SQL representation for queries. Please refer to the <literal>Statistics</literal>, <literal>EntityStatistics</literal>, <literal>CollectionStatistics</literal>, <literal>SecondLevelCacheStatistics</literal>, and <literal>QueryStatistics</literal> API Javadoc for more information. The following code is a simple example:"
msgstr ""
-#. Tag: programlisting
-#: performance.xml:1306
-#, no-c-format
-msgid ""
- "<![CDATA[Statistics stats = HibernateUtil.sessionFactory.getStatistics();\n"
- "\n"
- "double queryCacheHitCount = stats.getQueryCacheHitCount();\n"
- "double queryCacheMissCount = stats.getQueryCacheMissCount();\n"
- "double queryCacheHitRatio =\n"
- " queryCacheHitCount / (queryCacheHitCount + queryCacheMissCount);\n"
- "\n"
- "log.info(\"Query Hit ratio:\" + queryCacheHitRatio);\n"
- "\n"
- "EntityStatistics entityStats =\n"
- " stats.getEntityStatistics( Cat.class.getName() );\n"
- "long changes =\n"
- " entityStats.getInsertCount()\n"
- " + entityStats.getUpdateCount()\n"
- " + entityStats.getDeleteCount();\n"
- "log.info(Cat.class.getName() + \" changed \" + changes + \"times\" );]]>"
-msgstr ""
-
#. Tag: para
-#: performance.xml:1308
#, no-c-format
msgid "You can work on all entities, collections, queries and region caches, by retrieving the list of names of entities, collections, queries and region caches using the following methods: <literal>getQueries()</literal>, <literal>getEntityNames()</literal>, <literal>getCollectionRoleNames()</literal>, and <literal>getSecondLevelCacheRegionNames()</literal>."
msgstr ""
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/persistent_classes.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/persistent_classes.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/persistent_classes.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,709 +1,283 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-10 21:02+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:19\n"
+"PO-Revision-Date: 2010-01-08T04:07:19\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
-#: persistent_classes.xml:29
#, no-c-format
msgid "Persistent Classes"
msgstr ""
#. Tag: para
-#: persistent_classes.xml:31
#, no-c-format
msgid "Persistent classes are classes in an application that implement the entities of the business problem (e.g. Customer and Order in an E-commerce application). Not all instances of a persistent class are considered to be in the persistent state. For example, an instance can instead be transient or detached."
msgstr ""
#. Tag: para
-#: persistent_classes.xml:38
#, no-c-format
msgid "Hibernate works best if these classes follow some simple rules, also known as the Plain Old Java Object (POJO) programming model. However, none of these rules are hard requirements. Indeed, Hibernate3 assumes very little about the nature of your persistent objects. You can express a domain model in other ways (using trees of <literal>Map</literal> instances, for example)."
msgstr ""
#. Tag: title
-#: persistent_classes.xml:47
#, no-c-format
msgid "A simple POJO example"
msgstr ""
#. Tag: para
-#: persistent_classes.xml:49
#, no-c-format
msgid "Most Java applications require a persistent class representing felines. For example:"
msgstr ""
-#. Tag: programlisting
-#: persistent_classes.xml:53
-#, no-c-format
-msgid ""
- "<![CDATA[package eg;\n"
- "import java.util.Set;\n"
- "import java.util.Date;\n"
- "\n"
- "public class Cat {\n"
- " private Long id; // identifier\n"
- "\n"
- " private Date birthdate;\n"
- " private Color color;\n"
- " private char sex;\n"
- " private float weight;\n"
- " private int litterId;\n"
- "\n"
- " private Cat mother;\n"
- " private Set kittens = new HashSet();\n"
- "\n"
- " private void setId(Long id) {\n"
- " this.id=id;\n"
- " }\n"
- " public Long getId() {\n"
- " return id;\n"
- " }\n"
- "\n"
- " void setBirthdate(Date date) {\n"
- " birthdate = date;\n"
- " }\n"
- " public Date getBirthdate() {\n"
- " return birthdate;\n"
- " }\n"
- "\n"
- " void setWeight(float weight) {\n"
- " this.weight = weight;\n"
- " }\n"
- " public float getWeight() {\n"
- " return weight;\n"
- " }\n"
- "\n"
- " public Color getColor() {\n"
- " return color;\n"
- " }\n"
- " void setColor(Color color) {\n"
- " this.color = color;\n"
- " }\n"
- "\n"
- " void setSex(char sex) {\n"
- " this.sex=sex;\n"
- " }\n"
- " public char getSex() {\n"
- " return sex;\n"
- " }\n"
- "\n"
- " void setLitterId(int id) {\n"
- " this.litterId = id;\n"
- " }\n"
- " public int getLitterId() {\n"
- " return litterId;\n"
- " }\n"
- "\n"
- " void setMother(Cat mother) {\n"
- " this.mother = mother;\n"
- " }\n"
- " public Cat getMother() {\n"
- " return mother;\n"
- " }\n"
- " void setKittens(Set kittens) {\n"
- " this.kittens = kittens;\n"
- " }\n"
- " public Set getKittens() {\n"
- " return kittens;\n"
- " }\n"
- " \n"
- " // addKitten not needed by Hibernate\n"
- " public void addKitten(Cat kitten) {\n"
- " kitten.setMother(this);\n"
- " kitten.setLitterId( kittens.size() ); \n"
- " kittens.add(kitten);\n"
- " }\n"
- "}]]>"
-msgstr ""
-
#. Tag: para
-#: persistent_classes.xml:55
#, no-c-format
msgid "The four main rules of persistent classes are explored in more detail in the following sections."
msgstr ""
#. Tag: title
-#: persistent_classes.xml:61
#, no-c-format
msgid "Implement a no-argument constructor"
msgstr ""
#. Tag: para
-#: persistent_classes.xml:63
#, no-c-format
msgid "<literal>Cat</literal> has a no-argument constructor. All persistent classes must have a default constructor (which can be non-public) so that Hibernate can instantiate them using <literal>Constructor.newInstance()</literal>. It is recommended that you have a default constructor with at least <emphasis>package</emphasis> visibility for runtime proxy generation in Hibernate."
msgstr ""
#. Tag: title
-#: persistent_classes.xml:73
#, no-c-format
msgid "Provide an identifier property (optional)"
msgstr ""
#. Tag: para
-#: persistent_classes.xml:75
#, no-c-format
msgid "<literal>Cat</literal> has a property called <literal>id</literal>. This property maps to the primary key column of a database table. The property might have been called anything, and its type might have been any primitive type, any primitive \"wrapper\" type, <literal>java.lang.String</literal> or <literal>java.util.Date</literal>. If your legacy database table has composite keys, you can use a user-defined class with properties of these types (see the section on composite identifiers later in the chapter.)"
msgstr ""
#. Tag: para
-#: persistent_classes.xml:84
#, no-c-format
msgid "The identifier property is strictly optional. You can leave them off and let Hibernate keep track of object identifiers internally. We do not recommend this, however."
msgstr ""
#. Tag: para
-#: persistent_classes.xml:89
#, no-c-format
msgid "In fact, some functionality is available only to classes that declare an identifier property:"
msgstr ""
#. Tag: para
-#: persistent_classes.xml:96
#, no-c-format
-msgid "Transitive reattachment for detached objects (cascade update or cascade merge) - see"
+msgid "Transitive reattachment for detached objects (cascade update or cascade merge) - see <xref linkend=\"objectstate-transitive\" />"
msgstr ""
-#. Tag: literal
-#: persistent_classes.xml:103
+#. Tag: para
#, no-c-format
-msgid "Session.saveOrUpdate()"
+msgid "<literal>Session.saveOrUpdate()</literal>"
msgstr ""
-#. Tag: literal
-#: persistent_classes.xml:108
+#. Tag: para
#, no-c-format
-msgid "Session.merge()"
+msgid "<literal>Session.merge()</literal>"
msgstr ""
#. Tag: para
-#: persistent_classes.xml:113
#, no-c-format
msgid "We recommend that you declare consistently-named identifier properties on persistent classes and that you use a nullable (i.e., non-primitive) type."
msgstr ""
#. Tag: title
-#: persistent_classes.xml:120
#, no-c-format
msgid "Prefer non-final classes (optional)"
msgstr ""
#. Tag: para
-#: persistent_classes.xml:121
#, no-c-format
msgid "A central feature of Hibernate, <emphasis>proxies</emphasis>, depends upon the persistent class being either non-final, or the implementation of an interface that declares all public methods."
msgstr ""
#. Tag: para
-#: persistent_classes.xml:126
#, no-c-format
msgid "You can persist <literal>final</literal> classes that do not implement an interface with Hibernate. You will not, however, be able to use proxies for lazy association fetching which will ultimately limit your options for performance tuning."
msgstr ""
#. Tag: para
-#: persistent_classes.xml:131
#, no-c-format
msgid "You should also avoid declaring <literal>public final</literal> methods on the non-final classes. If you want to use a class with a <literal>public final</literal> method, you must explicitly disable proxying by setting <literal>lazy=\"false\"</literal>."
msgstr ""
#. Tag: title
-#: persistent_classes.xml:139
#, no-c-format
msgid "Declare accessors and mutators for persistent fields (optional)"
msgstr ""
#. Tag: para
-#: persistent_classes.xml:141
#, no-c-format
msgid "<literal>Cat</literal> declares accessor methods for all its persistent fields. Many other ORM tools directly persist instance variables. It is better to provide an indirection between the relational schema and internal data structures of the class. By default, Hibernate persists JavaBeans style properties and recognizes method names of the form <literal>getFoo</literal>, <literal>isFoo</literal> and <literal>setFoo</literal>. If required, you can switch to direct field access for particular properties."
msgstr ""
#. Tag: para
-#: persistent_classes.xml:151
#, no-c-format
msgid "Properties need <emphasis>not</emphasis> be declared public - Hibernate can persist a property with a default, <literal>protected</literal> or <literal>private</literal> get / set pair."
msgstr ""
#. Tag: title
-#: persistent_classes.xml:162
#, no-c-format
msgid "Implementing inheritance"
msgstr ""
#. Tag: para
-#: persistent_classes.xml:164
#, no-c-format
msgid "A subclass must also observe the first and second rules. It inherits its identifier property from the superclass, <literal>Cat</literal>. For example:"
msgstr ""
-#. Tag: programlisting
-#: persistent_classes.xml:169
-#, no-c-format
-msgid ""
- "<![CDATA[package eg;\n"
- "\n"
- "public class DomesticCat extends Cat {\n"
- " private String name;\n"
- "\n"
- " public String getName() {\n"
- " return name;\n"
- " }\n"
- " protected void setName(String name) {\n"
- " this.name=name;\n"
- " }\n"
- "}]]>"
-msgstr ""
-
#. Tag: title
-#: persistent_classes.xml:173
#, no-c-format
msgid "Implementing <literal>equals()</literal> and <literal>hashCode()</literal>"
msgstr ""
#. Tag: para
-#: persistent_classes.xml:175
#, no-c-format
msgid "You have to override the <literal>equals()</literal> and <literal>hashCode()</literal> methods if you:"
msgstr ""
#. Tag: para
-#: persistent_classes.xml:181
#, no-c-format
msgid "intend to put instances of persistent classes in a <literal>Set</literal> (the recommended way to represent many-valued associations); <emphasis>and</emphasis>"
msgstr ""
#. Tag: para
-#: persistent_classes.xml:188
#, no-c-format
msgid "intend to use reattachment of detached instances"
msgstr ""
#. Tag: para
-#: persistent_classes.xml:194
#, no-c-format
msgid "Hibernate guarantees equivalence of persistent identity (database row) and Java identity only inside a particular session scope. When you mix instances retrieved in different sessions, you must implement <literal>equals()</literal> and <literal>hashCode()</literal> if you wish to have meaningful semantics for <literal>Set</literal>s."
msgstr ""
#. Tag: para
-#: persistent_classes.xml:202
#, no-c-format
msgid "The most obvious way is to implement <literal>equals()</literal>/<literal>hashCode()</literal> by comparing the identifier value of both objects. If the value is the same, both must be the same database row, because they are equal. If both are added to a <literal>Set</literal>, you will only have one element in the <literal>Set</literal>). Unfortunately, you cannot use that approach with generated identifiers. Hibernate will only assign identifier values to objects that are persistent; a newly created instance will not have any identifier value. Furthermore, if an instance is unsaved and currently in a <literal>Set</literal>, saving it will assign an identifier value to the object. If <literal>equals()</literal> and <literal>hashCode()</literal> are based on the identifier value, the hash code would change, breaking the contract of the <literal>Set</literal>. See the Hibernate website for a full discussion of this problem. This is not a Hibernate issue, but normal Ja!
va semantics of object identity and equality."
msgstr ""
#. Tag: para
-#: persistent_classes.xml:216
#, no-c-format
msgid "It is recommended that you implement <literal>equals()</literal> and <literal>hashCode()</literal> using <emphasis>Business key equality</emphasis>. Business key equality means that the <literal>equals()</literal> method compares only the properties that form the business key. It is a key that would identify our instance in the real world (a <emphasis>natural</emphasis> candidate key):"
msgstr ""
-#. Tag: programlisting
-#: persistent_classes.xml:224
-#, no-c-format
-msgid ""
- "<![CDATA[public class Cat {\n"
- "\n"
- " ...\n"
- " public boolean equals(Object other) {\n"
- " if (this == other) return true;\n"
- " if ( !(other instanceof Cat) ) return false;\n"
- "\n"
- " final Cat cat = (Cat) other;\n"
- "\n"
- " if ( !cat.getLitterId().equals( getLitterId() ) ) return false;\n"
- " if ( !cat.getMother().equals( getMother() ) ) return false;\n"
- "\n"
- " return true;\n"
- " }\n"
- "\n"
- " public int hashCode() {\n"
- " int result;\n"
- " result = getMother().hashCode();\n"
- " result = 29 * result + getLitterId();\n"
- " return result;\n"
- " }\n"
- "\n"
- "}]]>"
-msgstr ""
-
#. Tag: para
-#: persistent_classes.xml:226
#, no-c-format
-msgid "A business key does not have to be as solid as a database primary key candidate (see <xref linkend=\"transactions-basics-identity\"/>). Immutable or unique properties are usually good candidates for a business key."
+msgid "A business key does not have to be as solid as a database primary key candidate (see <xref linkend=\"transactions-basics-identity\" />). Immutable or unique properties are usually good candidates for a business key."
msgstr ""
#. Tag: title
-#: persistent_classes.xml:236
#, no-c-format
msgid "Dynamic models"
msgstr ""
#. Tag: title
-#: persistent_classes.xml:239
#, no-c-format
msgid "Note"
msgstr ""
-#. Tag: emphasis
-#: persistent_classes.xml:241
+#. Tag: para
#, no-c-format
-msgid "The following features are currently considered experimental and may change in the near future."
+msgid "<emphasis>The following features are currently considered experimental and may change in the near future.</emphasis>"
msgstr ""
#. Tag: para
-#: persistent_classes.xml:246
#, no-c-format
msgid "Persistent entities do not necessarily have to be represented as POJO classes or as JavaBean objects at runtime. Hibernate also supports dynamic models (using <literal>Map</literal>s of <literal>Map</literal>s at runtime) and the representation of entities as DOM4J trees. With this approach, you do not write persistent classes, only mapping files."
msgstr ""
#. Tag: para
-#: persistent_classes.xml:254
#, no-c-format
-msgid "By default, Hibernate works in normal POJO mode. You can set a default entity representation mode for a particular <literal>SessionFactory</literal> using the <literal>default_entity_mode</literal> configuration option (see <xref linkend=\"configuration-optional-properties\"/>)."
+msgid "By default, Hibernate works in normal POJO mode. You can set a default entity representation mode for a particular <literal>SessionFactory</literal> using the <literal>default_entity_mode</literal> configuration option (see <xref linkend=\"configuration-optional-properties\" />)."
msgstr ""
#. Tag: para
-#: persistent_classes.xml:261
#, no-c-format
msgid "The following examples demonstrate the representation using <literal>Map</literal>s. First, in the mapping file an <literal>entity-name</literal> has to be declared instead of, or in addition to, a class name:"
msgstr ""
-#. Tag: programlisting
-#: persistent_classes.xml:267
-#, no-c-format
-msgid ""
- "<![CDATA[<hibernate-mapping>\n"
- "\n"
- " <class entity-name=\"Customer\">\n"
- "\n"
- " <id name=\"id\"\n"
- " type=\"long\"\n"
- " column=\"ID\">\n"
- " <generator class=\"sequence\"/>\n"
- " </id>\n"
- "\n"
- " <property name=\"name\"\n"
- " column=\"NAME\"\n"
- " type=\"string\"/>\n"
- "\n"
- " <property name=\"address\"\n"
- " column=\"ADDRESS\"\n"
- " type=\"string\"/>\n"
- "\n"
- " <many-to-one name=\"organization\"\n"
- " column=\"ORGANIZATION_ID\"\n"
- " class=\"Organization\"/>\n"
- "\n"
- " <bag name=\"orders\"\n"
- " inverse=\"true\"\n"
- " lazy=\"false\"\n"
- " cascade=\"all\">\n"
- " <key column=\"CUSTOMER_ID\"/>\n"
- " <one-to-many class=\"Order\"/>\n"
- " </bag>\n"
- "\n"
- " </class>\n"
- " \n"
- "</hibernate-mapping>]]>"
-msgstr ""
-
#. Tag: para
-#: persistent_classes.xml:269
#, no-c-format
msgid "Even though associations are declared using target class names, the target type of associations can also be a dynamic entity instead of a POJO."
msgstr ""
#. Tag: para
-#: persistent_classes.xml:276
#, no-c-format
msgid "After setting the default entity mode to <literal>dynamic-map</literal> for the <literal>SessionFactory</literal>, you can, at runtime, work with <literal>Map</literal>s of <literal>Map</literal>s:"
msgstr ""
-#. Tag: programlisting
-#: persistent_classes.xml:282
-#, no-c-format
-msgid ""
- "<![CDATA[Session s = openSession();\n"
- "Transaction tx = s.beginTransaction();\n"
- "Session s = openSession();\n"
- "\n"
- "// Create a customer\n"
- "Map david = new HashMap();\n"
- "david.put(\"name\", \"David\");\n"
- "\n"
- "// Create an organization\n"
- "Map foobar = new HashMap();\n"
- "foobar.put(\"name\", \"Foobar Inc.\");\n"
- "\n"
- "// Link both\n"
- "david.put(\"organization\", foobar);\n"
- "\n"
- "// Save both\n"
- "s.save(\"Customer\", david);\n"
- "s.save(\"Organization\", foobar);\n"
- "\n"
- "tx.commit();\n"
- "s.close();]]>"
-msgstr ""
-
#. Tag: para
-#: persistent_classes.xml:284
#, no-c-format
msgid "One of the main advantages of dynamic mapping is quick turnaround time for prototyping, without the need for entity class implementation. However, you lose compile-time type checking and will likely deal with many exceptions at runtime. As a result of the Hibernate mapping, the database schema can easily be normalized and sound, allowing to add a proper domain model implementation on top later on."
msgstr ""
#. Tag: para
-#: persistent_classes.xml:292
#, no-c-format
msgid "Entity representation modes can also be set on a per <literal>Session</literal> basis:"
msgstr ""
-#. Tag: programlisting
-#: persistent_classes.xml:297
-#, no-c-format
-msgid ""
- "<![CDATA[Session dynamicSession = pojoSession.getSession(EntityMode.MAP);\n"
- "\n"
- "// Create a customer\n"
- "Map david = new HashMap();\n"
- "david.put(\"name\", \"David\");\n"
- "dynamicSession.save(\"Customer\", david);\n"
- "...\n"
- "dynamicSession.flush();\n"
- "dynamicSession.close()\n"
- "...\n"
- "// Continue on pojoSession\n"
- "]]>"
-msgstr ""
-
#. Tag: para
-#: persistent_classes.xml:300
#, no-c-format
msgid "Please note that the call to <literal>getSession()</literal> using an <literal>EntityMode</literal> is on the <literal>Session</literal> API, not the <literal>SessionFactory</literal>. That way, the new <literal>Session</literal> shares the underlying JDBC connection, transaction, and other context information. This means you do not have to call <literal>flush()</literal> and <literal>close()</literal> on the secondary <literal>Session</literal>, and also leave the transaction and connection handling to the primary unit of work."
msgstr ""
#. Tag: para
-#: persistent_classes.xml:310
#, no-c-format
-msgid "More information about the XML representation capabilities can be found in <xref linkend=\"xml\"/>."
+msgid "More information about the XML representation capabilities can be found in <xref linkend=\"xml\" />."
msgstr ""
#. Tag: title
-#: persistent_classes.xml:318
#, no-c-format
msgid "Tuplizers"
msgstr ""
#. Tag: para
-#: persistent_classes.xml:320
#, no-c-format
msgid "<literal>org.hibernate.tuple.Tuplizer</literal>, and its sub-interfaces, are responsible for managing a particular representation of a piece of data given that representation's <literal>org.hibernate.EntityMode</literal>. If a given piece of data is thought of as a data structure, then a tuplizer is the thing that knows how to create such a data structure and how to extract values from and inject values into such a data structure. For example, for the POJO entity mode, the corresponding tuplizer knows how create the POJO through its constructor. It also knows how to access the POJO properties using the defined property accessors."
msgstr ""
#. Tag: para
-#: persistent_classes.xml:330
#, no-c-format
msgid "There are two high-level types of Tuplizers, represented by the <literal>org.hibernate.tuple.entity.EntityTuplizer</literal> and <literal>org.hibernate.tuple.component.ComponentTuplizer</literal> interfaces. <literal>EntityTuplizer</literal>s are responsible for managing the above mentioned contracts in regards to entities, while <literal>ComponentTuplizer</literal>s do the same for components."
msgstr ""
#. Tag: para
-#: persistent_classes.xml:338
#, no-c-format
msgid "Users can also plug in their own tuplizers. Perhaps you require that a <literal>java.util.Map</literal> implementation other than <literal>java.util.HashMap</literal> be used while in the dynamic-map entity-mode. Or perhaps you need to define a different proxy generation strategy than the one used by default. Both would be achieved by defining a custom tuplizer implementation. Tuplizer definitions are attached to the entity or component mapping they are meant to manage. Going back to the example of our customer entity:"
msgstr ""
-#. Tag: programlisting
-#: persistent_classes.xml:347
-#, no-c-format
-msgid ""
- "<![CDATA[<hibernate-mapping>\n"
- " <class entity-name=\"Customer\">\n"
- " <!--\n"
- " Override the dynamic-map entity-mode\n"
- " tuplizer for the customer entity\n"
- " -->\n"
- " <tuplizer entity-mode=\"dynamic-map\"\n"
- " class=\"CustomMapTuplizerImpl\"/>\n"
- "\n"
- " <id name=\"id\" type=\"long\" column=\"ID\">\n"
- " <generator class=\"sequence\"/>\n"
- " </id>\n"
- "\n"
- " <!-- other properties -->\n"
- " ...\n"
- " </class>\n"
- "</hibernate-mapping>\n"
- "\n"
- "\n"
- "public class CustomMapTuplizerImpl\n"
- " extends org.hibernate.tuple.entity.DynamicMapEntityTuplizer {\n"
- " // override the buildInstantiator() method to plug in our custom map...\n"
- " protected final Instantiator buildInstantiator(\n"
- " org.hibernate.mapping.PersistentClass mappingInfo) {\n"
- " return new CustomMapInstantiator( mappingInfo );\n"
- " }\n"
- "\n"
- " private static final class CustomMapInstantiator\n"
- " extends org.hibernate.tuple.DynamicMapInstantitor {\n"
- " // override the generateMap() method to return our custom map...\n"
- " protected final Map generateMap() {\n"
- " return new CustomMap();\n"
- " }\n"
- " }\n"
- "}]]>"
-msgstr ""
-
#. Tag: title
-#: persistent_classes.xml:353
#, no-c-format
msgid "EntityNameResolvers"
msgstr ""
#. Tag: para
-#: persistent_classes.xml:355
#, no-c-format
msgid "The <interfacename>org.hibernate.EntityNameResolver</interfacename> interface is a contract for resolving the entity name of a given entity instance. The interface defines a single method <methodname>resolveEntityName</methodname> which is passed the entity instance and is expected to return the appropriate entity name (null is allowed and would indicate that the resolver does not know how to resolve the entity name of the given entity instance). Generally speaking, an <interfacename>org.hibernate.EntityNameResolver</interfacename> is going to be most useful in the case of dynamic models. One example might be using proxied interfaces as your domain model. The hibernate test suite has an example of this exact style of usage under the <package>org.hibernate.test.dynamicentity.tuplizer2</package>. Here is some of the code from that package for illustration."
msgstr ""
-#. Tag: programlisting
-#: persistent_classes.xml:367
-#, no-c-format
-msgid ""
- "/**\n"
- " * A very trivial JDK Proxy InvocationHandler implementation where we proxy an interface as\n"
- " * the domain model and simply store persistent state in an internal Map. This is an extremely\n"
- " * trivial example meant only for illustration.\n"
- " */\n"
- "public final class DataProxyHandler implements InvocationHandler {\n"
- " private String entityName;\n"
- " private HashMap data = new HashMap();\n"
- "\n"
- " public DataProxyHandler(String entityName, Serializable id) {\n"
- " this.entityName = entityName;\n"
- " data.put( \"Id\", id );\n"
- " }\n"
- "\n"
- " public Object invoke(Object proxy, Method method, Object[] args) throws Throwable {\n"
- " String methodName = method.getName();\n"
- " if ( methodName.startsWith( \"set\" ) ) {\n"
- " String propertyName = methodName.substring( 3 );\n"
- " data.put( propertyName, args[0] );\n"
- " }\n"
- " else if ( methodName.startsWith( \"get\" ) ) {\n"
- " String propertyName = methodName.substring( 3 );\n"
- " return data.get( propertyName );\n"
- " }\n"
- " else if ( \"toString\".equals( methodName ) ) {\n"
- " return entityName + \"#\" + data.get( \"Id\" );\n"
- " }\n"
- " else if ( \"hashCode\".equals( methodName ) ) {\n"
- " return new Integer( this.hashCode() );\n"
- " }\n"
- " return null;\n"
- " }\n"
- "\n"
- " public String getEntityName() {\n"
- " return entityName;\n"
- " }\n"
- "\n"
- " public HashMap getData() {\n"
- " return data;\n"
- " }\n"
- "}\n"
- "\n"
- "/**\n"
- " *\n"
- " */\n"
- "public class ProxyHelper {\n"
- " public static String extractEntityName(Object object) {\n"
- " // Our custom java.lang.reflect.Proxy instances actually bundle\n"
- " // their appropriate entity name, so we simply extract it from there\n"
- " // if this represents one of our proxies; otherwise, we return null\n"
- " if ( Proxy.isProxyClass( object.getClass() ) ) {\n"
- " InvocationHandler handler = Proxy.getInvocationHandler( object );\n"
- " if ( DataProxyHandler.class.isAssignableFrom( handler.getClass() ) ) {\n"
- " DataProxyHandler myHandler = ( DataProxyHandler ) handler;\n"
- " return myHandler.getEntityName();\n"
- " }\n"
- " }\n"
- " return null;\n"
- " }\n"
- "\n"
- " // various other utility methods ....\n"
- "\n"
- "}\n"
- "\n"
- "/**\n"
- " * The EntityNameResolver implementation.\n"
- " * IMPL NOTE : An EntityNameResolver really defines a strategy for how entity names should be\n"
- " * resolved. Since this particular impl can handle resolution for all of our entities we want to\n"
- " * take advantage of the fact that SessionFactoryImpl keeps these in a Set so that we only ever\n"
- " * have one instance registered. Why? Well, when it comes time to resolve an entity name,\n"
- " * Hibernate must iterate over all the registered resolvers. So keeping that number down\n"
- " * helps that process be as speedy as possible. Hence the equals and hashCode impls\n"
- " */\n"
- "public class MyEntityNameResolver implements EntityNameResolver {\n"
- " public static final MyEntityNameResolver INSTANCE = new MyEntityNameResolver();\n"
- "\n"
- " public String resolveEntityName(Object entity) {\n"
- " return ProxyHelper.extractEntityName( entity );\n"
- " }\n"
- "\n"
- " public boolean equals(Object obj) {\n"
- " return getClass().equals( obj.getClass() );\n"
- " }\n"
- "\n"
- " public int hashCode() {\n"
- " return getClass().hashCode();\n"
- " }\n"
- "}\n"
- "\n"
- "public class MyEntityTuplizer extends PojoEntityTuplizer {\n"
- " public MyEntityTuplizer(EntityMetamodel entityMetamodel, PersistentClass mappedEntity) {\n"
- " super( entityMetamodel, mappedEntity );\n"
- " }\n"
- "\n"
- " public EntityNameResolver[] getEntityNameResolvers() {\n"
- " return new EntityNameResolver[] { MyEntityNameResolver.INSTANCE };\n"
- " }\n"
- "\n"
- " public String determineConcreteSubclassEntityName(Object entityInstance, SessionFactoryImplementor factory) {\n"
- " String entityName = ProxyHelper.extractEntityName( entityInstance );\n"
- " if ( entityName == null ) {\n"
- " entityName = super.determineConcreteSubclassEntityName( entityInstance, factory );\n"
- " }\n"
- " return entityName;\n"
- " }\n"
- "\n"
- " ...\n"
- "}"
-msgstr ""
-
#. Tag: para
-#: persistent_classes.xml:369
#, no-c-format
msgid "In order to register an <interfacename>org.hibernate.EntityNameResolver</interfacename> users must either:"
msgstr ""
#. Tag: para
-#: persistent_classes.xml:373
#, no-c-format
-msgid "Implement a custom <link linkend=\"persistent-classes-tuplizers\">Tuplizer</link>, implementing the <methodname>getEntityNameResolvers</methodname> method."
+msgid "Implement a custom Tupelizer implementing the <methodname>getEntityNameResolvers</methodname> method (see <xref linkend=\"persistent-classes-tuplizers\" />)."
msgstr ""
#. Tag: para
-#: persistent_classes.xml:379
#, no-c-format
msgid "Register it with the <classname>org.hibernate.impl.SessionFactoryImpl</classname> (which is the implementation class for <interfacename>org.hibernate.SessionFactory</interfacename>) using the <methodname>registerEntityNameResolver</methodname> method."
msgstr ""
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/portability.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/portability.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/portability.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,135 +1,138 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-23 18:41+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:19\n"
+"PO-Revision-Date: 2010-01-08T04:07:19\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
-#: portability.xml:26
#, no-c-format
msgid "Database Portability Considerations"
msgstr ""
#. Tag: title
-#: portability.xml:29
#, no-c-format
msgid "Portability Basics"
msgstr ""
#. Tag: para
-#: portability.xml:31
#, no-c-format
msgid "One of the selling points of Hibernate (and really Object/Relational Mapping as a whole) is the notion of database portability. This could mean an internal IT user migrating from one database vendor to another, or it could mean a framework or deployable application consuming Hibernate to simultaneously target multiple database products by their users. Regardless of the exact scenario, the basic idea is that you want Hibernate to help you run against any number of databases without changes to your code, and ideally without any changes to the mapping metadata."
msgstr ""
#. Tag: title
-#: portability.xml:42
#, no-c-format
msgid "Dialect"
msgstr ""
#. Tag: para
-#: portability.xml:44
#, no-c-format
msgid "The first line of portability for Hibernate is the dialect, which is a specialization of the <classname>org.hibernate.dialect.Dialect</classname> contract. A dialect encapsulates all the differences in how Hibernate must communicate with a particular database to accomplish some task like getting a sequence value or structuring a SELECT query. Hibernate bundles a wide range of dialects for many of the most popular databases. If you find that your particular database is not among them, it is not terribly difficult to write your own."
msgstr ""
#. Tag: title
-#: portability.xml:55
#, no-c-format
msgid "Dialect resolution"
msgstr ""
#. Tag: para
-#: portability.xml:57
#, no-c-format
msgid "Originally, Hibernate would always require that users specify which dialect to use. In the case of users looking to simultaneously target multiple databases with their build that was problematic. Generally this required their users to configure the Hibernate dialect or defining their own method of setting that value."
msgstr ""
#. Tag: para
-#: portability.xml:64
#, no-c-format
msgid "Starting with version 3.2, Hibernate introduced the notion of automatically detecting the dialect to use based on the <interfacename>java.sql.DatabaseMetaData</interfacename> obtained from a <interfacename>java.sql.Connection</interfacename> to that database. This was much better, expect that this resolution was limited to databases Hibernate know about ahead of time and was in no way configurable or overrideable."
msgstr ""
#. Tag: para
-#: portability.xml:72
#, no-c-format
-msgid "Starting with version 3.3, Hibernate has a fare more powerful way to automatically determine which dialect to should be used by relying on a series of delegates which implement the <interfacename>org.hibernate.dialect.resolver.DialectResolver</interfacename> which defines only a single method:<programlisting><![CDATA[public Dialect resolveDialect(DatabaseMetaData metaData) throws JDBCConnectionException]]></programlisting>. The basic contract here is that if the resolver 'understands' the given database metadata then it returns the corresponding Dialect; if not it returns null and the process continues to the next resolver. The signature also identifies <exceptionname>org.hibernate.exception.JDBCConnectionException</exceptionname> as possibly being thrown. A JDBCConnectionException here is interpreted to imply a \"non transient\" (aka non-recoverable) connection problem and is used to indicate an immediate stop to resolution attempts. All other exceptions result in a!
warning and continuing on to the next resolver."
+msgid "Starting with version 3.3, Hibernate has a fare more powerful way to automatically determine which dialect to should be used by relying on a series of delegates which implement the <interfacename>org.hibernate.dialect.resolver.DialectResolver</interfacename> which defines only a single method:<programlisting>public Dialect resolveDialect(DatabaseMetaData metaData) throws JDBCConnectionException</programlisting>. The basic contract here is that if the resolver 'understands' the given database metadata then it returns the corresponding Dialect; if not it returns null and the process continues to the next resolver. The signature also identifies <exceptionname>org.hibernate.exception.JDBCConnectionException</exceptionname> as possibly being thrown. A JDBCConnectionException here is interpreted to imply a \"non transient\" (aka non-recoverable) connection problem and is used to indicate an immediate stop to resolution attempts. All other exceptions result in a warning and!
continuing on to the next resolver."
msgstr ""
#. Tag: para
-#: portability.xml:85
#, no-c-format
msgid "The cool part about these resolvers is that users can also register their own custom resolvers which will be processed ahead of the built-in Hibernate ones. This might be useful in a number of different situations: it allows easy integration for auto-detection of dialects beyond those shipped with HIbernate itself; it allows you to specify to use a custom dialect when a particular database is recognized; etc. To register one or more resolvers, simply specify them (seperated by commas, tabs or spaces) using the 'hibernate.dialect_resolvers' configuration setting (see the <constant>DIALECT_RESOLVERS</constant> constant on <classname>org.hibernate.cfg.Environment</classname>)."
msgstr ""
#. Tag: title
-#: portability.xml:98
#, no-c-format
msgid "Identifier generation"
msgstr ""
#. Tag: para
-#: portability.xml:100
#, no-c-format
-msgid "When considering portability between databases, another important decision is selecting the identifier generation stratagy you want to use. Originally Hibernate provided the <emphasis>native</emphasis> generator for this purpose, which was intended to select between a <emphasis>sequence</emphasis>, <emphasis>identity</emphasis>, or <emphasis>table</emphasis> strategy depending on the capability of the underlying database. However, an insidious implication of this approach comes about when targtetting some databases which support <emphasis>identity</emphasis> generation and some which do not. <emphasis>identity</emphasis> generation relies on the SQL definition of an IDENTITY (or auto-increment) column to manage the identifier value; it is what is known as a post-insert generation strategy becauase the insert must actually happen before we can know the identifier value. Because Hibernate relies on this identifier value to uniquely reference entities within a persisten!
ce context it must then issue the insert immediately when the users requests the entitiy be associated with the session (like via save() e.g.) regardless of current transactional semantics. <note> <para> Hibernate was changed slightly once the implication of this was better understood so that the insert is delayed in cases where that is feasible. </para> </note> The underlying issue is that the actual semanctics of the application itself changes in these cases."
+msgid "When considering portability between databases, another important decision is selecting the identifier generation stratagy you want to use. Originally Hibernate provided the <emphasis>native</emphasis> generator for this purpose, which was intended to select between a <emphasis>sequence</emphasis>, <emphasis>identity</emphasis>, or <emphasis>table</emphasis> strategy depending on the capability of the underlying database. However, an insidious implication of this approach comes about when targtetting some databases which support <emphasis>identity</emphasis> generation and some which do not. <emphasis>identity</emphasis> generation relies on the SQL definition of an IDENTITY (or auto-increment) column to manage the identifier value; it is what is known as a post-insert generation strategy becauase the insert must actually happen before we can know the identifier value. Because Hibernate relies on this identifier value to uniquely reference entities within a persisten!
ce context it must then issue the insert immediately when the users requests the entitiy be associated with the session (like via save() e.g.) regardless of current transactional semantics. The underlying issue is that the semantics of the application itself changes in these cases."
msgstr ""
#. Tag: para
-#: portability.xml:125
#, no-c-format
-msgid "Starting with version 3.2.3, Hibernate comes with a set of <ulink url=\"http://in.relation.to/2082.lace\">enhanced</ulink> identifier generators targetting portability in a much different way. <note> <para> There are specifically 2 bundled <emphasis>enhanced</emphasis>generators: <itemizedlist> <listitem> <para> <classname>org.hibernate.id.enhanced.SequenceStyleGenerator</classname> </para> </listitem> <listitem> <para> <classname>org.hibernate.id.enhanced.TableGenerator</classname> </para> </listitem> </itemizedlist> </para> </note> The idea behind these generators is to port the actual semantics of the identifer value generation to the different databases. For example, the <classname>org.hibernate.id.enhanced.SequenceStyleGenerator</classname> mimics the behavior of a sequence on databases which do not support sequences by using a table."
+msgid "Hibernate has been improved so that the insert is delayed in cases where that is feasible."
msgstr ""
+#. Tag: para
+#, no-c-format
+msgid "Starting with version 3.2.3, Hibernate comes with a set of <ulink url=\"http://in.relation.to/2082.lace\">enhanced</ulink> identifier generators targetting portability in a much different way."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are specifically 2 bundled <emphasis>enhanced</emphasis>generators:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<classname>org.hibernate.id.enhanced.SequenceStyleGenerator</classname>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<classname>org.hibernate.id.enhanced.TableGenerator</classname>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The idea behind these generators is to port the actual semantics of the identifer value generation to the different databases. For example, the <classname>org.hibernate.id.enhanced.SequenceStyleGenerator</classname> mimics the behavior of a sequence on databases which do not support sequences by using a table."
+msgstr ""
+
#. Tag: title
-#: portability.xml:154
#, no-c-format
msgid "Database functions"
msgstr ""
#. Tag: para
-#: portability.xml:157
#, no-c-format
-msgid "This is an area in Hibernate in need of improvement. In terms of portability concerns, this function handling currently works pretty well from HQL; however, it is quite lacking in all other aspects."
+msgid "This is a new area in Hibernate and as such it is not as mature as the overall Hibernate experience."
msgstr ""
#. Tag: para
-#: portability.xml:164
#, no-c-format
msgid "SQL functions can be referenced in many ways by users. However, not all databases support the same set of functions. Hibernate, provides a means of mapping a <emphasis>logical</emphasis> function name to a a delegate which knows how to render that particular function, perhaps even using a totally different physical function call."
msgstr ""
#. Tag: para
-#: portability.xml:170
#, no-c-format
msgid "Technically this function registration is handled through the <classname>org.hibernate.dialect.function.SQLFunctionRegistry</classname> class which is intended to allow users to provide custom function definitions without having to provide a custom dialect. This specific behavior is not fully completed as of yet."
msgstr ""
#. Tag: para
-#: portability.xml:177
#, no-c-format
msgid "It is sort of implemented such that users can programatically register functions with the <classname>org.hibernate.cfg.Configuration</classname> and those functions will be recognized for HQL."
msgstr ""
#. Tag: title
-#: portability.xml:187
#, no-c-format
msgid "Type mappings"
msgstr ""
#. Tag: para
-#: portability.xml:189
#, no-c-format
msgid "This section scheduled for completion at a later date..."
msgstr ""
Deleted: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/preface.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/preface.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/preface.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,112 +0,0 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
-#
-#, fuzzy
-msgid ""
-msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-23 18:41+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#: preface.xml:29
-#, no-c-format
-msgid "Preface"
-msgstr ""
-
-#. Tag: para
-#: preface.xml:31
-#, no-c-format
-msgid "Working with object-oriented software and a relational database can be cumbersome and time consuming in today's enterprise environments. Hibernate is an Object/Relational Mapping tool for Java environments. The term Object/Relational Mapping (ORM) refers to the technique of mapping a data representation from an object model to a relational data model with a SQL-based schema."
-msgstr ""
-
-#. Tag: para
-#: preface.xml:39
-#, no-c-format
-msgid "Hibernate not only takes care of the mapping from Java classes to database tables (and from Java data types to SQL data types), but also provides data query and retrieval facilities. It can also significantly reduce development time otherwise spent with manual data handling in SQL and JDBC."
-msgstr ""
-
-#. Tag: para
-#: preface.xml:46
-#, no-c-format
-msgid "Hibernate's goal is to relieve the developer from 95 percent of common data persistence related programming tasks. Hibernate may not be the best solution for data-centric applications that only use stored-procedures to implement the business logic in the database, it is most useful with object-oriented domain models and business logic in the Java-based middle-tier. However, Hibernate can certainly help you to remove or encapsulate vendor-specific SQL code and will help with the common task of result set translation from a tabular representation to a graph of objects."
-msgstr ""
-
-#. Tag: para
-#: preface.xml:56
-#, no-c-format
-msgid "If you are new to Hibernate and Object/Relational Mapping or even Java, please follow these steps:"
-msgstr ""
-
-#. Tag: para
-#: preface.xml:63
-#, no-c-format
-msgid "Read <xref linkend=\"tutorial\"/> for a tutorial with step-by-step instructions. The source code for the tutorial is included in the distribution in the <literal>doc/reference/tutorial/</literal> directory."
-msgstr ""
-
-#. Tag: para
-#: preface.xml:71
-#, no-c-format
-msgid "Read <xref linkend=\"architecture\"/> to understand the environments where Hibernate can be used."
-msgstr ""
-
-#. Tag: para
-#: preface.xml:77
-#, no-c-format
-msgid "View the <literal>eg/</literal> directory in the Hibernate distribution. It contains a simple standalone application. Copy your JDBC driver to the <literal>lib/</literal> directory and edit <literal>etc/hibernate.properties</literal>, specifying correct values for your database. From a command prompt in the distribution directory, type <literal>ant eg</literal> (using Ant), or under Windows, type <literal>build eg</literal>."
-msgstr ""
-
-#. Tag: para
-#: preface.xml:88
-#, no-c-format
-msgid "Use this reference documentation as your primary source of information. Consider reading <biblioref linkend=\"biblio-JPwH\"></biblioref> if you need more help with application design, or if you prefer a step-by-step tutorial. Also visit <ulink url=\"http://caveatemptor.hibernate.org\"></ulink> and download the example application from <biblioref linkend=\"biblio-JPwH\"></biblioref>."
-msgstr ""
-
-#. Tag: para
-#: preface.xml:98
-#, no-c-format
-msgid "FAQs are answered on the Hibernate website."
-msgstr ""
-
-#. Tag: para
-#: preface.xml:103
-#, no-c-format
-msgid "Links to third party demos, examples, and tutorials are maintained on the Hibernate website."
-msgstr ""
-
-#. Tag: para
-#: preface.xml:109
-#, no-c-format
-msgid "The Community Area on the Hibernate website is a good resource for design patterns and various integration solutions (Tomcat, JBoss AS, Struts, EJB, etc.)."
-msgstr ""
-
-#. Tag: para
-#: preface.xml:117
-#, no-c-format
-msgid "If you have questions, use the user forum linked on the Hibernate website. We also provide a JIRA issue tracking system for bug reports and feature requests. If you are interested in the development of Hibernate, join the developer mailing list. If you are interested in translating this documentation into your language, contact us on the developer mailing list."
-msgstr ""
-
-#. Tag: para
-#: preface.xml:125
-#, no-c-format
-msgid "Commercial development support, production support, and training for Hibernate is available through JBoss Inc. (see http://www.hibernate.org/SupportTraining/). Hibernate is a Professional Open Source project and a critical component of the JBoss Enterprise Middleware System (JEMS) suite of products."
-msgstr ""
-
-#. Tag: title
-#: preface.xml:133
-#, no-c-format
-msgid "Feedback"
-msgstr ""
-
-#. Tag: para
-#: preface.xml:134
-#, no-c-format
-msgid "Use <ulink url=\"http://opensource.atlassian.com/projects/hibernate\">Hibernate JIRA</ulink> to report errors or request enhacements to this documentation."
-msgstr ""
-
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/query_criteria.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/query_criteria.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/query_criteria.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,624 +1,219 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-10 21:02+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:19\n"
+"PO-Revision-Date: 2010-01-08T04:07:19\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
-#: query_criteria.xml:29
#, no-c-format
msgid "Criteria Queries"
msgstr ""
#. Tag: para
-#: query_criteria.xml:31
#, no-c-format
msgid "Hibernate features an intuitive, extensible criteria query API."
msgstr ""
#. Tag: title
-#: query_criteria.xml:36
#, no-c-format
msgid "Creating a <literal>Criteria</literal> instance"
msgstr ""
#. Tag: para
-#: query_criteria.xml:38
#, no-c-format
msgid "The interface <literal>org.hibernate.Criteria</literal> represents a query against a particular persistent class. The <literal>Session</literal> is a factory for <literal>Criteria</literal> instances."
msgstr ""
-#. Tag: programlisting
-#: query_criteria.xml:44
-#, no-c-format
-msgid ""
- "<![CDATA[Criteria crit = sess.createCriteria(Cat.class);\n"
- "crit.setMaxResults(50);\n"
- "List cats = crit.list();]]>"
-msgstr ""
-
#. Tag: title
-#: query_criteria.xml:49
#, no-c-format
msgid "Narrowing the result set"
msgstr ""
#. Tag: para
-#: query_criteria.xml:51
#, no-c-format
msgid "An individual query criterion is an instance of the interface <literal>org.hibernate.criterion.Criterion</literal>. The class <literal>org.hibernate.criterion.Restrictions</literal> defines factory methods for obtaining certain built-in <literal>Criterion</literal> types."
msgstr ""
-#. Tag: programlisting
-#: query_criteria.xml:59
-#, no-c-format
-msgid ""
- "<![CDATA[List cats = sess.createCriteria(Cat.class)\n"
- " .add( Restrictions.like(\"name\", \"Fritz%\") )\n"
- " .add( Restrictions.between(\"weight\", minWeight, maxWeight) )\n"
- " .list();]]>"
-msgstr ""
-
#. Tag: para
-#: query_criteria.xml:61
#, no-c-format
msgid "Restrictions can be grouped logically."
msgstr ""
-#. Tag: programlisting
-#: query_criteria.xml:65
-#, no-c-format
-msgid ""
- "<![CDATA[List cats = sess.createCriteria(Cat.class)\n"
- " .add( Restrictions.like(\"name\", \"Fritz%\") )\n"
- " .add( Restrictions.or(\n"
- " Restrictions.eq( \"age\", new Integer(0) ),\n"
- " Restrictions.isNull(\"age\")\n"
- " ) )\n"
- " .list();]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_criteria.xml:67
-#, no-c-format
-msgid ""
- "<![CDATA[List cats = sess.createCriteria(Cat.class)\n"
- " .add( Restrictions.in( \"name\", new String[] { \"Fritz\", \"Izi\", \"Pk\" } ) )\n"
- " .add( Restrictions.disjunction()\n"
- " .add( Restrictions.isNull(\"age\") )\n"
- " .add( Restrictions.eq(\"age\", new Integer(0) ) )\n"
- " .add( Restrictions.eq(\"age\", new Integer(1) ) )\n"
- " .add( Restrictions.eq(\"age\", new Integer(2) ) )\n"
- " ) )\n"
- " .list();]]>"
-msgstr ""
-
#. Tag: para
-#: query_criteria.xml:69
#, no-c-format
msgid "There are a range of built-in criterion types (<literal>Restrictions</literal> subclasses). One of the most useful allows you to specify SQL directly."
msgstr ""
-#. Tag: programlisting
-#: query_criteria.xml:74
-#, no-c-format
-msgid ""
- "<![CDATA[List cats = sess.createCriteria(Cat.class)\n"
- " .add( Restrictions.sqlRestriction(\"lower({alias}.name) like lower(?)\", \"Fritz%\", Hibernate.STRING) )\n"
- " .list();]]>"
-msgstr ""
-
#. Tag: para
-#: query_criteria.xml:76
#, no-c-format
msgid "The <literal>{alias}</literal> placeholder with be replaced by the row alias of the queried entity."
msgstr ""
#. Tag: para
-#: query_criteria.xml:81
#, no-c-format
msgid "You can also obtain a criterion from a <literal>Property</literal> instance. You can create a <literal>Property</literal> by calling <literal>Property.forName()</literal>:"
msgstr ""
-#. Tag: programlisting
-#: query_criteria.xml:87
-#, no-c-format
-msgid ""
- "<![CDATA[\n"
- "Property age = Property.forName(\"age\");\n"
- "List cats = sess.createCriteria(Cat.class)\n"
- " .add( Restrictions.disjunction()\n"
- " .add( age.isNull() )\n"
- " .add( age.eq( new Integer(0) ) )\n"
- " .add( age.eq( new Integer(1) ) )\n"
- " .add( age.eq( new Integer(2) ) )\n"
- " ) )\n"
- " .add( Property.forName(\"name\").in( new String[] { \"Fritz\", \"Izi\", \"Pk\" } ) )\n"
- " .list();]]>"
-msgstr ""
-
#. Tag: title
-#: query_criteria.xml:92
#, no-c-format
msgid "Ordering the results"
msgstr ""
#. Tag: para
-#: query_criteria.xml:94
#, no-c-format
msgid "You can order the results using <literal>org.hibernate.criterion.Order</literal>."
msgstr ""
-#. Tag: programlisting
-#: query_criteria.xml:98
-#, no-c-format
-msgid ""
- "<![CDATA[List cats = sess.createCriteria(Cat.class)\n"
- " .add( Restrictions.like(\"name\", \"F%\")\n"
- " .addOrder( Order.asc(\"name\") )\n"
- " .addOrder( Order.desc(\"age\") )\n"
- " .setMaxResults(50)\n"
- " .list();]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_criteria.xml:100
-#, no-c-format
-msgid ""
- "<![CDATA[List cats = sess.createCriteria(Cat.class)\n"
- " .add( Property.forName(\"name\").like(\"F%\") )\n"
- " .addOrder( Property.forName(\"name\").asc() )\n"
- " .addOrder( Property.forName(\"age\").desc() )\n"
- " .setMaxResults(50)\n"
- " .list();]]>"
-msgstr ""
-
#. Tag: title
-#: query_criteria.xml:105
#, no-c-format
msgid "Associations"
msgstr ""
#. Tag: para
-#: query_criteria.xml:107
#, no-c-format
msgid "By navigating associations using <literal>createCriteria()</literal> you can specify constraints upon related entities:"
msgstr ""
-#. Tag: programlisting
-#: query_criteria.xml:112
-#, no-c-format
-msgid ""
- "<![CDATA[List cats = sess.createCriteria(Cat.class)\n"
- " .add( Restrictions.like(\"name\", \"F%\") )\n"
- " .createCriteria(\"kittens\")\n"
- " .add( Restrictions.like(\"name\", \"F%\") )\n"
- " .list();]]>"
-msgstr ""
-
#. Tag: para
-#: query_criteria.xml:114
#, no-c-format
msgid "The second <literal>createCriteria()</literal> returns a new instance of <literal>Criteria</literal> that refers to the elements of the <literal>kittens</literal> collection."
msgstr ""
#. Tag: para
-#: query_criteria.xml:120
#, no-c-format
msgid "There is also an alternate form that is useful in certain circumstances:"
msgstr ""
-#. Tag: programlisting
-#: query_criteria.xml:124
-#, no-c-format
-msgid ""
- "<![CDATA[List cats = sess.createCriteria(Cat.class)\n"
- " .createAlias(\"kittens\", \"kt\")\n"
- " .createAlias(\"mate\", \"mt\")\n"
- " .add( Restrictions.eqProperty(\"kt.name\", \"mt.name\") )\n"
- " .list();]]>"
-msgstr ""
-
#. Tag: para
-#: query_criteria.xml:126
#, no-c-format
msgid "(<literal>createAlias()</literal> does not create a new instance of <literal>Criteria</literal>.)"
msgstr ""
#. Tag: para
-#: query_criteria.xml:131
#, no-c-format
msgid "The kittens collections held by the <literal>Cat</literal> instances returned by the previous two queries are <emphasis>not</emphasis> pre-filtered by the criteria. If you want to retrieve just the kittens that match the criteria, you must use a <literal>ResultTransformer</literal>."
msgstr ""
-#. Tag: programlisting
-#: query_criteria.xml:138
-#, no-c-format
-msgid ""
- "<![CDATA[List cats = sess.createCriteria(Cat.class)\n"
- " .createCriteria(\"kittens\", \"kt\")\n"
- " .add( Restrictions.eq(\"name\", \"F%\") )\n"
- " .setResultTransformer(Criteria.ALIAS_TO_ENTITY_MAP)\n"
- " .list();\n"
- "Iterator iter = cats.iterator();\n"
- "while ( iter.hasNext() ) {\n"
- " Map map = (Map) iter.next();\n"
- " Cat cat = (Cat) map.get(Criteria.ROOT_ALIAS);\n"
- " Cat kitten = (Cat) map.get(\"kt\");\n"
- "}]]>"
-msgstr ""
-
#. Tag: title
-#: query_criteria.xml:143
#, no-c-format
msgid "Dynamic association fetching"
msgstr ""
#. Tag: para
-#: query_criteria.xml:145
#, no-c-format
msgid "You can specify association fetching semantics at runtime using <literal>setFetchMode()</literal>."
msgstr ""
-#. Tag: programlisting
-#: query_criteria.xml:150
-#, no-c-format
-msgid ""
- "<![CDATA[List cats = sess.createCriteria(Cat.class)\n"
- " .add( Restrictions.like(\"name\", \"Fritz%\") )\n"
- " .setFetchMode(\"mate\", FetchMode.EAGER)\n"
- " .setFetchMode(\"kittens\", FetchMode.EAGER)\n"
- " .list();]]>"
-msgstr ""
-
#. Tag: para
-#: query_criteria.xml:152
#, no-c-format
-msgid "This query will fetch both <literal>mate</literal> and <literal>kittens</literal> by outer join. See <xref linkend=\"performance-fetching\"/> for more information."
+msgid "This query will fetch both <literal>mate</literal> and <literal>kittens</literal> by outer join. See <xref linkend=\"performance-fetching\" /> for more information."
msgstr ""
#. Tag: title
-#: query_criteria.xml:160
#, no-c-format
msgid "Example queries"
msgstr ""
#. Tag: para
-#: query_criteria.xml:162
#, no-c-format
msgid "The class <literal>org.hibernate.criterion.Example</literal> allows you to construct a query criterion from a given instance."
msgstr ""
-#. Tag: programlisting
-#: query_criteria.xml:167
-#, no-c-format
-msgid ""
- "<![CDATA[Cat cat = new Cat();\n"
- "cat.setSex('F');\n"
- "cat.setColor(Color.BLACK);\n"
- "List results = session.createCriteria(Cat.class)\n"
- " .add( Example.create(cat) )\n"
- " .list();]]>"
-msgstr ""
-
#. Tag: para
-#: query_criteria.xml:169
#, no-c-format
msgid "Version properties, identifiers and associations are ignored. By default, null valued properties are excluded."
msgstr ""
#. Tag: para
-#: query_criteria.xml:174
#, no-c-format
msgid "You can adjust how the <literal>Example</literal> is applied."
msgstr ""
-#. Tag: programlisting
-#: query_criteria.xml:178
-#, no-c-format
-msgid ""
- "<![CDATA[Example example = Example.create(cat)\n"
- " .excludeZeroes() //exclude zero valued properties\n"
- " .excludeProperty(\"color\") //exclude the property named \"color\"\n"
- " .ignoreCase() //perform case insensitive string comparisons\n"
- " .enableLike(); //use like for string comparisons\n"
- "List results = session.createCriteria(Cat.class)\n"
- " .add(example)\n"
- " .list();]]>"
-msgstr ""
-
#. Tag: para
-#: query_criteria.xml:180
#, no-c-format
msgid "You can even use examples to place criteria upon associated objects."
msgstr ""
-#. Tag: programlisting
-#: query_criteria.xml:184
-#, no-c-format
-msgid ""
- "<![CDATA[List results = session.createCriteria(Cat.class)\n"
- " .add( Example.create(cat) )\n"
- " .createCriteria(\"mate\")\n"
- " .add( Example.create( cat.getMate() ) )\n"
- " .list();]]>"
-msgstr ""
-
#. Tag: title
-#: query_criteria.xml:189
#, no-c-format
msgid "Projections, aggregation and grouping"
msgstr ""
#. Tag: para
-#: query_criteria.xml:190
#, no-c-format
msgid "The class <literal>org.hibernate.criterion.Projections</literal> is a factory for <literal>Projection</literal> instances. You can apply a projection to a query by calling <literal>setProjection()</literal>."
msgstr ""
-#. Tag: programlisting
-#: query_criteria.xml:196
-#, no-c-format
-msgid ""
- "<![CDATA[List results = session.createCriteria(Cat.class)\n"
- " .setProjection( Projections.rowCount() )\n"
- " .add( Restrictions.eq(\"color\", Color.BLACK) )\n"
- " .list();]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_criteria.xml:198
-#, no-c-format
-msgid ""
- "<![CDATA[List results = session.createCriteria(Cat.class)\n"
- " .setProjection( Projections.projectionList()\n"
- " .add( Projections.rowCount() )\n"
- " .add( Projections.avg(\"weight\") )\n"
- " .add( Projections.max(\"weight\") )\n"
- " .add( Projections.groupProperty(\"color\") )\n"
- " )\n"
- " .list();]]>"
-msgstr ""
-
#. Tag: para
-#: query_criteria.xml:200
#, no-c-format
msgid "There is no explicit \"group by\" necessary in a criteria query. Certain projection types are defined to be <emphasis>grouping projections</emphasis>, which also appear in the SQL <literal>group by</literal> clause."
msgstr ""
#. Tag: para
-#: query_criteria.xml:206
#, no-c-format
msgid "An alias can be assigned to a projection so that the projected value can be referred to in restrictions or orderings. Here are two different ways to do this:"
msgstr ""
-#. Tag: programlisting
-#: query_criteria.xml:212
-#, no-c-format
-msgid ""
- "<![CDATA[List results = session.createCriteria(Cat.class)\n"
- " .setProjection( Projections.alias( Projections.groupProperty(\"color\"), \"colr\" ) )\n"
- " .addOrder( Order.asc(\"colr\") )\n"
- " .list();]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_criteria.xml:214
-#, no-c-format
-msgid ""
- "<![CDATA[List results = session.createCriteria(Cat.class)\n"
- " .setProjection( Projections.groupProperty(\"color\").as(\"colr\") )\n"
- " .addOrder( Order.asc(\"colr\") )\n"
- " .list();]]>"
-msgstr ""
-
#. Tag: para
-#: query_criteria.xml:216
#, no-c-format
msgid "The <literal>alias()</literal> and <literal>as()</literal> methods simply wrap a projection instance in another, aliased, instance of <literal>Projection</literal>. As a shortcut, you can assign an alias when you add the projection to a projection list:"
msgstr ""
-#. Tag: programlisting
-#: query_criteria.xml:223
-#, no-c-format
-msgid ""
- "<![CDATA[List results = session.createCriteria(Cat.class)\n"
- " .setProjection( Projections.projectionList()\n"
- " .add( Projections.rowCount(), \"catCountByColor\" )\n"
- " .add( Projections.avg(\"weight\"), \"avgWeight\" )\n"
- " .add( Projections.max(\"weight\"), \"maxWeight\" )\n"
- " .add( Projections.groupProperty(\"color\"), \"color\" )\n"
- " )\n"
- " .addOrder( Order.desc(\"catCountByColor\") )\n"
- " .addOrder( Order.desc(\"avgWeight\") )\n"
- " .list();]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_criteria.xml:225
-#, no-c-format
-msgid ""
- "<![CDATA[List results = session.createCriteria(Domestic.class, \"cat\")\n"
- " .createAlias(\"kittens\", \"kit\")\n"
- " .setProjection( Projections.projectionList()\n"
- " .add( Projections.property(\"cat.name\"), \"catName\" )\n"
- " .add( Projections.property(\"kit.name\"), \"kitName\" )\n"
- " )\n"
- " .addOrder( Order.asc(\"catName\") )\n"
- " .addOrder( Order.asc(\"kitName\") )\n"
- " .list();]]>"
-msgstr ""
-
#. Tag: para
-#: query_criteria.xml:227
#, no-c-format
msgid "You can also use <literal>Property.forName()</literal> to express projections:"
msgstr ""
-#. Tag: programlisting
-#: query_criteria.xml:231
-#, no-c-format
-msgid ""
- "<![CDATA[List results = session.createCriteria(Cat.class)\n"
- " .setProjection( Property.forName(\"name\") )\n"
- " .add( Property.forName(\"color\").eq(Color.BLACK) )\n"
- " .list();]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_criteria.xml:233
-#, no-c-format
-msgid ""
- "<![CDATA[List results = session.createCriteria(Cat.class)\n"
- " .setProjection( Projections.projectionList()\n"
- " .add( Projections.rowCount().as(\"catCountByColor\") )\n"
- " .add( Property.forName(\"weight\").avg().as(\"avgWeight\") )\n"
- " .add( Property.forName(\"weight\").max().as(\"maxWeight\") )\n"
- " .add( Property.forName(\"color\").group().as(\"color\" )\n"
- " )\n"
- " .addOrder( Order.desc(\"catCountByColor\") )\n"
- " .addOrder( Order.desc(\"avgWeight\") )\n"
- " .list();]]>"
-msgstr ""
-
#. Tag: title
-#: query_criteria.xml:238
#, no-c-format
msgid "Detached queries and subqueries"
msgstr ""
#. Tag: para
-#: query_criteria.xml:239
#, no-c-format
msgid "The <literal>DetachedCriteria</literal> class allows you to create a query outside the scope of a session and then execute it using an arbitrary <literal>Session</literal>."
msgstr ""
-#. Tag: programlisting
-#: query_criteria.xml:244
-#, no-c-format
-msgid ""
- "<![CDATA[DetachedCriteria query = DetachedCriteria.forClass(Cat.class)\n"
- " .add( Property.forName(\"sex\").eq('F') );\n"
- " \n"
- "Session session = ....;\n"
- "Transaction txn = session.beginTransaction();\n"
- "List results = query.getExecutableCriteria(session).setMaxResults(100).list();\n"
- "txn.commit();\n"
- "session.close();]]>"
-msgstr ""
-
#. Tag: para
-#: query_criteria.xml:246
#, no-c-format
msgid "A <literal>DetachedCriteria</literal> can also be used to express a subquery. Criterion instances involving subqueries can be obtained via <literal>Subqueries</literal> or <literal>Property</literal>."
msgstr ""
-#. Tag: programlisting
-#: query_criteria.xml:252
-#, no-c-format
-msgid ""
- "<![CDATA[DetachedCriteria avgWeight = DetachedCriteria.forClass(Cat.class)\n"
- " .setProjection( Property.forName(\"weight\").avg() );\n"
- "session.createCriteria(Cat.class)\n"
- " .add( Property.forName(\"weight\").gt(avgWeight) )\n"
- " .list();]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_criteria.xml:254
-#, no-c-format
-msgid ""
- "<![CDATA[DetachedCriteria weights = DetachedCriteria.forClass(Cat.class)\n"
- " .setProjection( Property.forName(\"weight\") );\n"
- "session.createCriteria(Cat.class)\n"
- " .add( Subqueries.geAll(\"weight\", weights) )\n"
- " .list();]]>"
-msgstr ""
-
#. Tag: para
-#: query_criteria.xml:256
#, no-c-format
msgid "Correlated subqueries are also possible:"
msgstr ""
-#. Tag: programlisting
-#: query_criteria.xml:260
-#, no-c-format
-msgid ""
- "<![CDATA[DetachedCriteria avgWeightForSex = DetachedCriteria.forClass(Cat.class, \"cat2\")\n"
- " .setProjection( Property.forName(\"weight\").avg() )\n"
- " .add( Property.forName(\"cat2.sex\").eqProperty(\"cat.sex\") );\n"
- "session.createCriteria(Cat.class, \"cat\")\n"
- " .add( Property.forName(\"weight\").gt(avgWeightForSex) )\n"
- " .list();]]>"
-msgstr ""
-
#. Tag: title
-#: query_criteria.xml:269
#, no-c-format
msgid "Queries by natural identifier"
msgstr ""
#. Tag: para
-#: query_criteria.xml:271
#, no-c-format
msgid "For most queries, including criteria queries, the query cache is not efficient because query cache invalidation occurs too frequently. However, there is a special kind of query where you can optimize the cache invalidation algorithm: lookups by a constant natural key. In some applications, this kind of query occurs frequently. The criteria API provides special provision for this use case."
msgstr ""
#. Tag: para
-#: query_criteria.xml:279
#, no-c-format
msgid "First, map the natural key of your entity using <literal><natural-id></literal> and enable use of the second-level cache."
msgstr ""
-#. Tag: programlisting
-#: query_criteria.xml:284
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"User\">\n"
- " <cache usage=\"read-write\"/>\n"
- " <id name=\"id\">\n"
- " <generator class=\"increment\"/>\n"
- " </id>\n"
- " <natural-id>\n"
- " <property name=\"name\"/>\n"
- " <property name=\"org\"/>\n"
- " </natural-id>\n"
- " <property name=\"password\"/>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: query_criteria.xml:286
#, no-c-format
msgid "This functionality is not intended for use with entities with <emphasis>mutable</emphasis> natural keys."
msgstr ""
#. Tag: para
-#: query_criteria.xml:291
#, no-c-format
msgid "Once you have enabled the Hibernate query cache, the <literal>Restrictions.naturalId()</literal> allows you to make use of the more efficient cache algorithm."
msgstr ""
-#. Tag: programlisting
-#: query_criteria.xml:297
-#, no-c-format
-msgid ""
- "<![CDATA[session.createCriteria(User.class)\n"
- " .add( Restrictions.naturalId()\n"
- " .set(\"name\", \"gavin\")\n"
- " .set(\"org\", \"hb\") \n"
- " ).setCacheable(true)\n"
- " .uniqueResult();]]>"
-msgstr ""
-
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/query_hql.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/query_hql.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/query_hql.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,1786 +1,793 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-10 21:02+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:19\n"
+"PO-Revision-Date: 2010-01-08T04:07:19\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
-#: query_hql.xml:29
#, no-c-format
msgid "HQL: The Hibernate Query Language"
msgstr ""
#. Tag: para
-#: query_hql.xml:31
#, no-c-format
msgid "Hibernate uses a powerful query language (HQL) that is similar in appearance to SQL. Compared with SQL, however, HQL is fully object-oriented and understands notions like inheritance, polymorphism and association."
msgstr ""
#. Tag: title
-#: query_hql.xml:38
#, no-c-format
msgid "Case Sensitivity"
msgstr ""
#. Tag: para
-#: query_hql.xml:40
#, no-c-format
msgid "With the exception of names of Java classes and properties, queries are case-insensitive. So <literal>SeLeCT</literal> is the same as <literal>sELEct</literal> is the same as <literal>SELECT</literal>, but <literal>org.hibernate.eg.FOO</literal> is not <literal>org.hibernate.eg.Foo</literal>, and <literal>foo.barSet</literal> is not <literal>foo.BARSET</literal>."
msgstr ""
#. Tag: para
-#: query_hql.xml:51
#, no-c-format
msgid "This manual uses lowercase HQL keywords. Some users find queries with uppercase keywords more readable, but this convention is unsuitable for queries embedded in Java code."
msgstr ""
#. Tag: title
-#: query_hql.xml:59
#, no-c-format
msgid "The from clause"
msgstr ""
#. Tag: para
-#: query_hql.xml:61
#, no-c-format
msgid "The simplest possible Hibernate query is of the form:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:65
-#, no-c-format
-msgid "<![CDATA[from eg.Cat]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:67
#, no-c-format
msgid "This returns all instances of the class <literal>eg.Cat</literal>. You do not usually need to qualify the class name, since <literal>auto-import</literal> is the default. For example:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:73
-#, no-c-format
-msgid "<![CDATA[from Cat]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:75
#, no-c-format
msgid "In order to refer to the <literal>Cat</literal> in other parts of the query, you will need to assign an <emphasis>alias</emphasis>. For example:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:81 query_hql.xml:396
-#, no-c-format
-msgid "<![CDATA[from Cat as cat]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:83
#, no-c-format
msgid "This query assigns the alias <literal>cat</literal> to <literal>Cat</literal> instances, so you can use that alias later in the query. The <literal>as</literal> keyword is optional. You could also write:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:89
-#, no-c-format
-msgid "<![CDATA[from Cat cat]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:91
#, no-c-format
msgid "Multiple classes can appear, resulting in a cartesian product or \"cross\" join."
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:95
-#, no-c-format
-msgid "<![CDATA[from Formula, Parameter]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:96
-#, no-c-format
-msgid "<![CDATA[from Formula as form, Parameter as param]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:98
#, no-c-format
msgid "It is good practice to name query aliases using an initial lowercase as this is consistent with Java naming standards for local variables (e.g. <literal>domesticCat</literal>)."
msgstr ""
#. Tag: title
-#: query_hql.xml:107
#, no-c-format
msgid "Associations and joins"
msgstr ""
#. Tag: para
-#: query_hql.xml:109
#, no-c-format
msgid "You can also assign aliases to associated entities or to elements of a collection of values using a <literal>join</literal>. For example:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:114
-#, no-c-format
-msgid ""
- "<![CDATA[from Cat as cat\n"
- " inner join cat.mate as mate\n"
- " left outer join cat.kittens as kitten]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:116
-#, no-c-format
-msgid "<![CDATA[from Cat as cat left join cat.mate.kittens as kittens]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:118
-#, no-c-format
-msgid "<![CDATA[from Formula form full join form.parameter param]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:120
#, no-c-format
msgid "The supported join types are borrowed from ANSI SQL:"
msgstr ""
-#. Tag: literal
-#: query_hql.xml:127
+#. Tag: para
#, no-c-format
-msgid "inner join"
+msgid "<literal>inner join</literal>"
msgstr ""
-#. Tag: literal
-#: query_hql.xml:132
+#. Tag: para
#, no-c-format
-msgid "left outer join"
+msgid "<literal>left outer join</literal>"
msgstr ""
-#. Tag: literal
-#: query_hql.xml:137
+#. Tag: para
#, no-c-format
-msgid "right outer join"
+msgid "<literal>right outer join</literal>"
msgstr ""
#. Tag: para
-#: query_hql.xml:141
#, no-c-format
msgid "<literal>full join</literal> (not usually useful)"
msgstr ""
#. Tag: para
-#: query_hql.xml:147
#, no-c-format
msgid "The <literal>inner join</literal>, <literal>left outer join</literal> and <literal>right outer join</literal> constructs may be abbreviated."
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:152
-#, no-c-format
-msgid ""
- "<![CDATA[from Cat as cat\n"
- " join cat.mate as mate\n"
- " left join cat.kittens as kitten]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:154
#, no-c-format
msgid "You may supply extra join conditions using the HQL <literal>with</literal> keyword."
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:159
-#, no-c-format
-msgid ""
- "<![CDATA[from Cat as cat\n"
- " left join cat.kittens as kitten\n"
- " with kitten.bodyWeight > 10.0]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:161
#, no-c-format
-msgid "A \"fetch\" join allows associations or collections of values to be initialized along with their parent objects using a single select. This is particularly useful in the case of a collection. It effectively overrides the outer join and lazy declarations of the mapping file for associations and collections. See <xref linkend=\"performance-fetching\"/> for more information."
+msgid "A \"fetch\" join allows associations or collections of values to be initialized along with their parent objects using a single select. This is particularly useful in the case of a collection. It effectively overrides the outer join and lazy declarations of the mapping file for associations and collections. See <xref linkend=\"performance-fetching\" /> for more information."
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:169
-#, no-c-format
-msgid ""
- "<![CDATA[from Cat as cat\n"
- " inner join fetch cat.mate\n"
- " left join fetch cat.kittens]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:171
#, no-c-format
msgid "A fetch join does not usually need to assign an alias, because the associated objects should not be used in the <literal>where</literal> clause (or any other clause). The associated objects are also not returned directly in the query results. Instead, they may be accessed via the parent object. The only reason you might need an alias is if you are recursively join fetching a further collection:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:179
-#, no-c-format
-msgid ""
- "<![CDATA[from Cat as cat\n"
- " inner join fetch cat.mate\n"
- " left join fetch cat.kittens child\n"
- " left join fetch child.kittens]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:181
#, no-c-format
msgid "The <literal>fetch</literal> construct cannot be used in queries called using <literal>iterate()</literal> (though <literal>scroll()</literal> can be used). <literal>Fetch</literal> should be used together with <literal>setMaxResults()</literal> or <literal>setFirstResult()</literal>, as these operations are based on the result rows which usually contain duplicates for eager collection fetching, hence, the number of rows is not what you would expect. <literal>Fetch</literal> should also not be used together with impromptu <literal>with</literal> condition. It is possible to create a cartesian product by join fetching more than one collection in a query, so take care in this case. Join fetching multiple collection roles can produce unexpected results for bag mappings, so user discretion is advised when formulating queries in this case. Finally, note that <literal>full join fetch</literal> and <literal>right join fetch</literal> are not meaningful."
msgstr ""
#. Tag: para
-#: query_hql.xml:196
#, no-c-format
msgid "If you are using property-level lazy fetching (with bytecode instrumentation), it is possible to force Hibernate to fetch the lazy properties in the first query immediately using <literal>fetch all properties</literal>."
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:202
-#, no-c-format
-msgid "<![CDATA[from Document fetch all properties order by name]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:203
-#, no-c-format
-msgid "<![CDATA[from Document doc fetch all properties where lower(doc.name) like '%cats%']]>"
-msgstr ""
-
#. Tag: title
-#: query_hql.xml:208
#, no-c-format
msgid "Forms of join syntax"
msgstr ""
#. Tag: para
-#: query_hql.xml:210
#, no-c-format
msgid "HQL supports two forms of association joining: <literal>implicit</literal> and <literal>explicit</literal>."
msgstr ""
#. Tag: para
-#: query_hql.xml:214
#, no-c-format
msgid "The queries shown in the previous section all use the <literal>explicit</literal> form, that is, where the join keyword is explicitly used in the from clause. This is the recommended form."
msgstr ""
#. Tag: para
-#: query_hql.xml:219
#, no-c-format
msgid "The <literal>implicit</literal> form does not use the join keyword. Instead, the associations are \"dereferenced\" using dot-notation. <literal>implicit</literal> joins can appear in any of the HQL clauses. <literal>implicit</literal> join result in inner joins in the resulting SQL statement."
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:226
-#, no-c-format
-msgid "<![CDATA[from Cat as cat where cat.mate.name like '%s%']]>"
-msgstr ""
-
#. Tag: title
-#: query_hql.xml:230
#, no-c-format
msgid "Referring to identifier property"
msgstr ""
#. Tag: para
-#: query_hql.xml:232
#, no-c-format
msgid "There are 2 ways to refer to an entity's identifier property:"
msgstr ""
#. Tag: para
-#: query_hql.xml:237
#, no-c-format
msgid "The special property (lowercase) <literal>id</literal> may be used to reference the identifier property of an entity <emphasis>provided that the entity does not define a non-identifier property named id</emphasis>."
msgstr ""
#. Tag: para
-#: query_hql.xml:244
#, no-c-format
msgid "If the entity defines a named identifier property, you can use that property name."
msgstr ""
#. Tag: para
-#: query_hql.xml:250
#, no-c-format
msgid "References to composite identifier properties follow the same naming rules. If the entity has a non-identifier property named id, the composite identifier property can only be referenced by its defined named. Otherwise, the special <literal>id</literal> property can be used to reference the identifier property."
msgstr ""
#. Tag: para
-#: query_hql.xml:258
#, no-c-format
msgid "Please note that, starting in version 3.2.2, this has changed significantly. In previous versions, <literal>id</literal> <emphasis>always</emphasis> referred to the identifier property regardless of its actual name. A ramification of that decision was that non-identifier properties named <literal>id</literal> could never be referenced in Hibernate queries."
msgstr ""
#. Tag: title
-#: query_hql.xml:269
#, no-c-format
msgid "The select clause"
msgstr ""
#. Tag: para
-#: query_hql.xml:271
#, no-c-format
msgid "The <literal>select</literal> clause picks which objects and properties to return in the query result set. Consider the following:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:276
-#, no-c-format
-msgid ""
- "<![CDATA[select mate\n"
- "from Cat as cat\n"
- " inner join cat.mate as mate]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:278
#, no-c-format
msgid "The query will select <literal>mate</literal>s of other <literal>Cat</literal>s. You can express this query more compactly as:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:283
-#, no-c-format
-msgid "<![CDATA[select cat.mate from Cat cat]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:285
#, no-c-format
msgid "Queries can return properties of any value type including properties of component type:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:289
-#, no-c-format
-msgid ""
- "<![CDATA[select cat.name from DomesticCat cat\n"
- "where cat.name like 'fri%']]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:291
-#, no-c-format
-msgid "<![CDATA[select cust.name.firstName from Customer as cust]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:293
#, no-c-format
msgid "Queries can return multiple objects and/or properties as an array of type <literal>Object[]</literal>:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:298
-#, no-c-format
-msgid ""
- "<![CDATA[select mother, offspr, mate.name\n"
- "from DomesticCat as mother\n"
- " inner join mother.mate as mate\n"
- " left outer join mother.kittens as offspr]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:300
#, no-c-format
msgid "Or as a <literal>List</literal>:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:304
-#, no-c-format
-msgid ""
- "<![CDATA[select new list(mother, offspr, mate.name)\n"
- "from DomesticCat as mother\n"
- " inner join mother.mate as mate\n"
- " left outer join mother.kittens as offspr]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:306
#, no-c-format
msgid "Or - assuming that the class <literal>Family</literal> has an appropriate constructor - as an actual typesafe Java object:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:310
-#, no-c-format
-msgid ""
- "<![CDATA[select new Family(mother, mate, offspr)\n"
- "from DomesticCat as mother\n"
- " join mother.mate as mate\n"
- " left join mother.kittens as offspr]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:313
#, no-c-format
msgid "You can assign aliases to selected expressions using <literal>as</literal>:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:317
-#, no-c-format
-msgid ""
- "<![CDATA[select max(bodyWeight) as max, min(bodyWeight) as min, count(*) as n\n"
- "from Cat cat]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:319
#, no-c-format
msgid "This is most useful when used together with <literal>select new map</literal>:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:323
-#, no-c-format
-msgid ""
- "<![CDATA[select new map( max(bodyWeight) as max, min(bodyWeight) as min, count(*) as n )\n"
- "from Cat cat]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:325
#, no-c-format
msgid "This query returns a <literal>Map</literal> from aliases to selected values."
msgstr ""
#. Tag: title
-#: query_hql.xml:332
#, no-c-format
msgid "Aggregate functions"
msgstr ""
#. Tag: para
-#: query_hql.xml:334
#, no-c-format
msgid "HQL queries can even return the results of aggregate functions on properties:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:338
-#, no-c-format
-msgid ""
- "<![CDATA[select avg(cat.weight), sum(cat.weight), max(cat.weight), count(cat)\n"
- "from Cat cat]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:349
#, no-c-format
msgid "The supported aggregate functions are:"
msgstr ""
-#. Tag: literal
-#: query_hql.xml:356
+#. Tag: para
#, no-c-format
-msgid "avg(...), sum(...), min(...), max(...)"
+msgid "<literal>avg(...), sum(...), min(...), max(...)</literal>"
msgstr ""
-#. Tag: literal
-#: query_hql.xml:361
+#. Tag: para
#, no-c-format
-msgid "count(*)"
+msgid "<literal>count(*)</literal>"
msgstr ""
-#. Tag: literal
-#: query_hql.xml:366
+#. Tag: para
#, no-c-format
-msgid "count(...), count(distinct ...), count(all...)"
+msgid "<literal>count(...), count(distinct ...), count(all...)</literal>"
msgstr ""
#. Tag: para
-#: query_hql.xml:371
#, no-c-format
msgid "You can use arithmetic operators, concatenation, and recognized SQL functions in the select clause:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:376
-#, no-c-format
-msgid ""
- "<![CDATA[select cat.weight + sum(kitten.weight)\n"
- "from Cat cat\n"
- " join cat.kittens kitten\n"
- "group by cat.id, cat.weight]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:378
-#, no-c-format
-msgid "<![CDATA[select firstName||' '||initial||' '||upper(lastName) from Person]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:380
#, no-c-format
msgid "The <literal>distinct</literal> and <literal>all</literal> keywords can be used and have the same semantics as in SQL."
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:385
-#, no-c-format
-msgid ""
- "<![CDATA[select distinct cat.name from Cat cat\n"
- "\n"
- "select count(distinct cat.name), count(cat) from Cat cat]]>"
-msgstr ""
-
#. Tag: title
-#: query_hql.xml:390
#, no-c-format
msgid "Polymorphic queries"
msgstr ""
#. Tag: para
-#: query_hql.xml:392
#, no-c-format
msgid "A query like:"
msgstr ""
#. Tag: para
-#: query_hql.xml:398
#, no-c-format
msgid "returns instances not only of <literal>Cat</literal>, but also of subclasses like <literal>DomesticCat</literal>. Hibernate queries can name <emphasis>any</emphasis> Java class or interface in the <literal>from</literal> clause. The query will return instances of all persistent classes that extend that class or implement the interface. The following query would return all persistent objects:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:406
-#, no-c-format
-msgid "<![CDATA[from java.lang.Object o]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:408
#, no-c-format
msgid "The interface <literal>Named</literal> might be implemented by various persistent classes:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:413
-#, no-c-format
-msgid "<![CDATA[from Named n, Named m where n.name = m.name]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:415
#, no-c-format
msgid "These last two queries will require more than one SQL <literal>SELECT</literal>. This means that the <literal>order by</literal> clause does not correctly order the whole result set. It also means you cannot call these queries using <literal>Query.scroll()</literal>."
msgstr ""
#. Tag: title
-#: query_hql.xml:424
#, no-c-format
msgid "The where clause"
msgstr ""
#. Tag: para
-#: query_hql.xml:426
#, no-c-format
msgid "The <literal>where</literal> clause allows you to refine the list of instances returned. If no alias exists, you can refer to properties by name:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:431
-#, no-c-format
-msgid "<![CDATA[from Cat where name='Fritz']]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:433
#, no-c-format
msgid "If there is an alias, use a qualified property name:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:437
-#, no-c-format
-msgid "<![CDATA[from Cat as cat where cat.name='Fritz']]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:439
#, no-c-format
msgid "This returns instances of <literal>Cat</literal> named 'Fritz'."
msgstr ""
#. Tag: para
-#: query_hql.xml:443
#, no-c-format
-msgid ""
- "The following query: <programlisting><![CDATA[select foo\n"
- "from Foo foo, Bar bar\n"
- "where foo.startDate = bar.date]]></programlisting> returns all instances of <literal>Foo</literal> with an instance of <literal>bar</literal> with a <literal>date</literal> property equal to the <literal>startDate</literal> property of the <literal>Foo</literal>. Compound path expressions make the <literal>where</literal> clause extremely powerful. Consider the following:"
+msgid "The following query:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:454
+#. Tag: para
#, no-c-format
-msgid "<![CDATA[from Cat cat where cat.mate.name is not null]]>"
+msgid "returns all instances of <literal>Foo</literal> with an instance of <literal>bar</literal> with a <literal>date</literal> property equal to the <literal>startDate</literal> property of the <literal>Foo</literal>. Compound path expressions make the <literal>where</literal> clause extremely powerful. Consider the following:"
msgstr ""
#. Tag: para
-#: query_hql.xml:456
#, no-c-format
msgid "This query translates to an SQL query with a table (inner) join. For example:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:461
-#, no-c-format
-msgid ""
- "<![CDATA[from Foo foo\n"
- "where foo.bar.baz.customer.address.city is not null]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:463
#, no-c-format
msgid "would result in a query that would require four table joins in SQL."
msgstr ""
#. Tag: para
-#: query_hql.xml:467
#, no-c-format
msgid "The <literal>=</literal> operator can be used to compare not only properties, but also instances:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:472
-#, no-c-format
-msgid "<![CDATA[from Cat cat, Cat rival where cat.mate = rival.mate]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:474
-#, no-c-format
-msgid ""
- "<![CDATA[select cat, mate\n"
- "from Cat cat, Cat mate\n"
- "where cat.mate = mate]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:476
#, no-c-format
-msgid "The special property (lowercase) <literal>id</literal> can be used to reference the unique identifier of an object. See <xref linkend=\"queryhql-identifier-property\"/> for more information."
+msgid "The special property (lowercase) <literal>id</literal> can be used to reference the unique identifier of an object. See <xref linkend=\"queryhql-identifier-property\" /> for more information."
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:482
-#, no-c-format
-msgid ""
- "<![CDATA[from Cat as cat where cat.id = 123\n"
- "\n"
- "from Cat as cat where cat.mate.id = 69]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:484
#, no-c-format
msgid "The second query is efficient and does not require a table join."
msgstr ""
#. Tag: para
-#: query_hql.xml:488
#, no-c-format
msgid "Properties of composite identifiers can also be used. Consider the following example where <literal>Person</literal> has composite identifiers consisting of <literal>country</literal> and <literal>medicareNumber</literal>:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:494
-#, no-c-format
-msgid ""
- "<![CDATA[from bank.Person person\n"
- "where person.id.country = 'AU'\n"
- " and person.id.medicareNumber = 123456]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:496
-#, no-c-format
-msgid ""
- "<![CDATA[from bank.Account account\n"
- "where account.owner.id.country = 'AU'\n"
- " and account.owner.id.medicareNumber = 123456]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:498
#, no-c-format
msgid "Once again, the second query does not require a table join."
msgstr ""
#. Tag: para
-#: query_hql.xml:502
#, no-c-format
-msgid "See <xref linkend=\"queryhql-identifier-property\"/> for more information regarding referencing identifier properties)"
+msgid "See <xref linkend=\"queryhql-identifier-property\" /> for more information regarding referencing identifier properties)"
msgstr ""
#. Tag: para
-#: query_hql.xml:507
#, no-c-format
msgid "The special property <literal>class</literal> accesses the discriminator value of an instance in the case of polymorphic persistence. A Java class name embedded in the where clause will be translated to its discriminator value."
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:513
-#, no-c-format
-msgid "<![CDATA[from Cat cat where cat.class = DomesticCat]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:515
#, no-c-format
-msgid "You can also use components or composite user types, or properties of said component types. See <xref linkend=\"queryhql-components\"/> for more information."
+msgid "You can also use components or composite user types, or properties of said component types. See <xref linkend=\"queryhql-components\" /> for more information."
msgstr ""
#. Tag: para
-#: query_hql.xml:520
#, no-c-format
msgid "An \"any\" type has the special properties <literal>id</literal> and <literal>class</literal> that allows you to express a join in the following way (where <literal>AuditLog.item</literal> is a property mapped with <literal><any></literal>):"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:526
-#, no-c-format
-msgid ""
- "<![CDATA[from AuditLog log, Payment payment\n"
- "where log.item.class = 'Payment' and log.item.id = payment.id]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:528
#, no-c-format
msgid "The <literal>log.item.class</literal> and <literal>payment.class</literal> would refer to the values of completely different database columns in the above query."
msgstr ""
#. Tag: title
-#: query_hql.xml:536
#, no-c-format
msgid "Expressions"
msgstr ""
#. Tag: para
-#: query_hql.xml:538
#, no-c-format
msgid "Expressions used in the <literal>where</literal> clause include the following:"
msgstr ""
#. Tag: para
-#: query_hql.xml:545
#, no-c-format
msgid "mathematical operators: <literal>+, -, *, /</literal>"
msgstr ""
#. Tag: para
-#: query_hql.xml:550
#, no-c-format
msgid "binary comparison operators: <literal>=, >=, <=, <>, !=, like</literal>"
msgstr ""
#. Tag: para
-#: query_hql.xml:555
#, no-c-format
msgid "logical operations <literal>and, or, not</literal>"
msgstr ""
#. Tag: para
-#: query_hql.xml:560
#, no-c-format
msgid "Parentheses <literal>( )</literal> that indicates grouping"
msgstr ""
#. Tag: para
-#: query_hql.xml:565
#, no-c-format
msgid "<literal>in</literal>, <literal>not in</literal>, <literal>between</literal>, <literal>is null</literal>, <literal>is not null</literal>, <literal>is empty</literal>, <literal>is not empty</literal>, <literal>member of</literal> and <literal>not member of</literal>"
msgstr ""
#. Tag: para
-#: query_hql.xml:578
#, no-c-format
msgid "\"Simple\" case, <literal>case ... when ... then ... else ... end</literal>, and \"searched\" case, <literal>case when ... then ... else ... end</literal>"
msgstr ""
#. Tag: para
-#: query_hql.xml:584
#, no-c-format
msgid "string concatenation <literal>...||...</literal> or <literal>concat(...,...)</literal>"
msgstr ""
#. Tag: para
-#: query_hql.xml:589
#, no-c-format
msgid "<literal>current_date()</literal>, <literal>current_time()</literal>, and <literal>current_timestamp()</literal>"
msgstr ""
#. Tag: para
-#: query_hql.xml:595
#, no-c-format
msgid "<literal>second(...)</literal>, <literal>minute(...)</literal>, <literal>hour(...)</literal>, <literal>day(...)</literal>, <literal>month(...)</literal>, and <literal>year(...)</literal>"
msgstr ""
#. Tag: para
-#: query_hql.xml:602
#, no-c-format
msgid "Any function or operator defined by EJB-QL 3.0: <literal>substring(), trim(), lower(), upper(), length(), locate(), abs(), sqrt(), bit_length(), mod()</literal>"
msgstr ""
#. Tag: para
-#: query_hql.xml:608
#, no-c-format
msgid "<literal>coalesce()</literal> and <literal>nullif()</literal>"
msgstr ""
#. Tag: para
-#: query_hql.xml:613
#, no-c-format
msgid "<literal>str()</literal> for converting numeric or temporal values to a readable string"
msgstr ""
#. Tag: para
-#: query_hql.xml:619
#, no-c-format
msgid "<literal>cast(... as ...)</literal>, where the second argument is the name of a Hibernate type, and <literal>extract(... from ...)</literal> if ANSI <literal>cast()</literal> and <literal>extract()</literal> is supported by the underlying database"
msgstr ""
#. Tag: para
-#: query_hql.xml:627
#, no-c-format
msgid "the HQL <literal>index()</literal> function, that applies to aliases of a joined indexed collection"
msgstr ""
#. Tag: para
-#: query_hql.xml:633
#, no-c-format
msgid "HQL functions that take collection-valued path expressions: <literal>size(), minelement(), maxelement(), minindex(), maxindex()</literal>, along with the special <literal>elements()</literal> and <literal>indices</literal> functions that can be quantified using <literal>some, all, exists, any, in</literal>."
msgstr ""
#. Tag: para
-#: query_hql.xml:641
#, no-c-format
msgid "Any database-supported SQL scalar function like <literal>sign()</literal>, <literal>trunc()</literal>, <literal>rtrim()</literal>, and <literal>sin()</literal>"
msgstr ""
#. Tag: para
-#: query_hql.xml:647
#, no-c-format
msgid "JDBC-style positional parameters <literal>?</literal>"
msgstr ""
#. Tag: para
-#: query_hql.xml:652
#, no-c-format
msgid "named parameters <literal>:name</literal>, <literal>:start_date</literal>, and <literal>:x1</literal>"
msgstr ""
#. Tag: para
-#: query_hql.xml:657
#, no-c-format
msgid "SQL literals <literal>'foo'</literal>, <literal>69</literal>, <literal>6.66E+2</literal>, <literal>'1970-01-01 10:00:01.0'</literal>"
msgstr ""
#. Tag: para
-#: query_hql.xml:663
#, no-c-format
msgid "Java <literal>public static final</literal> constants <literal>eg.Color.TABBY</literal>"
msgstr ""
#. Tag: para
-#: query_hql.xml:669
#, no-c-format
msgid "<literal>in</literal> and <literal>between</literal> can be used as follows:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:673
-#, no-c-format
-msgid "<![CDATA[from DomesticCat cat where cat.name between 'A' and 'B']]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:675
-#, no-c-format
-msgid "<![CDATA[from DomesticCat cat where cat.name in ( 'Foo', 'Bar', 'Baz' )]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:677
#, no-c-format
msgid "The negated forms can be written as follows:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:681
-#, no-c-format
-msgid "<![CDATA[from DomesticCat cat where cat.name not between 'A' and 'B']]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:683
-#, no-c-format
-msgid "<![CDATA[from DomesticCat cat where cat.name not in ( 'Foo', 'Bar', 'Baz' )]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:685
#, no-c-format
msgid "Similarly, <literal>is null</literal> and <literal>is not null</literal> can be used to test for null values."
msgstr ""
#. Tag: para
-#: query_hql.xml:690
#, no-c-format
msgid "Booleans can be easily used in expressions by declaring HQL query substitutions in Hibernate configuration:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:695
-#, no-c-format
-msgid "<![CDATA[<property name=\"hibernate.query.substitutions\">true 1, false 0</property>]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:697
#, no-c-format
msgid "This will replace the keywords <literal>true</literal> and <literal>false</literal> with the literals <literal>1</literal> and <literal>0</literal> in the translated SQL from this HQL:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:702
-#, no-c-format
-msgid "<![CDATA[from Cat cat where cat.alive = true]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:704
#, no-c-format
msgid "You can test the size of a collection with the special property <literal>size</literal> or the special <literal>size()</literal> function."
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:709
-#, no-c-format
-msgid "<![CDATA[from Cat cat where cat.kittens.size > 0]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:711
-#, no-c-format
-msgid "<![CDATA[from Cat cat where size(cat.kittens) > 0]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:713
#, no-c-format
msgid "For indexed collections, you can refer to the minimum and maximum indices using <literal>minindex</literal> and <literal>maxindex</literal> functions. Similarly, you can refer to the minimum and maximum elements of a collection of basic type using the <literal>minelement</literal> and <literal>maxelement</literal> functions. For example:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:721
-#, no-c-format
-msgid "<![CDATA[from Calendar cal where maxelement(cal.holidays) > current_date]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:723
-#, no-c-format
-msgid "<![CDATA[from Order order where maxindex(order.items) > 100]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:725
-#, no-c-format
-msgid "<![CDATA[from Order order where minelement(order.items) > 10000]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:727
#, no-c-format
msgid "The SQL functions <literal>any, some, all, exists, in</literal> are supported when passed the element or index set of a collection (<literal>elements</literal> and <literal>indices</literal> functions) or the result of a subquery (see below):"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:733
-#, no-c-format
-msgid ""
- "<![CDATA[select mother from Cat as mother, Cat as kit\n"
- "where kit in elements(foo.kittens)]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:735
-#, no-c-format
-msgid ""
- "<![CDATA[select p from NameList list, Person p\n"
- "where p.name = some elements(list.names)]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:737
-#, no-c-format
-msgid "<![CDATA[from Cat cat where exists elements(cat.kittens)]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:739
-#, no-c-format
-msgid "<![CDATA[from Player p where 3 > all elements(p.scores)]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:741
-#, no-c-format
-msgid "<![CDATA[from Show show where 'fizard' in indices(show.acts)]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:743
#, no-c-format
msgid "Note that these constructs - <literal>size</literal>, <literal>elements</literal>, <literal>indices</literal>, <literal>minindex</literal>, <literal>maxindex</literal>, <literal>minelement</literal>, <literal>maxelement</literal> - can only be used in the where clause in Hibernate3."
msgstr ""
#. Tag: para
-#: query_hql.xml:750
#, no-c-format
msgid "Elements of indexed collections (arrays, lists, and maps) can be referred to by index in a where clause only:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:755
-#, no-c-format
-msgid "<![CDATA[from Order order where order.items[0].id = 1234]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:757
-#, no-c-format
-msgid ""
- "<![CDATA[select person from Person person, Calendar calendar\n"
- "where calendar.holidays['national day'] = person.birthDay\n"
- " and person.nationality.calendar = calendar]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:759
-#, no-c-format
-msgid ""
- "<![CDATA[select item from Item item, Order order\n"
- "where order.items[ order.deliveredItemIndices[0] ] = item and order.id = 11]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:761
-#, no-c-format
-msgid ""
- "<![CDATA[select item from Item item, Order order\n"
- "where order.items[ maxindex(order.items) ] = item and order.id = 11]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:763
#, no-c-format
msgid "The expression inside <literal>[]</literal> can even be an arithmetic expression:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:767
-#, no-c-format
-msgid ""
- "<![CDATA[select item from Item item, Order order\n"
- "where order.items[ size(order.items) - 1 ] = item]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:769
#, no-c-format
msgid "HQL also provides the built-in <literal>index()</literal> function for elements of a one-to-many association or collection of values."
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:774
-#, no-c-format
-msgid ""
- "<![CDATA[select item, index(item) from Order order\n"
- " join order.items item\n"
- "where index(item) < 5]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:776
#, no-c-format
msgid "Scalar SQL functions supported by the underlying database can be used:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:780
-#, no-c-format
-msgid "<![CDATA[from DomesticCat cat where upper(cat.name) like 'FRI%']]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:782
#, no-c-format
msgid "Consider how much longer and less readable the following query would be in SQL:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:787
-#, no-c-format
-msgid ""
- "<![CDATA[select cust\n"
- "from Product prod,\n"
- " Store store\n"
- " inner join store.customers cust\n"
- "where prod.name = 'widget'\n"
- " and store.location.name in ( 'Melbourne', 'Sydney' )\n"
- " and prod = all elements(cust.currentOrder.lineItems)]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:789
#, no-c-format
msgid "<emphasis>Hint:</emphasis> something like"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:793
-#, no-c-format
-msgid ""
- "<![CDATA[SELECT cust.name, cust.address, cust.phone, cust.id, cust.current_order\n"
- "FROM customers cust,\n"
- " stores store,\n"
- " locations loc,\n"
- " store_customers sc,\n"
- " product prod\n"
- "WHERE prod.name = 'widget'\n"
- " AND store.loc_id = loc.id\n"
- " AND loc.name IN ( 'Melbourne', 'Sydney' )\n"
- " AND sc.store_id = store.id\n"
- " AND sc.cust_id = cust.id\n"
- " AND prod.id = ALL(\n"
- " SELECT item.prod_id\n"
- " FROM line_items item, orders o\n"
- " WHERE item.order_id = o.id\n"
- " AND cust.current_order = o.id\n"
- " )]]>"
-msgstr ""
-
#. Tag: title
-#: query_hql.xml:798
#, no-c-format
msgid "The order by clause"
msgstr ""
#. Tag: para
-#: query_hql.xml:800
#, no-c-format
msgid "The list returned by a query can be ordered by any property of a returned class or components:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:804
-#, no-c-format
-msgid ""
- "<![CDATA[from DomesticCat cat\n"
- "order by cat.name asc, cat.weight desc, cat.birthdate]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:806
#, no-c-format
msgid "The optional <literal>asc</literal> or <literal>desc</literal> indicate ascending or descending order respectively."
msgstr ""
#. Tag: title
-#: query_hql.xml:813
#, no-c-format
msgid "The group by clause"
msgstr ""
#. Tag: para
-#: query_hql.xml:815
#, no-c-format
msgid "A query that returns aggregate values can be grouped by any property of a returned class or components:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:819
-#, no-c-format
-msgid ""
- "<![CDATA[select cat.color, sum(cat.weight), count(cat)\n"
- "from Cat cat\n"
- "group by cat.color]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:821
-#, no-c-format
-msgid ""
- "<![CDATA[select foo.id, avg(name), max(name)\n"
- "from Foo foo join foo.names name\n"
- "group by foo.id]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:823
#, no-c-format
msgid "A <literal>having</literal> clause is also allowed."
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:827
-#, no-c-format
-msgid ""
- "<![CDATA[select cat.color, sum(cat.weight), count(cat)\n"
- "from Cat cat\n"
- "group by cat.color\n"
- "having cat.color in (eg.Color.TABBY, eg.Color.BLACK)]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:829
#, no-c-format
msgid "SQL functions and aggregate functions are allowed in the <literal>having</literal> and <literal>order by</literal> clauses if they are supported by the underlying database (i.e., not in MySQL)."
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:835
-#, no-c-format
-msgid ""
- "<![CDATA[select cat\n"
- "from Cat cat\n"
- " join cat.kittens kitten\n"
- "group by cat.id, cat.name, cat.other, cat.properties\n"
- "having avg(kitten.weight) > 100\n"
- "order by count(kitten) asc, sum(kitten.weight) desc]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:837
#, no-c-format
msgid "Neither the <literal>group by</literal> clause nor the <literal>order by</literal> clause can contain arithmetic expressions. Hibernate also does not currently expand a grouped entity, so you cannot write <literal>group by cat</literal> if all properties of <literal>cat</literal> are non-aggregated. You have to list all non-aggregated properties explicitly."
msgstr ""
#. Tag: title
-#: query_hql.xml:849
#, no-c-format
msgid "Subqueries"
msgstr ""
#. Tag: para
-#: query_hql.xml:851
#, no-c-format
msgid "For databases that support subselects, Hibernate supports subqueries within queries. A subquery must be surrounded by parentheses (often by an SQL aggregate function call). Even correlated subqueries (subqueries that refer to an alias in the outer query) are allowed."
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:857
-#, no-c-format
-msgid ""
- "<![CDATA[from Cat as fatcat\n"
- "where fatcat.weight > (\n"
- " select avg(cat.weight) from DomesticCat cat\n"
- ")]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:859
-#, no-c-format
-msgid ""
- "<![CDATA[from DomesticCat as cat\n"
- "where cat.name = some (\n"
- " select name.nickName from Name as name\n"
- ")]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:861
-#, no-c-format
-msgid ""
- "<![CDATA[from Cat as cat\n"
- "where not exists (\n"
- " from Cat as mate where mate.mate = cat\n"
- ")]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:863
-#, no-c-format
-msgid ""
- "<![CDATA[from DomesticCat as cat\n"
- "where cat.name not in (\n"
- " select name.nickName from Name as name\n"
- ")]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:865
-#, no-c-format
-msgid ""
- "<![CDATA[select cat.id, (select max(kit.weight) from cat.kitten kit)\n"
- "from Cat as cat]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:867
#, no-c-format
msgid "Note that HQL subqueries can occur only in the select or where clauses."
msgstr ""
#. Tag: para
-#: query_hql.xml:871
#, no-c-format
-msgid "Note that subqueries can also utilize <literal>row value constructor</literal> syntax. See <xref linkend=\"queryhql-tuple\"/> for more information."
+msgid "Note that subqueries can also utilize <literal>row value constructor</literal> syntax. See <xref linkend=\"queryhql-tuple\" /> for more information."
msgstr ""
#. Tag: title
-#: query_hql.xml:879
#, no-c-format
msgid "HQL examples"
msgstr ""
#. Tag: para
-#: query_hql.xml:881
#, no-c-format
msgid "Hibernate queries can be quite powerful and complex. In fact, the power of the query language is one of Hibernate's main strengths. The following example queries are similar to queries that have been used on recent projects. Please note that most queries you will write will be much simpler than the following examples."
msgstr ""
#. Tag: para
-#: query_hql.xml:887
#, no-c-format
msgid "The following query returns the order id, number of items, the given minimum total value and the total value of the order for all unpaid orders for a particular customer. The results are ordered by total value. In determining the prices, it uses the current catalog. The resulting SQL query, against the <literal>ORDER</literal>, <literal>ORDER_LINE</literal>, <literal>PRODUCT</literal>, <literal>CATALOG</literal> and <literal>PRICE</literal> tables has four inner joins and an (uncorrelated) subselect."
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:896
-#, no-c-format
-msgid ""
- "<![CDATA[select order.id, sum(price.amount), count(item)\n"
- "from Order as order\n"
- " join order.lineItems as item\n"
- " join item.product as product,\n"
- " Catalog as catalog\n"
- " join catalog.prices as price\n"
- "where order.paid = false\n"
- " and order.customer = :customer\n"
- " and price.product = product\n"
- " and catalog.effectiveDate < sysdate\n"
- " and catalog.effectiveDate >= all (\n"
- " select cat.effectiveDate\n"
- " from Catalog as cat\n"
- " where cat.effectiveDate < sysdate\n"
- " )\n"
- "group by order\n"
- "having sum(price.amount) > :minAmount\n"
- "order by sum(price.amount) desc]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:898
#, no-c-format
msgid "What a monster! Actually, in real life, I'm not very keen on subqueries, so my query was really more like this:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:903
-#, no-c-format
-msgid ""
- "<![CDATA[select order.id, sum(price.amount), count(item)\n"
- "from Order as order\n"
- " join order.lineItems as item\n"
- " join item.product as product,\n"
- " Catalog as catalog\n"
- " join catalog.prices as price\n"
- "where order.paid = false\n"
- " and order.customer = :customer\n"
- " and price.product = product\n"
- " and catalog = :currentCatalog\n"
- "group by order\n"
- "having sum(price.amount) > :minAmount\n"
- "order by sum(price.amount) desc]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:905
#, no-c-format
msgid "The next query counts the number of payments in each status, excluding all payments in the <literal>AWAITING_APPROVAL</literal> status where the most recent status change was made by the current user. It translates to an SQL query with two inner joins and a correlated subselect against the <literal>PAYMENT</literal>, <literal>PAYMENT_STATUS</literal> and <literal>PAYMENT_STATUS_CHANGE</literal> tables."
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:913
-#, no-c-format
-msgid ""
- "<![CDATA[select count(payment), status.name\n"
- "from Payment as payment\n"
- " join payment.currentStatus as status\n"
- " join payment.statusChanges as statusChange\n"
- "where payment.status.name <> PaymentStatus.AWAITING_APPROVAL\n"
- " or (\n"
- " statusChange.timeStamp = (\n"
- " select max(change.timeStamp)\n"
- " from PaymentStatusChange change\n"
- " where change.payment = payment\n"
- " )\n"
- " and statusChange.user <> :currentUser\n"
- " )\n"
- "group by status.name, status.sortOrder\n"
- "order by status.sortOrder]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:915
#, no-c-format
msgid "If the <literal>statusChanges</literal> collection was mapped as a list, instead of a set, the query would have been much simpler to write."
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:920
-#, no-c-format
-msgid ""
- "<![CDATA[select count(payment), status.name\n"
- "from Payment as payment\n"
- " join payment.currentStatus as status\n"
- "where payment.status.name <> PaymentStatus.AWAITING_APPROVAL\n"
- " or payment.statusChanges[ maxIndex(payment.statusChanges) ].user <> :currentUser\n"
- "group by status.name, status.sortOrder\n"
- "order by status.sortOrder]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:922
#, no-c-format
msgid "The next query uses the MS SQL Server <literal>isNull()</literal> function to return all the accounts and unpaid payments for the organization to which the current user belongs. It translates to an SQL query with three inner joins, an outer join and a subselect against the <literal>ACCOUNT</literal>, <literal>PAYMENT</literal>, <literal>PAYMENT_STATUS</literal>, <literal>ACCOUNT_TYPE</literal>, <literal>ORGANIZATION</literal> and <literal>ORG_USER</literal> tables."
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:931
-#, no-c-format
-msgid ""
- "<![CDATA[select account, payment\n"
- "from Account as account\n"
- " left outer join account.payments as payment\n"
- "where :currentUser in elements(account.holder.users)\n"
- " and PaymentStatus.UNPAID = isNull(payment.currentStatus.name, PaymentStatus.UNPAID)\n"
- "order by account.type.sortOrder, account.accountNumber, payment.dueDate]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:933
#, no-c-format
msgid "For some databases, we would need to do away with the (correlated) subselect."
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:937
-#, no-c-format
-msgid ""
- "<![CDATA[select account, payment\n"
- "from Account as account\n"
- " join account.holder.users as user\n"
- " left outer join account.payments as payment\n"
- "where :currentUser = user\n"
- " and PaymentStatus.UNPAID = isNull(payment.currentStatus.name, PaymentStatus.UNPAID)\n"
- "order by account.type.sortOrder, account.accountNumber, payment.dueDate]]>"
-msgstr ""
-
#. Tag: title
-#: query_hql.xml:942
#, no-c-format
msgid "Bulk update and delete"
msgstr ""
#. Tag: para
-#: query_hql.xml:944
#, no-c-format
-msgid "HQL now supports <literal>update</literal>, <literal>delete</literal> and <literal>insert ... select ...</literal> statements. See <xref linkend=\"batch-direct\"/> for more information."
+msgid "HQL now supports <literal>update</literal>, <literal>delete</literal> and <literal>insert ... select ...</literal> statements. See <xref linkend=\"batch-direct\" /> for more information."
msgstr ""
#. Tag: title
-#: query_hql.xml:952
#, no-c-format
msgid "Tips & Tricks"
msgstr ""
#. Tag: para
-#: query_hql.xml:954
#, no-c-format
msgid "You can count the number of query results without returning them:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:958
-#, no-c-format
-msgid "<![CDATA[( (Integer) session.createQuery(\"select count(*) from ....\").iterate().next() ).intValue()]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:960
#, no-c-format
msgid "To order a result by the size of a collection, use the following query:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:964
-#, no-c-format
-msgid ""
- "<![CDATA[select usr.id, usr.name\n"
- "from User as usr\n"
- " left join usr.messages as msg\n"
- "group by usr.id, usr.name\n"
- "order by count(msg)]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:966
#, no-c-format
msgid "If your database supports subselects, you can place a condition upon selection size in the where clause of your query:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:971
-#, no-c-format
-msgid "<![CDATA[from User usr where size(usr.messages) >= 1]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:973
#, no-c-format
msgid "If your database does not support subselects, use the following query:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:977
-#, no-c-format
-msgid ""
- "<![CDATA[select usr.id, usr.name\n"
- "from User usr.name\n"
- " join usr.messages msg\n"
- "group by usr.id, usr.name\n"
- "having count(msg) >= 1]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:980
#, no-c-format
msgid "As this solution cannot return a <literal>User</literal> with zero messages because of the inner join, the following form is also useful:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:985
-#, no-c-format
-msgid ""
- "<![CDATA[select usr.id, usr.name\n"
- "from User as usr\n"
- " left join usr.messages as msg\n"
- "group by usr.id, usr.name\n"
- "having count(msg) = 0]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:987
#, no-c-format
msgid "Properties of a JavaBean can be bound to named query parameters:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:991
-#, no-c-format
-msgid ""
- "<![CDATA[Query q = s.createQuery(\"from foo Foo as foo where foo.name=:name and foo.size=:size\");\n"
- "q.setProperties(fooBean); // fooBean has getName() and getSize()\n"
- "List foos = q.list();]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:993
#, no-c-format
msgid "Collections are pageable by using the <literal>Query</literal> interface with a filter:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:997
-#, no-c-format
-msgid ""
- "<![CDATA[Query q = s.createFilter( collection, \"\" ); // the trivial filter\n"
- "q.setMaxResults(PAGE_SIZE);\n"
- "q.setFirstResult(PAGE_SIZE * pageNumber);\n"
- "List page = q.list();]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:999
#, no-c-format
msgid "Collection elements can be ordered or grouped using a query filter:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:1003
-#, no-c-format
-msgid ""
- "<![CDATA[Collection orderedCollection = s.filter( collection, \"order by this.amount\" );\n"
- "Collection counts = s.filter( collection, \"select this.type, count(this) group by this.type\" );]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:1005
#, no-c-format
msgid "You can find the size of a collection without initializing it:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:1009
-#, no-c-format
-msgid "<![CDATA[( (Integer) session.createQuery(\"select count(*) from ....\").iterate().next() ).intValue();]]>"
-msgstr ""
-
#. Tag: title
-#: query_hql.xml:1014
#, no-c-format
msgid "Components"
msgstr ""
#. Tag: para
-#: query_hql.xml:1016
#, no-c-format
msgid "Components can be used similarly to the simple value types that are used in HQL queries. They can appear in the <literal>select</literal> clause as follows:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:1021 query_hql.xml:1067
-#, no-c-format
-msgid "<![CDATA[select p.name from Person p]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:1022
-#, no-c-format
-msgid "<![CDATA[select p.name.first from Person p]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:1024
#, no-c-format
msgid "where the Person's name property is a component. Components can also be used in the <literal>where</literal> clause:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:1029
-#, no-c-format
-msgid "<![CDATA[from Person p where p.name = :name]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:1030
-#, no-c-format
-msgid "<![CDATA[from Person p where p.name.first = :firstName]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:1032
#, no-c-format
msgid "Components can also be used in the <literal>order by</literal> clause:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:1036
-#, no-c-format
-msgid "<![CDATA[from Person p order by p.name]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_hql.xml:1037
-#, no-c-format
-msgid "<![CDATA[from Person p order by p.name.first]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:1039
#, no-c-format
-msgid "Another common use of components is in <link linkend=\"queryhql-tuple\">row value constructors</link>."
+msgid "Another common use of components is in row value constructors (<xref linkend=\"queryhql-tuple\" />)."
msgstr ""
#. Tag: title
-#: query_hql.xml:1045
#, no-c-format
msgid "Row value constructor syntax"
msgstr ""
#. Tag: para
-#: query_hql.xml:1047
#, no-c-format
msgid "HQL supports the use of ANSI SQL <literal>row value constructor</literal> syntax, sometimes referred to AS <literal>tuple</literal> syntax, even though the underlying database may not support that notion. Here, we are generally referring to multi-valued comparisons, typically associated with components. Consider an entity Person which defines a name component:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:1054
-#, no-c-format
-msgid "<![CDATA[from Person p where p.name.first='John' and p.name.last='Jingleheimer-Schmidt']]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:1056
#, no-c-format
msgid "That is valid syntax although it is a little verbose. You can make this more concise by using <literal>row value constructor</literal> syntax:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:1061
-#, no-c-format
-msgid "<![CDATA[from Person p where p.name=('John', 'Jingleheimer-Schmidt')]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:1063
#, no-c-format
msgid "It can also be useful to specify this in the <literal>select</literal> clause:"
msgstr ""
#. Tag: para
-#: query_hql.xml:1069
#, no-c-format
msgid "Using <literal>row value constructor</literal> syntax can also be beneficial when using subqueries that need to compare against multiple values:"
msgstr ""
-#. Tag: programlisting
-#: query_hql.xml:1074
-#, no-c-format
-msgid ""
- "<![CDATA[from Cat as cat\n"
- "where not ( cat.name, cat.color ) in (\n"
- " select cat.name, cat.color from DomesticCat cat\n"
- ")]]>"
-msgstr ""
-
#. Tag: para
-#: query_hql.xml:1076
#, no-c-format
msgid "One thing to consider when deciding if you want to use this syntax, is that the query will be dependent upon the ordering of the component sub-properties in the metadata."
msgstr ""
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/query_sql.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/query_sql.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/query_sql.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,1112 +1,589 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-10 21:02+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:19\n"
+"PO-Revision-Date: 2010-01-08T04:07:19\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
-#: query_sql.xml:29
#, no-c-format
msgid "Native SQL"
msgstr ""
#. Tag: para
-#: query_sql.xml:31
#, no-c-format
msgid "You can also express queries in the native SQL dialect of your database. This is useful if you want to utilize database-specific features such as query hints or the <literal>CONNECT</literal> keyword in Oracle. It also provides a clean migration path from a direct SQL/JDBC based application to Hibernate."
msgstr ""
#. Tag: para
-#: query_sql.xml:37
#, no-c-format
msgid "Hibernate3 allows you to specify handwritten SQL, including stored procedures, for all create, update, delete, and load operations."
msgstr ""
#. Tag: title
-#: query_sql.xml:41
#, no-c-format
msgid "Using a <literal>SQLQuery</literal>"
msgstr ""
#. Tag: para
-#: query_sql.xml:43
#, no-c-format
msgid "Execution of native SQL queries is controlled via the <literal>SQLQuery</literal> interface, which is obtained by calling <literal>Session.createSQLQuery()</literal>. The following sections describe how to use this API for querying."
msgstr ""
#. Tag: title
-#: query_sql.xml:49
#, no-c-format
msgid "Scalar queries"
msgstr ""
#. Tag: para
-#: query_sql.xml:51
#, no-c-format
msgid "The most basic SQL query is to get a list of scalars (values)."
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:54
-#, no-c-format
-msgid ""
- "<![CDATA[sess.createSQLQuery(\"SELECT * FROM CATS\").list();\n"
- "sess.createSQLQuery(\"SELECT ID, NAME, BIRTHDATE FROM CATS\").list();\n"
- "]]>"
-msgstr ""
-
#. Tag: para
-#: query_sql.xml:56
#, no-c-format
msgid "These will return a List of Object arrays (Object[]) with scalar values for each column in the CATS table. Hibernate will use ResultSetMetadata to deduce the actual order and types of the returned scalar values."
msgstr ""
#. Tag: para
-#: query_sql.xml:61
#, no-c-format
msgid "To avoid the overhead of using <literal>ResultSetMetadata</literal>, or simply to be more explicit in what is returned, one can use <literal>addScalar()</literal>:"
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:65
-#, no-c-format
-msgid ""
- "<![CDATA[sess.createSQLQuery(\"SELECT * FROM CATS\")\n"
- " .addScalar(\"ID\", Hibernate.LONG)\n"
- " .addScalar(\"NAME\", Hibernate.STRING)\n"
- " .addScalar(\"BIRTHDATE\", Hibernate.DATE)\n"
- "]]>"
-msgstr ""
-
#. Tag: para
-#: query_sql.xml:67 query_sql.xml:113 query_sql.xml:198 query_sql.xml:349
#, no-c-format
msgid "This query specified:"
msgstr ""
#. Tag: para
-#: query_sql.xml:71 query_sql.xml:117 query_sql.xml:353
#, no-c-format
msgid "the SQL query string"
msgstr ""
#. Tag: para
-#: query_sql.xml:75
#, no-c-format
msgid "the columns and types to return"
msgstr ""
#. Tag: para
-#: query_sql.xml:79
#, no-c-format
msgid "This will return Object arrays, but now it will not use <literal>ResultSetMetadata</literal> but will instead explicitly get the ID, NAME and BIRTHDATE column as respectively a Long, String and a Short from the underlying resultset. This also means that only these three columns will be returned, even though the query is using <literal>*</literal> and could return more than the three listed columns."
msgstr ""
#. Tag: para
-#: query_sql.xml:87
#, no-c-format
msgid "It is possible to leave out the type information for all or some of the scalars."
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:90
-#, no-c-format
-msgid ""
- "<![CDATA[sess.createSQLQuery(\"SELECT * FROM CATS\")\n"
- " .addScalar(\"ID\", Hibernate.LONG)\n"
- " .addScalar(\"NAME\")\n"
- " .addScalar(\"BIRTHDATE\")\n"
- "]]>"
-msgstr ""
-
#. Tag: para
-#: query_sql.xml:92
#, no-c-format
msgid "This is essentially the same query as before, but now <literal>ResultSetMetaData</literal> is used to determine the type of NAME and BIRTHDATE, where as the type of ID is explicitly specified."
msgstr ""
#. Tag: para
-#: query_sql.xml:96
#, no-c-format
msgid "How the java.sql.Types returned from ResultSetMetaData is mapped to Hibernate types is controlled by the Dialect. If a specific type is not mapped, or does not result in the expected type, it is possible to customize it via calls to <literal>registerHibernateType</literal> in the Dialect."
msgstr ""
#. Tag: title
-#: query_sql.xml:104
#, no-c-format
msgid "Entity queries"
msgstr ""
#. Tag: para
-#: query_sql.xml:106
#, no-c-format
msgid "The above queries were all about returning scalar values, basically returning the \"raw\" values from the resultset. The following shows how to get entity objects from a native sql query via <literal>addEntity()</literal>."
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:111
-#, no-c-format
-msgid ""
- "<![CDATA[sess.createSQLQuery(\"SELECT * FROM CATS\").addEntity(Cat.class);\n"
- "sess.createSQLQuery(\"SELECT ID, NAME, BIRTHDATE FROM CATS\").addEntity(Cat.class);\n"
- "]]>"
-msgstr ""
-
#. Tag: para
-#: query_sql.xml:121
#, no-c-format
msgid "the entity returned by the query"
msgstr ""
#. Tag: para
-#: query_sql.xml:125
#, no-c-format
msgid "Assuming that Cat is mapped as a class with the columns ID, NAME and BIRTHDATE the above queries will both return a List where each element is a Cat entity."
msgstr ""
#. Tag: para
-#: query_sql.xml:129
#, no-c-format
msgid "If the entity is mapped with a <literal>many-to-one</literal> to another entity it is required to also return this when performing the native query, otherwise a database specific \"column not found\" error will occur. The additional columns will automatically be returned when using the * notation, but we prefer to be explicit as in the following example for a <literal>many-to-one</literal> to a <literal>Dog</literal>:"
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:137
-#, no-c-format
-msgid ""
- "<![CDATA[sess.createSQLQuery(\"SELECT ID, NAME, BIRTHDATE, DOG_ID FROM CATS\").addEntity(Cat.class);\n"
- "]]>"
-msgstr ""
-
#. Tag: para
-#: query_sql.xml:139
#, no-c-format
msgid "This will allow cat.getDog() to function properly."
msgstr ""
#. Tag: title
-#: query_sql.xml:143
#, no-c-format
msgid "Handling associations and collections"
msgstr ""
#. Tag: para
-#: query_sql.xml:145
#, no-c-format
msgid "It is possible to eagerly join in the <literal>Dog</literal> to avoid the possible extra roundtrip for initializing the proxy. This is done via the <literal>addJoin()</literal> method, which allows you to join in an association or collection."
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:150
-#, no-c-format
-msgid ""
- "<![CDATA[sess.createSQLQuery(\"SELECT c.ID, NAME, BIRTHDATE, DOG_ID, D_ID, D_NAME FROM CATS c, DOGS d WHERE c.DOG_ID = d.D_ID\")\n"
- " .addEntity(\"cat\", Cat.class)\n"
- " .addJoin(\"cat.dog\");\n"
- "]]>"
-msgstr ""
-
#. Tag: para
-#: query_sql.xml:152
#, no-c-format
msgid "In this example, the returned <literal>Cat</literal>'s will have their <literal>dog</literal> property fully initialized without any extra roundtrip to the database. Notice that you added an alias name (\"cat\") to be able to specify the target property path of the join. It is possible to do the same eager joining for collections, e.g. if the <literal>Cat</literal> had a one-to-many to <literal>Dog</literal> instead."
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:160
-#, no-c-format
-msgid ""
- "<![CDATA[sess.createSQLQuery(\"SELECT ID, NAME, BIRTHDATE, D_ID, D_NAME, CAT_ID FROM CATS c, DOGS d WHERE c.ID = d.CAT_ID\")\n"
- " .addEntity(\"cat\", Cat.class)\n"
- " .addJoin(\"cat.dogs\");\n"
- "]]>"
-msgstr ""
-
#. Tag: para
-#: query_sql.xml:162
#, no-c-format
msgid "At this stage you are reaching the limits of what is possible with native queries, without starting to enhance the sql queries to make them usable in Hibernate. Problems can arise when returning multiple entities of the same type or when the default alias/column names are not enough."
msgstr ""
#. Tag: title
-#: query_sql.xml:170
#, no-c-format
msgid "Returning multiple entities"
msgstr ""
#. Tag: para
-#: query_sql.xml:172
#, no-c-format
msgid "Until now, the result set column names are assumed to be the same as the column names specified in the mapping document. This can be problematic for SQL queries that join multiple tables, since the same column names can appear in more than one table."
msgstr ""
#. Tag: para
-#: query_sql.xml:177
#, no-c-format
msgid "Column alias injection is needed in the following query (which most likely will fail):"
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:180
-#, no-c-format
-msgid ""
- "<![CDATA[sess.createSQLQuery(\"SELECT c.*, m.* FROM CATS c, CATS m WHERE c.MOTHER_ID = c.ID\")\n"
- " .addEntity(\"cat\", Cat.class)\n"
- " .addEntity(\"mother\", Cat.class)\n"
- "]]>"
-msgstr ""
-
#. Tag: para
-#: query_sql.xml:184
#, no-c-format
msgid "The query was intended to return two Cat instances per row: a cat and its mother. The query will, however, fail because there is a conflict of names; the instances are mapped to the same column names. Also, on some databases the returned column aliases will most likely be on the form \"c.ID\", \"c.NAME\", etc. which are not equal to the columns specified in the mappings (\"ID\" and \"NAME\")."
msgstr ""
#. Tag: para
-#: query_sql.xml:193
#, no-c-format
msgid "The following form is not vulnerable to column name duplication:"
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:196
-#, no-c-format
-msgid ""
- "<![CDATA[sess.createSQLQuery(\"SELECT {cat.*}, {mother.*} FROM CATS c, CATS m WHERE c.MOTHER_ID = c.ID\")\n"
- " .addEntity(\"cat\", Cat.class)\n"
- " .addEntity(\"mother\", Cat.class)\n"
- "]]>"
-msgstr ""
-
#. Tag: para
-#: query_sql.xml:202
#, no-c-format
msgid "the SQL query string, with placeholders for Hibernate to inject column aliases"
msgstr ""
#. Tag: para
-#: query_sql.xml:207
#, no-c-format
msgid "the entities returned by the query"
msgstr ""
#. Tag: para
-#: query_sql.xml:211
#, no-c-format
msgid "The {cat.*} and {mother.*} notation used above is a shorthand for \"all properties\". Alternatively, you can list the columns explicitly, but even in this case Hibernate injects the SQL column aliases for each property. The placeholder for a column alias is just the property name qualified by the table alias. In the following example, you retrieve Cats and their mothers from a different table (cat_log) to the one declared in the mapping metadata. You can even use the property aliases in the where clause."
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:220
-#, no-c-format
-msgid ""
- "<![CDATA[String sql = \"SELECT ID as {c.id}, NAME as {c.name}, \" + \n"
- " \"BIRTHDATE as {c.birthDate}, MOTHER_ID as {c.mother}, {mother.*} \" +\n"
- " \"FROM CAT_LOG c, CAT_LOG m WHERE {c.mother} = c.ID\";\n"
- "\n"
- "List loggedCats = sess.createSQLQuery(sql)\n"
- " .addEntity(\"cat\", Cat.class)\n"
- " .addEntity(\"mother\", Cat.class).list()\n"
- "]]>"
-msgstr ""
-
#. Tag: title
-#: query_sql.xml:223
#, no-c-format
msgid "Alias and property references"
msgstr ""
#. Tag: para
-#: query_sql.xml:225
#, no-c-format
msgid "In most cases the above alias injection is needed. For queries relating to more complex mappings, like composite properties, inheritance discriminators, collections etc., you can use specific aliases that allow Hibernate to inject the proper aliases."
msgstr ""
#. Tag: para
-#: query_sql.xml:230
#, no-c-format
msgid "The following table shows the different ways you can use the alias injection. Please note that the alias names in the result are simply examples; each alias will have a unique and probably different name when used."
msgstr ""
#. Tag: title
-#: query_sql.xml:236
#, no-c-format
msgid "Alias injection names"
msgstr ""
#. Tag: entry
-#: query_sql.xml:247
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: entry
-#: query_sql.xml:249
#, no-c-format
msgid "Syntax"
msgstr ""
#. Tag: entry
-#: query_sql.xml:251
#, no-c-format
msgid "Example"
msgstr ""
#. Tag: entry
-#: query_sql.xml:257
#, no-c-format
msgid "A simple property"
msgstr ""
-#. Tag: literal
-#: query_sql.xml:259
+#. Tag: entry
#, no-c-format
-msgid "{[aliasname].[propertyname]"
+msgid "<literal>{[aliasname].[propertyname]</literal>"
msgstr ""
-#. Tag: literal
-#: query_sql.xml:261
+#. Tag: entry
#, no-c-format
-msgid "A_NAME as {item.name}"
+msgid "<literal>A_NAME as {item.name}</literal>"
msgstr ""
#. Tag: entry
-#: query_sql.xml:265
#, no-c-format
msgid "A composite property"
msgstr ""
-#. Tag: literal
-#: query_sql.xml:267
+#. Tag: entry
#, no-c-format
-msgid "{[aliasname].[componentname].[propertyname]}"
+msgid "<literal>{[aliasname].[componentname].[propertyname]}</literal>"
msgstr ""
-#. Tag: literal
-#: query_sql.xml:269
+#. Tag: entry
#, no-c-format
-msgid "CURRENCY as {item.amount.currency}, VALUE as {item.amount.value}"
+msgid "<literal>CURRENCY as {item.amount.currency}, VALUE as {item.amount.value}</literal>"
msgstr ""
#. Tag: entry
-#: query_sql.xml:274
#, no-c-format
msgid "Discriminator of an entity"
msgstr ""
-#. Tag: literal
-#: query_sql.xml:276
+#. Tag: entry
#, no-c-format
-msgid "{[aliasname].class}"
+msgid "<literal>{[aliasname].class}</literal>"
msgstr ""
-#. Tag: literal
-#: query_sql.xml:278
+#. Tag: entry
#, no-c-format
-msgid "DISC as {item.class}"
+msgid "<literal>DISC as {item.class}</literal>"
msgstr ""
#. Tag: entry
-#: query_sql.xml:282
#, no-c-format
msgid "All properties of an entity"
msgstr ""
-#. Tag: literal
-#: query_sql.xml:284 query_sql.xml:332
+#. Tag: entry
#, no-c-format
-msgid "{[aliasname].*}"
+msgid "<literal>{[aliasname].*}</literal>"
msgstr ""
-#. Tag: literal
-#: query_sql.xml:286
+#. Tag: entry
#, no-c-format
-msgid "{item.*}"
+msgid "<literal>{item.*}</literal>"
msgstr ""
#. Tag: entry
-#: query_sql.xml:290
#, no-c-format
msgid "A collection key"
msgstr ""
-#. Tag: literal
-#: query_sql.xml:292
+#. Tag: entry
#, no-c-format
-msgid "{[aliasname].key}"
+msgid "<literal>{[aliasname].key}</literal>"
msgstr ""
-#. Tag: literal
-#: query_sql.xml:294
+#. Tag: entry
#, no-c-format
-msgid "ORGID as {coll.key}"
+msgid "<literal>ORGID as {coll.key}</literal>"
msgstr ""
#. Tag: entry
-#: query_sql.xml:298
#, no-c-format
msgid "The id of an collection"
msgstr ""
-#. Tag: literal
-#: query_sql.xml:300
+#. Tag: entry
#, no-c-format
-msgid "{[aliasname].id}"
+msgid "<literal>{[aliasname].id}</literal>"
msgstr ""
-#. Tag: literal
-#: query_sql.xml:302
+#. Tag: entry
#, no-c-format
-msgid "EMPID as {coll.id}"
+msgid "<literal>EMPID as {coll.id}</literal>"
msgstr ""
#. Tag: entry
-#: query_sql.xml:306
#, no-c-format
msgid "The element of an collection"
msgstr ""
-#. Tag: literal
-#: query_sql.xml:308
+#. Tag: entry
#, no-c-format
-msgid "{[aliasname].element}"
+msgid "<literal>{[aliasname].element}</literal>"
msgstr ""
-#. Tag: literal
-#: query_sql.xml:310
+#. Tag: entry
#, no-c-format
-msgid "XID as {coll.element}"
+msgid "<literal>XID as {coll.element}</literal>"
msgstr ""
#. Tag: entry
-#: query_sql.xml:314
#, no-c-format
msgid "property of the element in the collection"
msgstr ""
-#. Tag: literal
-#: query_sql.xml:316
+#. Tag: entry
#, no-c-format
-msgid "{[aliasname].element.[propertyname]}"
+msgid "<literal>{[aliasname].element.[propertyname]}</literal>"
msgstr ""
-#. Tag: literal
-#: query_sql.xml:318
+#. Tag: entry
#, no-c-format
-msgid "NAME as {coll.element.name}"
+msgid "<literal>NAME as {coll.element.name}</literal>"
msgstr ""
#. Tag: entry
-#: query_sql.xml:322
#, no-c-format
msgid "All properties of the element in the collection"
msgstr ""
-#. Tag: literal
-#: query_sql.xml:324
+#. Tag: entry
#, no-c-format
-msgid "{[aliasname].element.*}"
+msgid "<literal>{[aliasname].element.*}</literal>"
msgstr ""
-#. Tag: literal
-#: query_sql.xml:326
+#. Tag: entry
#, no-c-format
-msgid "{coll.element.*}"
+msgid "<literal>{coll.element.*}</literal>"
msgstr ""
#. Tag: entry
-#: query_sql.xml:330
#, no-c-format
msgid "All properties of the the collection"
msgstr ""
-#. Tag: literal
-#: query_sql.xml:334
+#. Tag: entry
#, no-c-format
-msgid "{coll.*}"
+msgid "<literal>{coll.*}</literal>"
msgstr ""
#. Tag: title
-#: query_sql.xml:343
#, no-c-format
msgid "Returning non-managed entities"
msgstr ""
#. Tag: para
-#: query_sql.xml:345
#, no-c-format
msgid "It is possible to apply a ResultTransformer to native SQL queries, allowing it to return non-managed entities."
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:347
-#, no-c-format
-msgid ""
- "<![CDATA[sess.createSQLQuery(\"SELECT NAME, BIRTHDATE FROM CATS\")\n"
- " .setResultTransformer(Transformers.aliasToBean(CatDTO.class))]]>"
-msgstr ""
-
#. Tag: para
-#: query_sql.xml:357
#, no-c-format
msgid "a result transformer"
msgstr ""
#. Tag: para
-#: query_sql.xml:361
#, no-c-format
msgid "The above query will return a list of <literal>CatDTO</literal> which has been instantiated and injected the values of NAME and BIRTHNAME into its corresponding properties or fields."
msgstr ""
#. Tag: title
-#: query_sql.xml:368
#, no-c-format
msgid "Handling inheritance"
msgstr ""
#. Tag: para
-#: query_sql.xml:370
#, no-c-format
msgid "Native SQL queries which query for entities that are mapped as part of an inheritance must include all properties for the baseclass and all its subclasses."
msgstr ""
#. Tag: title
-#: query_sql.xml:376
#, no-c-format
msgid "Parameters"
msgstr ""
#. Tag: para
-#: query_sql.xml:378
#, no-c-format
msgid "Native SQL queries support positional as well as named parameters:"
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:381
-#, no-c-format
-msgid ""
- "<![CDATA[Query query = sess.createSQLQuery(\"SELECT * FROM CATS WHERE NAME like ?\").addEntity(Cat.class);\n"
- "List pusList = query.setString(0, \"Pus%\").list();\n"
- " \n"
- "query = sess.createSQLQuery(\"SELECT * FROM CATS WHERE NAME like :name\").addEntity(Cat.class);\n"
- "List pusList = query.setString(\"name\", \"Pus%\").list(); ]]>"
-msgstr ""
-
#. Tag: title
-#: query_sql.xml:389
#, no-c-format
msgid "Named SQL queries"
msgstr ""
#. Tag: para
-#: query_sql.xml:391
#, no-c-format
msgid "Named SQL queries can be defined in the mapping document and called in exactly the same way as a named HQL query. In this case, you do <emphasis>not</emphasis> need to call <literal>addEntity()</literal>."
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:396
-#, no-c-format
-msgid ""
- "<![CDATA[<sql-query name=\"persons\">\n"
- " <return alias=\"person\" class=\"eg.Person\"/>\n"
- " SELECT person.NAME AS {person.name},\n"
- " person.AGE AS {person.age},\n"
- " person.SEX AS {person.sex}\n"
- " FROM PERSON person\n"
- " WHERE person.NAME LIKE :namePattern\n"
- "</sql-query>]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_sql.xml:398
-#, no-c-format
-msgid ""
- "<![CDATA[List people = sess.getNamedQuery(\"persons\")\n"
- " .setString(\"namePattern\", namePattern)\n"
- " .setMaxResults(50)\n"
- " .list();]]>"
-msgstr ""
-
#. Tag: para
-#: query_sql.xml:400
#, no-c-format
msgid "The <literal><return-join></literal> element is use to join associations and the <literal><load-collection></literal> element is used to define queries which initialize collections,"
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:404
-#, no-c-format
-msgid ""
- "<![CDATA[<sql-query name=\"personsWith\">\n"
- " <return alias=\"person\" class=\"eg.Person\"/>\n"
- " <return-join alias=\"address\" property=\"person.mailingAddress\"/>\n"
- " SELECT person.NAME AS {person.name},\n"
- " person.AGE AS {person.age},\n"
- " person.SEX AS {person.sex},\n"
- " address.STREET AS {address.street},\n"
- " address.CITY AS {address.city},\n"
- " address.STATE AS {address.state},\n"
- " address.ZIP AS {address.zip}\n"
- " FROM PERSON person\n"
- " JOIN ADDRESS address\n"
- " ON person.ID = address.PERSON_ID AND address.TYPE='MAILING'\n"
- " WHERE person.NAME LIKE :namePattern\n"
- "</sql-query>]]>"
-msgstr ""
-
#. Tag: para
-#: query_sql.xml:406
#, no-c-format
msgid "A named SQL query may return a scalar value. You must declare the column alias and Hibernate type using the <literal><return-scalar></literal> element:"
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:410
-#, no-c-format
-msgid ""
- "<![CDATA[<sql-query name=\"mySqlQuery\">\n"
- " <return-scalar column=\"name\" type=\"string\"/>\n"
- " <return-scalar column=\"age\" type=\"long\"/>\n"
- " SELECT p.NAME AS name,\n"
- " p.AGE AS age,\n"
- " FROM PERSON p WHERE p.NAME LIKE 'Hiber%'\n"
- "</sql-query>]]>"
-msgstr ""
-
#. Tag: para
-#: query_sql.xml:412
#, no-c-format
msgid "You can externalize the resultset mapping information in a <literal><resultset></literal> element which will allow you to either reuse them across several named queries or through the <literal>setResultSetMapping()</literal> API."
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:417
-#, no-c-format
-msgid ""
- "<![CDATA[<resultset name=\"personAddress\">\n"
- " <return alias=\"person\" class=\"eg.Person\"/>\n"
- " <return-join alias=\"address\" property=\"person.mailingAddress\"/>\n"
- "</resultset>\n"
- "\n"
- "<sql-query name=\"personsWith\" resultset-ref=\"personAddress\">\n"
- " SELECT person.NAME AS {person.name},\n"
- " person.AGE AS {person.age},\n"
- " person.SEX AS {person.sex},\n"
- " address.STREET AS {address.street},\n"
- " address.CITY AS {address.city},\n"
- " address.STATE AS {address.state},\n"
- " address.ZIP AS {address.zip}\n"
- " FROM PERSON person\n"
- " JOIN ADDRESS address\n"
- " ON person.ID = address.PERSON_ID AND address.TYPE='MAILING'\n"
- " WHERE person.NAME LIKE :namePattern\n"
- "</sql-query>]]>"
-msgstr ""
-
#. Tag: para
-#: query_sql.xml:419
#, no-c-format
msgid "You can, alternatively, use the resultset mapping information in your hbm files directly in java code."
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:422
-#, no-c-format
-msgid ""
- "<![CDATA[List cats = sess.createSQLQuery(\n"
- " \"select {cat.*}, {kitten.*} from cats cat, cats kitten where kitten.mother = cat.id\"\n"
- " )\n"
- " .setResultSetMapping(\"catAndKitten\")\n"
- " .list();]]>"
-msgstr ""
-
#. Tag: title
-#: query_sql.xml:425
#, no-c-format
msgid "Using return-property to explicitly specify column/alias names"
msgstr ""
#. Tag: para
-#: query_sql.xml:428
#, no-c-format
msgid "You can explicitly tell Hibernate what column aliases to use with <literal><return-property></literal>, instead of using the <literal>{}</literal>-syntax to let Hibernate inject its own aliases.For example:"
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:433
-#, no-c-format
-msgid ""
- "<![CDATA[<sql-query name=\"mySqlQuery\">\n"
- " <return alias=\"person\" class=\"eg.Person\">\n"
- " <return-property name=\"name\" column=\"myName\"/>\n"
- " <return-property name=\"age\" column=\"myAge\"/>\n"
- " <return-property name=\"sex\" column=\"mySex\"/>\n"
- " </return>\n"
- " SELECT person.NAME AS myName,\n"
- " person.AGE AS myAge,\n"
- " person.SEX AS mySex,\n"
- " FROM PERSON person WHERE person.NAME LIKE :name\n"
- "</sql-query>\n"
- "]]>"
-msgstr ""
-
#. Tag: para
-#: query_sql.xml:435
#, no-c-format
msgid "<literal><return-property></literal> also works with multiple columns. This solves a limitation with the <literal>{}</literal>-syntax which cannot allow fine grained control of multi-column properties."
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:440
-#, no-c-format
-msgid ""
- "<![CDATA[<sql-query name=\"organizationCurrentEmployments\">\n"
- " <return alias=\"emp\" class=\"Employment\">\n"
- " <return-property name=\"salary\">\n"
- " <return-column name=\"VALUE\"/>\n"
- " <return-column name=\"CURRENCY\"/>\n"
- " </return-property>\n"
- " <return-property name=\"endDate\" column=\"myEndDate\"/>\n"
- " </return>\n"
- " SELECT EMPLOYEE AS {emp.employee}, EMPLOYER AS {emp.employer},\n"
- " STARTDATE AS {emp.startDate}, ENDDATE AS {emp.endDate},\n"
- " REGIONCODE as {emp.regionCode}, EID AS {emp.id}, VALUE, CURRENCY\n"
- " FROM EMPLOYMENT\n"
- " WHERE EMPLOYER = :id AND ENDDATE IS NULL\n"
- " ORDER BY STARTDATE ASC\n"
- "</sql-query>]]>"
-msgstr ""
-
#. Tag: para
-#: query_sql.xml:442
#, no-c-format
msgid "In this example <literal><return-property></literal> was used in combination with the <literal>{}</literal>-syntax for injection. This allows users to choose how they want to refer column and properties."
msgstr ""
#. Tag: para
-#: query_sql.xml:447
#, no-c-format
msgid "If your mapping has a discriminator you must use <literal><return-discriminator></literal> to specify the discriminator column."
msgstr ""
#. Tag: title
-#: query_sql.xml:453
#, no-c-format
msgid "Using stored procedures for querying"
msgstr ""
#. Tag: para
-#: query_sql.xml:455
#, no-c-format
msgid "Hibernate3 provides support for queries via stored procedures and functions. Most of the following documentation is equivalent for both. The stored procedure/function must return a resultset as the first out-parameter to be able to work with Hibernate. An example of such a stored function in Oracle 9 and higher is as follows:"
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:461
-#, no-c-format
-msgid ""
- "<![CDATA[CREATE OR REPLACE FUNCTION selectAllEmployments\n"
- " RETURN SYS_REFCURSOR\n"
- "AS\n"
- " st_cursor SYS_REFCURSOR;\n"
- "BEGIN\n"
- " OPEN st_cursor FOR\n"
- " SELECT EMPLOYEE, EMPLOYER,\n"
- " STARTDATE, ENDDATE,\n"
- " REGIONCODE, EID, VALUE, CURRENCY\n"
- " FROM EMPLOYMENT;\n"
- " RETURN st_cursor;\n"
- " END;]]>"
-msgstr ""
-
#. Tag: para
-#: query_sql.xml:463
#, no-c-format
msgid "To use this query in Hibernate you need to map it via a named query."
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:466
-#, no-c-format
-msgid ""
- "<![CDATA[<sql-query name=\"selectAllEmployees_SP\" callable=\"true\">\n"
- " <return alias=\"emp\" class=\"Employment\">\n"
- " <return-property name=\"employee\" column=\"EMPLOYEE\"/>\n"
- " <return-property name=\"employer\" column=\"EMPLOYER\"/>\n"
- " <return-property name=\"startDate\" column=\"STARTDATE\"/>\n"
- " <return-property name=\"endDate\" column=\"ENDDATE\"/>\n"
- " <return-property name=\"regionCode\" column=\"REGIONCODE\"/>\n"
- " <return-property name=\"id\" column=\"EID\"/>\n"
- " <return-property name=\"salary\">\n"
- " <return-column name=\"VALUE\"/>\n"
- " <return-column name=\"CURRENCY\"/>\n"
- " </return-property>\n"
- " </return>\n"
- " { ? = call selectAllEmployments() }\n"
- "</sql-query>]]>"
-msgstr ""
-
#. Tag: para
-#: query_sql.xml:468
#, no-c-format
msgid "Stored procedures currently only return scalars and entities. <literal><return-join></literal> and <literal><load-collection></literal> are not supported."
msgstr ""
#. Tag: title
-#: query_sql.xml:473
#, no-c-format
msgid "Rules/limitations for using stored procedures"
msgstr ""
#. Tag: para
-#: query_sql.xml:475
#, no-c-format
msgid "You cannot use stored procedures with Hibernate unless you follow some procedure/function rules. If they do not follow those rules they are not usable with Hibernate. If you still want to use these procedures you have to execute them via <literal>session.connection()</literal>. The rules are different for each database, since database vendors have different stored procedure semantics/syntax."
msgstr ""
#. Tag: para
-#: query_sql.xml:482
#, no-c-format
msgid "Stored procedure queries cannot be paged with <literal>setFirstResult()/setMaxResults()</literal>."
msgstr ""
#. Tag: para
-#: query_sql.xml:485
#, no-c-format
msgid "The recommended call form is standard SQL92: <literal>{ ? = call functionName(<parameters>) }</literal> or <literal>{ ? = call procedureName(<parameters>}</literal>. Native call syntax is not supported."
msgstr ""
#. Tag: para
-#: query_sql.xml:490
#, no-c-format
msgid "For Oracle the following rules apply:"
msgstr ""
#. Tag: para
-#: query_sql.xml:494
#, no-c-format
msgid "A function must return a result set. The first parameter of a procedure must be an <literal>OUT</literal> that returns a result set. This is done by using a <literal>SYS_REFCURSOR</literal> type in Oracle 9 or 10. In Oracle you need to define a <literal>REF CURSOR</literal> type. See Oracle literature for further information."
msgstr ""
#. Tag: para
-#: query_sql.xml:503
#, no-c-format
msgid "For Sybase or MS SQL server the following rules apply:"
msgstr ""
#. Tag: para
-#: query_sql.xml:507
#, no-c-format
msgid "The procedure must return a result set. Note that since these servers can return multiple result sets and update counts, Hibernate will iterate the results and take the first result that is a result set as its return value. Everything else will be discarded."
msgstr ""
#. Tag: para
-#: query_sql.xml:515
#, no-c-format
msgid "If you can enable <literal>SET NOCOUNT ON</literal> in your procedure it will probably be more efficient, but this is not a requirement."
msgstr ""
#. Tag: title
-#: query_sql.xml:525
#, no-c-format
msgid "Custom SQL for create, update and delete"
msgstr ""
#. Tag: para
-#: query_sql.xml:527
#, no-c-format
msgid "Hibernate3 can use custom SQL statements for create, update, and delete operations. The class and collection persisters in Hibernate already contain a set of configuration time generated strings (insertsql, deletesql, updatesql etc.). The mapping tags <literal><sql-insert></literal>, <literal><sql-delete></literal>, and <literal><sql-update></literal> override these strings:"
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:535
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Person\">\n"
- " <id name=\"id\">\n"
- " <generator class=\"increment\"/>\n"
- " </id>\n"
- " <property name=\"name\" not-null=\"true\"/>\n"
- " <sql-insert>INSERT INTO PERSON (NAME, ID) VALUES ( UPPER(?), ? )</sql-insert>\n"
- " <sql-update>UPDATE PERSON SET NAME=UPPER(?) WHERE ID=?</sql-update>\n"
- " <sql-delete>DELETE FROM PERSON WHERE ID=?</sql-delete>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: query_sql.xml:537
#, no-c-format
msgid "The SQL is directly executed in your database, so you can use any dialect you like. This will reduce the portability of your mapping if you use database specific SQL."
msgstr ""
#. Tag: para
-#: query_sql.xml:541
#, no-c-format
msgid "Stored procedures are supported if the <literal>callable</literal> attribute is set:"
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:544
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Person\">\n"
- " <id name=\"id\">\n"
- " <generator class=\"increment\"/>\n"
- " </id>\n"
- " <property name=\"name\" not-null=\"true\"/>\n"
- " <sql-insert callable=\"true\">{call createPerson (?, ?)}</sql-insert>\n"
- " <sql-delete callable=\"true\">{? = call deletePerson (?)}</sql-delete>\n"
- " <sql-update callable=\"true\">{? = call updatePerson (?, ?)}</sql-update>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: query_sql.xml:546
#, no-c-format
msgid "The order of the positional parameters is vital, as they must be in the same sequence as Hibernate expects them."
msgstr ""
#. Tag: para
-#: query_sql.xml:549
#, no-c-format
msgid "You can view the expected order by enabling debug logging for the <literal>org.hibernate.persister.entity</literal> level. With this level enabled, Hibernate will print out the static SQL that is used to create, update, delete etc. entities. To view the expected sequence, do not include your custom SQL in the mapping files, as this will override the Hibernate generated static SQL."
msgstr ""
#. Tag: para
-#: query_sql.xml:556
#, no-c-format
msgid "The stored procedures are in most cases required to return the number of rows inserted, updated and deleted, as Hibernate has some runtime checks for the success of the statement. Hibernate always registers the first statement parameter as a numeric output parameter for the CUD operations:"
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:562
-#, no-c-format
-msgid ""
- "<![CDATA[CREATE OR REPLACE FUNCTION updatePerson (uid IN NUMBER, uname IN VARCHAR2)\n"
- " RETURN NUMBER IS\n"
- "BEGIN\n"
- "\n"
- " update PERSON\n"
- " set\n"
- " NAME = uname,\n"
- " where\n"
- " ID = uid;\n"
- "\n"
- " return SQL%ROWCOUNT;\n"
- "\n"
- "END updatePerson;]]>"
-msgstr ""
-
#. Tag: title
-#: query_sql.xml:566
#, no-c-format
msgid "Custom SQL for loading"
msgstr ""
#. Tag: para
-#: query_sql.xml:568
#, no-c-format
msgid "You can also declare your own SQL (or HQL) queries for entity loading:"
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:571
-#, no-c-format
-msgid ""
- "<![CDATA[<sql-query name=\"person\">\n"
- " <return alias=\"pers\" class=\"Person\" lock-mode=\"upgrade\"/>\n"
- " SELECT NAME AS {pers.name}, ID AS {pers.id}\n"
- " FROM PERSON\n"
- " WHERE ID=?\n"
- " FOR UPDATE\n"
- "</sql-query>]]>"
-msgstr ""
-
#. Tag: para
-#: query_sql.xml:573
#, no-c-format
msgid "This is just a named query declaration, as discussed earlier. You can reference this named query in a class mapping:"
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:576
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Person\">\n"
- " <id name=\"id\">\n"
- " <generator class=\"increment\"/>\n"
- " </id>\n"
- " <property name=\"name\" not-null=\"true\"/>\n"
- " <loader query-ref=\"person\"/>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: query_sql.xml:578
#, no-c-format
msgid "This even works with stored procedures."
msgstr ""
#. Tag: para
-#: query_sql.xml:580
#, no-c-format
msgid "You can even define a query for collection loading:"
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:582
-#, no-c-format
-msgid ""
- "<![CDATA[<set name=\"employments\" inverse=\"true\">\n"
- " <key/>\n"
- " <one-to-many class=\"Employment\"/>\n"
- " <loader query-ref=\"employments\"/>\n"
- "</set>]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: query_sql.xml:584
-#, no-c-format
-msgid ""
- "<![CDATA[<sql-query name=\"employments\">\n"
- " <load-collection alias=\"emp\" role=\"Person.employments\"/>\n"
- " SELECT {emp.*}\n"
- " FROM EMPLOYMENT emp\n"
- " WHERE EMPLOYER = :id\n"
- " ORDER BY STARTDATE ASC, EMPLOYEE ASC\n"
- "</sql-query>]]>"
-msgstr ""
-
#. Tag: para
-#: query_sql.xml:586
#, no-c-format
msgid "You can also define an entity loader that loads a collection by join fetching:"
msgstr ""
-#. Tag: programlisting
-#: query_sql.xml:589
-#, no-c-format
-msgid ""
- "<![CDATA[<sql-query name=\"person\">\n"
- " <return alias=\"pers\" class=\"Person\"/>\n"
- " <return-join alias=\"emp\" property=\"pers.employments\"/>\n"
- " SELECT NAME AS {pers.*}, {emp.*}\n"
- " FROM PERSON pers\n"
- " LEFT OUTER JOIN EMPLOYMENT emp\n"
- " ON pers.ID = emp.PERSON_ID\n"
- " WHERE ID=?\n"
- "</sql-query>]]>"
-msgstr ""
-
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/session_api.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/session_api.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/session_api.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,1354 +1,759 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-10 21:02+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:19\n"
+"PO-Revision-Date: 2010-01-08T04:07:19\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
-#: session_api.xml:29
#, no-c-format
msgid "Working with objects"
msgstr ""
#. Tag: para
-#: session_api.xml:31
#, no-c-format
msgid "Hibernate is a full object/relational mapping solution that not only shields the developer from the details of the underlying database management system, but also offers <emphasis>state management</emphasis> of objects. This is, contrary to the management of SQL <literal>statements</literal> in common JDBC/SQL persistence layers, a natural object-oriented view of persistence in Java applications."
msgstr ""
#. Tag: para
-#: session_api.xml:40
#, no-c-format
msgid "In other words, Hibernate application developers should always think about the <emphasis>state</emphasis> of their objects, and not necessarily about the execution of SQL statements. This part is taken care of by Hibernate and is only relevant for the application developer when tuning the performance of the system."
msgstr ""
#. Tag: title
-#: session_api.xml:48
#, no-c-format
msgid "Hibernate object states"
msgstr ""
#. Tag: para
-#: session_api.xml:50
#, no-c-format
msgid "Hibernate defines and supports the following object states:"
msgstr ""
#. Tag: para
-#: session_api.xml:56
#, no-c-format
msgid "<emphasis>Transient</emphasis> - an object is transient if it has just been instantiated using the <literal>new</literal> operator, and it is not associated with a Hibernate <literal>Session</literal>. It has no persistent representation in the database and no identifier value has been assigned. Transient instances will be destroyed by the garbage collector if the application does not hold a reference anymore. Use the Hibernate <literal>Session</literal> to make an object persistent (and let Hibernate take care of the SQL statements that need to be executed for this transition)."
msgstr ""
#. Tag: para
-#: session_api.xml:68
#, no-c-format
msgid "<emphasis>Persistent</emphasis> - a persistent instance has a representation in the database and an identifier value. It might just have been saved or loaded, however, it is by definition in the scope of a <literal>Session</literal>. Hibernate will detect any changes made to an object in persistent state and synchronize the state with the database when the unit of work completes. Developers do not execute manual <literal>UPDATE</literal> statements, or <literal>DELETE</literal> statements when an object should be made transient."
msgstr ""
#. Tag: para
-#: session_api.xml:79
#, no-c-format
msgid "<emphasis>Detached</emphasis> - a detached instance is an object that has been persistent, but its <literal>Session</literal> has been closed. The reference to the object is still valid, of course, and the detached instance might even be modified in this state. A detached instance can be reattached to a new <literal>Session</literal> at a later point in time, making it (and all the modifications) persistent again. This feature enables a programming model for long running units of work that require user think-time. We call them <emphasis>application transactions</emphasis>, i.e., a unit of work from the point of view of the user."
msgstr ""
#. Tag: para
-#: session_api.xml:93
#, no-c-format
msgid "We will now discuss the states and state transitions (and the Hibernate methods that trigger a transition) in more detail."
msgstr ""
#. Tag: title
-#: session_api.xml:101
#, no-c-format
msgid "Making objects persistent"
msgstr ""
#. Tag: para
-#: session_api.xml:103
#, no-c-format
msgid "Newly instantiated instances of a a persistent class are considered <emphasis>transient</emphasis> by Hibernate. We can make a transient instance <emphasis>persistent</emphasis> by associating it with a session:"
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:110
-#, no-c-format
-msgid ""
- "<![CDATA[DomesticCat fritz = new DomesticCat();\n"
- "fritz.setColor(Color.GINGER);\n"
- "fritz.setSex('M');\n"
- "fritz.setName(\"Fritz\");\n"
- "Long generatedId = (Long) sess.save(fritz);]]>"
-msgstr ""
-
#. Tag: para
-#: session_api.xml:112
#, no-c-format
msgid "If <literal>Cat</literal> has a generated identifier, the identifier is generated and assigned to the <literal>cat</literal> when <literal>save()</literal> is called. If <literal>Cat</literal> has an <literal>assigned</literal> identifier, or a composite key, the identifier should be assigned to the <literal>cat</literal> instance before calling <literal>save()</literal>. You can also use <literal>persist()</literal> instead of <literal>save()</literal>, with the semantics defined in the EJB3 early draft."
msgstr ""
#. Tag: para
-#: session_api.xml:124
#, no-c-format
msgid "<literal>persist()</literal> makes a transient instance persistent. However, it does not guarantee that the identifier value will be assigned to the persistent instance immediately, the assignment might happen at flush time. <literal>persist()</literal> also guarantees that it will not execute an <literal>INSERT</literal> statement if it is called outside of transaction boundaries. This is useful in long-running conversations with an extended Session/persistence context."
msgstr ""
#. Tag: para
-#: session_api.xml:135
#, no-c-format
msgid "<literal>save()</literal> does guarantee to return an identifier. If an INSERT has to be executed to get the identifier ( e.g. \"identity\" generator, not \"sequence\"), this INSERT happens immediately, no matter if you are inside or outside of a transaction. This is problematic in a long-running conversation with an extended Session/persistence context."
msgstr ""
#. Tag: para
-#: session_api.xml:145
#, no-c-format
msgid "Alternatively, you can assign the identifier using an overloaded version of <literal>save()</literal>."
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:150
-#, no-c-format
-msgid ""
- "<![CDATA[DomesticCat pk = new DomesticCat();\n"
- "pk.setColor(Color.TABBY);\n"
- "pk.setSex('F');\n"
- "pk.setName(\"PK\");\n"
- "pk.setKittens( new HashSet() );\n"
- "pk.addKitten(fritz);\n"
- "sess.save( pk, new Long(1234) );]]>"
-msgstr ""
-
#. Tag: para
-#: session_api.xml:152
#, no-c-format
msgid "If the object you make persistent has associated objects (e.g. the <literal>kittens</literal> collection in the previous example), these objects can be made persistent in any order you like unless you have a <literal>NOT NULL</literal> constraint upon a foreign key column. There is never a risk of violating foreign key constraints. However, you might violate a <literal>NOT NULL</literal> constraint if you <literal>save()</literal> the objects in the wrong order."
msgstr ""
#. Tag: para
-#: session_api.xml:162
#, no-c-format
msgid "Usually you do not bother with this detail, as you will normally use Hibernate's <emphasis>transitive persistence</emphasis> feature to save the associated objects automatically. Then, even <literal>NOT NULL</literal> constraint violations do not occur - Hibernate will take care of everything. Transitive persistence is discussed later in this chapter."
msgstr ""
#. Tag: title
-#: session_api.xml:173
#, no-c-format
msgid "Loading an object"
msgstr ""
#. Tag: para
-#: session_api.xml:175
#, no-c-format
msgid "The <literal>load()</literal> methods of <literal>Session</literal> provide a way of retrieving a persistent instance if you know its identifier. <literal>load()</literal> takes a class object and loads the state into a newly instantiated instance of that class in a persistent state."
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:182
-#, no-c-format
-msgid "<![CDATA[Cat fritz = (Cat) sess.load(Cat.class, generatedId);]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: session_api.xml:184
-#, no-c-format
-msgid ""
- "<![CDATA[// you need to wrap primitive identifiers\n"
- "long id = 1234;\n"
- "DomesticCat pk = (DomesticCat) sess.load( DomesticCat.class, new Long(id) );]]>"
-msgstr ""
-
#. Tag: para
-#: session_api.xml:186
#, no-c-format
msgid "Alternatively, you can load state into a given instance:"
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:190
-#, no-c-format
-msgid ""
- "<![CDATA[Cat cat = new DomesticCat();\n"
- "// load pk's state into cat\n"
- "sess.load( cat, new Long(pkId) );\n"
- "Set kittens = cat.getKittens();]]>"
-msgstr ""
-
#. Tag: para
-#: session_api.xml:192
#, no-c-format
msgid "Be aware that <literal>load()</literal> will throw an unrecoverable exception if there is no matching database row. If the class is mapped with a proxy, <literal>load()</literal> just returns an uninitialized proxy and does not actually hit the database until you invoke a method of the proxy. This is useful if you wish to create an association to an object without actually loading it from the database. It also allows multiple instances to be loaded as a batch if <literal>batch-size</literal> is defined for the class mapping."
msgstr ""
#. Tag: para
-#: session_api.xml:203
#, no-c-format
msgid "If you are not certain that a matching row exists, you should use the <literal>get()</literal> method which hits the database immediately and returns null if there is no matching row."
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:209
-#, no-c-format
-msgid ""
- "<![CDATA[Cat cat = (Cat) sess.get(Cat.class, id);\n"
- "if (cat==null) {\n"
- " cat = new Cat();\n"
- " sess.save(cat, id);\n"
- "}\n"
- "return cat;]]>"
-msgstr ""
-
#. Tag: para
-#: session_api.xml:211
#, no-c-format
msgid "You can even load an object using an SQL <literal>SELECT ... FOR UPDATE</literal>, using a <literal>LockMode</literal>. See the API documentation for more information."
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:216
-#, no-c-format
-msgid "<![CDATA[Cat cat = (Cat) sess.get(Cat.class, id, LockMode.UPGRADE);]]>"
-msgstr ""
-
#. Tag: para
-#: session_api.xml:218
#, no-c-format
msgid "Any associated instances or contained collections will <emphasis>not</emphasis> be selected <literal>FOR UPDATE</literal>, unless you decide to specify <literal>lock</literal> or <literal>all</literal> as a cascade style for the association."
msgstr ""
#. Tag: para
-#: session_api.xml:225
#, no-c-format
msgid "It is possible to re-load an object and all its collections at any time, using the <literal>refresh()</literal> method. This is useful when database triggers are used to initialize some of the properties of the object."
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:231
-#, no-c-format
-msgid ""
- "<![CDATA[sess.save(cat);\n"
- "sess.flush(); //force the SQL INSERT\n"
- "sess.refresh(cat); //re-read the state (after the trigger executes)]]>"
-msgstr ""
-
#. Tag: para
-#: session_api.xml:233
#, no-c-format
-msgid "How much does Hibernate load from the database and how many SQL <literal>SELECT</literal>s will it use? This depends on the <emphasis>fetching strategy</emphasis>. This is explained in <xref linkend=\"performance-fetching\"/>."
+msgid "How much does Hibernate load from the database and how many SQL <literal>SELECT</literal>s will it use? This depends on the <emphasis>fetching strategy</emphasis>. This is explained in <xref linkend=\"performance-fetching\" />."
msgstr ""
#. Tag: title
-#: session_api.xml:243
#, no-c-format
msgid "Querying"
msgstr ""
#. Tag: para
-#: session_api.xml:245
#, no-c-format
msgid "If you do not know the identifiers of the objects you are looking for, you need a query. Hibernate supports an easy-to-use but powerful object oriented query language (HQL). For programmatic query creation, Hibernate supports a sophisticated Criteria and Example query feature (QBC and QBE). You can also express your query in the native SQL of your database, with optional support from Hibernate for result set conversion into objects."
msgstr ""
#. Tag: title
-#: session_api.xml:255
#, no-c-format
msgid "Executing queries"
msgstr ""
#. Tag: para
-#: session_api.xml:257
#, no-c-format
msgid "HQL and native SQL queries are represented with an instance of <literal>org.hibernate.Query</literal>. This interface offers methods for parameter binding, result set handling, and for the execution of the actual query. You always obtain a <literal>Query</literal> using the current <literal>Session</literal>:"
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:264
-#, no-c-format
-msgid ""
- "<![CDATA[List cats = session.createQuery(\n"
- " \"from Cat as cat where cat.birthdate < ?\")\n"
- " .setDate(0, date)\n"
- " .list();\n"
- "\n"
- "List mothers = session.createQuery(\n"
- " \"select mother from Cat as cat join cat.mother as mother where cat.name = ?\")\n"
- " .setString(0, name)\n"
- " .list();\n"
- "\n"
- "List kittens = session.createQuery(\n"
- " \"from Cat as cat where cat.mother = ?\")\n"
- " .setEntity(0, pk)\n"
- " .list();\n"
- "\n"
- "Cat mother = (Cat) session.createQuery(\n"
- " \"select cat.mother from Cat as cat where cat = ?\")\n"
- " .setEntity(0, izi)\n"
- " .uniqueResult();]]\n"
- "\n"
- "Query mothersWithKittens = (Cat) session.createQuery(\n"
- " \"select mother from Cat as mother left join fetch mother.kittens\");\n"
- "Set uniqueMothers = new HashSet(mothersWithKittens.list());]]>"
-msgstr ""
-
#. Tag: para
-#: session_api.xml:266
#, no-c-format
msgid "A query is usually executed by invoking <literal>list()</literal>. The result of the query will be loaded completely into a collection in memory. Entity instances retrieved by a query are in a persistent state. The <literal>uniqueResult()</literal> method offers a shortcut if you know your query will only return a single object. Queries that make use of eager fetching of collections usually return duplicates of the root objects, but with their collections initialized. You can filter these duplicates through a <literal>Set</literal>."
msgstr ""
#. Tag: title
-#: session_api.xml:278
#, no-c-format
msgid "Iterating results"
msgstr ""
#. Tag: para
-#: session_api.xml:280
#, no-c-format
msgid "Occasionally, you might be able to achieve better performance by executing the query using the <literal>iterate()</literal> method. This will usually be the case if you expect that the actual entity instances returned by the query will already be in the session or second-level cache. If they are not already cached, <literal>iterate()</literal> will be slower than <literal>list()</literal> and might require many database hits for a simple query, usually <emphasis>1</emphasis> for the initial select which only returns identifiers, and <emphasis>n</emphasis> additional selects to initialize the actual instances."
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:292
-#, no-c-format
-msgid ""
- "<![CDATA[// fetch ids\n"
- "Iterator iter = sess.createQuery(\"from eg.Qux q order by q.likeliness\").iterate();\n"
- "while ( iter.hasNext() ) {\n"
- " Qux qux = (Qux) iter.next(); // fetch the object\n"
- " // something we couldnt express in the query\n"
- " if ( qux.calculateComplicatedAlgorithm() ) {\n"
- " // delete the current instance\n"
- " iter.remove();\n"
- " // dont need to process the rest\n"
- " break;\n"
- " }\n"
- "}]]>"
-msgstr ""
-
#. Tag: title
-#: session_api.xml:296
#, no-c-format
msgid "Queries that return tuples"
msgstr ""
#. Tag: para
-#: session_api.xml:298
#, no-c-format
msgid "Hibernate queries sometimes return tuples of objects. Each tuple is returned as an array:"
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:303
-#, no-c-format
-msgid ""
- "<![CDATA[Iterator kittensAndMothers = sess.createQuery(\n"
- " \"select kitten, mother from Cat kitten join kitten.mother mother\")\n"
- " .list()\n"
- " .iterator();\n"
- "\n"
- "while ( kittensAndMothers.hasNext() ) {\n"
- " Object[] tuple = (Object[]) kittensAndMothers.next();\n"
- " Cat kitten = (Cat) tuple[0];\n"
- " Cat mother = (Cat) tuple[1];\n"
- " ....\n"
- "}]]>"
-msgstr ""
-
#. Tag: title
-#: session_api.xml:308
#, no-c-format
msgid "Scalar results"
msgstr ""
#. Tag: para
-#: session_api.xml:310
#, no-c-format
msgid "Queries can specify a property of a class in the <literal>select</literal> clause. They can even call SQL aggregate functions. Properties or aggregates are considered \"scalar\" results and not entities in persistent state."
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:316
-#, no-c-format
-msgid ""
- "<![CDATA[Iterator results = sess.createQuery(\n"
- " \"select cat.color, min(cat.birthdate), count(cat) from Cat cat \" +\n"
- " \"group by cat.color\")\n"
- " .list()\n"
- " .iterator();\n"
- "\n"
- "while ( results.hasNext() ) {\n"
- " Object[] row = (Object[]) results.next();\n"
- " Color type = (Color) row[0];\n"
- " Date oldest = (Date) row[1];\n"
- " Integer count = (Integer) row[2];\n"
- " .....\n"
- "}]]>"
-msgstr ""
-
#. Tag: title
-#: session_api.xml:321
#, no-c-format
msgid "Bind parameters"
msgstr ""
#. Tag: para
-#: session_api.xml:323
#, no-c-format
msgid "Methods on <literal>Query</literal> are provided for binding values to named parameters or JDBC-style <literal>?</literal> parameters. <emphasis>Contrary to JDBC, Hibernate numbers parameters from zero.</emphasis> Named parameters are identifiers of the form <literal>:name</literal> in the query string. The advantages of named parameters are as follows:"
msgstr ""
#. Tag: para
-#: session_api.xml:333
#, no-c-format
msgid "named parameters are insensitive to the order they occur in the query string"
msgstr ""
#. Tag: para
-#: session_api.xml:339
#, no-c-format
msgid "they can occur multiple times in the same query"
msgstr ""
#. Tag: para
-#: session_api.xml:344
#, no-c-format
msgid "they are self-documenting"
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:350
-#, no-c-format
-msgid ""
- "<![CDATA[//named parameter (preferred)\n"
- "Query q = sess.createQuery(\"from DomesticCat cat where cat.name = :name\");\n"
- "q.setString(\"name\", \"Fritz\");\n"
- "Iterator cats = q.iterate();]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: session_api.xml:352
-#, no-c-format
-msgid ""
- "<![CDATA[//positional parameter\n"
- "Query q = sess.createQuery(\"from DomesticCat cat where cat.name = ?\");\n"
- "q.setString(0, \"Izi\");\n"
- "Iterator cats = q.iterate();]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: session_api.xml:354
-#, no-c-format
-msgid ""
- "<![CDATA[//named parameter list\n"
- "List names = new ArrayList();\n"
- "names.add(\"Izi\");\n"
- "names.add(\"Fritz\");\n"
- "Query q = sess.createQuery(\"from DomesticCat cat where cat.name in (:namesList)\");\n"
- "q.setParameterList(\"namesList\", names);\n"
- "List cats = q.list();]]>"
-msgstr ""
-
#. Tag: title
-#: session_api.xml:359
#, no-c-format
msgid "Pagination"
msgstr ""
#. Tag: para
-#: session_api.xml:361
#, no-c-format
msgid "If you need to specify bounds upon your result set, that is, the maximum number of rows you want to retrieve and/or the first row you want to retrieve, you can use methods of the <literal>Query</literal> interface:"
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:367
-#, no-c-format
-msgid ""
- "<![CDATA[Query q = sess.createQuery(\"from DomesticCat cat\");\n"
- "q.setFirstResult(20);\n"
- "q.setMaxResults(10);\n"
- "List cats = q.list();]]>"
-msgstr ""
-
#. Tag: para
-#: session_api.xml:369
#, no-c-format
msgid "Hibernate knows how to translate this limit query into the native SQL of your DBMS."
msgstr ""
#. Tag: title
-#: session_api.xml:377
#, no-c-format
msgid "Scrollable iteration"
msgstr ""
#. Tag: para
-#: session_api.xml:379
#, no-c-format
msgid "If your JDBC driver supports scrollable <literal>ResultSet</literal>s, the <literal>Query</literal> interface can be used to obtain a <literal>ScrollableResults</literal> object that allows flexible navigation of the query results."
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:386
-#, no-c-format
-msgid ""
- "<![CDATA[Query q = sess.createQuery(\"select cat.name, cat from DomesticCat cat \" +\n"
- " \"order by cat.name\");\n"
- "ScrollableResults cats = q.scroll();\n"
- "if ( cats.first() ) {\n"
- "\n"
- " // find the first name on each page of an alphabetical list of cats by name\n"
- " firstNamesOfPages = new ArrayList();\n"
- " do {\n"
- " String name = cats.getString(0);\n"
- " firstNamesOfPages.add(name);\n"
- " }\n"
- " while ( cats.scroll(PAGE_SIZE) );\n"
- "\n"
- " // Now get the first page of cats\n"
- " pageOfCats = new ArrayList();\n"
- " cats.beforeFirst();\n"
- " int i=0;\n"
- " while( ( PAGE_SIZE > i++ ) && cats.next() ) pageOfCats.add( cats.get(1) );\n"
- "\n"
- "}\n"
- "cats.close()]]>"
-msgstr ""
-
#. Tag: para
-#: session_api.xml:388
#, no-c-format
msgid "Note that an open database connection and cursor is required for this functionality. Use <literal>setMaxResult()</literal>/<literal>setFirstResult()</literal> if you need offline pagination functionality."
msgstr ""
#. Tag: title
-#: session_api.xml:397
#, no-c-format
msgid "Externalizing named queries"
msgstr ""
#. Tag: para
-#: session_api.xml:399
#, no-c-format
msgid "You can also define named queries in the mapping document. Remember to use a <literal>CDATA</literal> section if your query contains characters that could be interpreted as markup."
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:405
-#, no-c-format
-msgid ""
- "<![CDATA[<query name=\"ByNameAndMaximumWeight\"><![CDATA[\n"
- " from eg.DomesticCat as cat\n"
- " where cat.name = ?\n"
- " and cat.weight > ?\n"
- "] ]></query>]]>"
-msgstr ""
-
#. Tag: para
-#: session_api.xml:407
#, no-c-format
msgid "Parameter binding and executing is done programatically:"
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:411
-#, no-c-format
-msgid ""
- "<![CDATA[Query q = sess.getNamedQuery(\"ByNameAndMaximumWeight\");\n"
- "q.setString(0, name);\n"
- "q.setInt(1, minWeight);\n"
- "List cats = q.list();]]>"
-msgstr ""
-
#. Tag: para
-#: session_api.xml:413
#, no-c-format
msgid "The actual program code is independent of the query language that is used. You can also define native SQL queries in metadata, or migrate existing queries to Hibernate by placing them in mapping files."
msgstr ""
#. Tag: para
-#: session_api.xml:419
#, no-c-format
msgid "Also note that a query declaration inside a <literal><hibernate-mapping></literal> element requires a global unique name for the query, while a query declaration inside a <literal><class></literal> element is made unique automatically by prepending the fully qualified name of the class. For example <literal>eg.Cat.ByNameAndMaximumWeight</literal>."
msgstr ""
#. Tag: title
-#: session_api.xml:432
#, no-c-format
msgid "Filtering collections"
msgstr ""
#. Tag: para
-#: session_api.xml:433
#, no-c-format
msgid "A collection <emphasis>filter</emphasis> is a special type of query that can be applied to a persistent collection or array. The query string can refer to <literal>this</literal>, meaning the current collection element."
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:439
-#, no-c-format
-msgid ""
- "<![CDATA[Collection blackKittens = session.createFilter(\n"
- " pk.getKittens(), \n"
- " \"where this.color = ?\")\n"
- " .setParameter( Color.BLACK, Hibernate.custom(ColorUserType.class) )\n"
- " .list()\n"
- ");]]>"
-msgstr ""
-
#. Tag: para
-#: session_api.xml:441
#, no-c-format
msgid "The returned collection is considered a bag that is a copy of the given collection. The original collection is not modified. This is contrary to the implication of the name \"filter\", but consistent with expected behavior."
msgstr ""
#. Tag: para
-#: session_api.xml:447
#, no-c-format
msgid "Observe that filters do not require a <literal>from</literal> clause, although they can have one if required. Filters are not limited to returning the collection elements themselves."
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:452
-#, no-c-format
-msgid ""
- "<![CDATA[Collection blackKittenMates = session.createFilter(\n"
- " pk.getKittens(), \n"
- " \"select this.mate where this.color = eg.Color.BLACK.intValue\")\n"
- " .list();]]>"
-msgstr ""
-
#. Tag: para
-#: session_api.xml:454
#, no-c-format
msgid "Even an empty filter query is useful, e.g. to load a subset of elements in a large collection:"
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:459
-#, no-c-format
-msgid ""
- "<![CDATA[Collection tenKittens = session.createFilter(\n"
- " mother.getKittens(), \"\")\n"
- " .setFirstResult(0).setMaxResults(10)\n"
- " .list();]]>"
-msgstr ""
-
#. Tag: title
-#: session_api.xml:464
#, no-c-format
msgid "Criteria queries"
msgstr ""
#. Tag: para
-#: session_api.xml:466
#, no-c-format
msgid "HQL is extremely powerful, but some developers prefer to build queries dynamically using an object-oriented API, rather than building query strings. Hibernate provides an intuitive <literal>Criteria</literal> query API for these cases:"
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:472
-#, no-c-format
-msgid ""
- "<![CDATA[Criteria crit = session.createCriteria(Cat.class);\n"
- "crit.add( Restrictions.eq( \"color\", eg.Color.BLACK ) );\n"
- "crit.setMaxResults(10);\n"
- "List cats = crit.list();]]>"
-msgstr ""
-
#. Tag: para
-#: session_api.xml:474
#, no-c-format
-msgid "The <literal>Criteria</literal> and the associated <literal>Example</literal> API are discussed in more detail in <xref linkend=\"querycriteria\"/>."
+msgid "The <literal>Criteria</literal> and the associated <literal>Example</literal> API are discussed in more detail in <xref linkend=\"querycriteria\" />."
msgstr ""
#. Tag: title
-#: session_api.xml:482
#, no-c-format
msgid "Queries in native SQL"
msgstr ""
#. Tag: para
-#: session_api.xml:484
#, no-c-format
msgid "You can express a query in SQL, using <literal>createSQLQuery()</literal> and let Hibernate manage the mapping from result sets to objects. You can at any time call <literal>session.connection()</literal> and use the JDBC <literal>Connection</literal> directly. If you choose to use the Hibernate API, you must enclose SQL aliases in braces:"
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:492
-#, no-c-format
-msgid ""
- "<![CDATA[List cats = session.createSQLQuery(\"SELECT {cat.*} FROM CAT {cat} WHERE ROWNUM<10\")\n"
- " .addEntity(\"cat\", Cat.class)\n"
- ".list();]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: session_api.xml:494
-#, no-c-format
-msgid ""
- "<![CDATA[List cats = session.createSQLQuery(\n"
- " \"SELECT {cat}.ID AS {cat.id}, {cat}.SEX AS {cat.sex}, \" +\n"
- " \"{cat}.MATE AS {cat.mate}, {cat}.SUBCLASS AS {cat.class}, ... \" +\n"
- " \"FROM CAT {cat} WHERE ROWNUM<10\")\n"
- " .addEntity(\"cat\", Cat.class)\n"
- ".list()]]>"
-msgstr ""
-
#. Tag: para
-#: session_api.xml:496
#, no-c-format
-msgid "SQL queries can contain named and positional parameters, just like Hibernate queries. More information about native SQL queries in Hibernate can be found in <xref linkend=\"querysql\"/>."
+msgid "SQL queries can contain named and positional parameters, just like Hibernate queries. More information about native SQL queries in Hibernate can be found in <xref linkend=\"querysql\" />."
msgstr ""
#. Tag: title
-#: session_api.xml:507
#, no-c-format
msgid "Modifying persistent objects"
msgstr ""
#. Tag: para
-#: session_api.xml:509
#, no-c-format
msgid "<emphasis>Transactional persistent instances</emphasis> (i.e. objects loaded, saved, created or queried by the <literal>Session</literal>) can be manipulated by the application, and any changes to persistent state will be persisted when the <literal>Session</literal> is <emphasis>flushed</emphasis>. This is discussed later in this chapter. There is no need to call a particular method (like <literal>update()</literal>, which has a different purpose) to make your modifications persistent. The most straightforward way to update the state of an object is to <literal>load()</literal> it and then manipulate it directly while the <literal>Session</literal> is open:"
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:520
-#, no-c-format
-msgid ""
- "<![CDATA[DomesticCat cat = (DomesticCat) sess.load( Cat.class, new Long(69) );\n"
- "cat.setName(\"PK\");\n"
- "sess.flush(); // changes to cat are automatically detected and persisted]]>"
-msgstr ""
-
#. Tag: para
-#: session_api.xml:522
#, no-c-format
msgid "Sometimes this programming model is inefficient, as it requires in the same session both an SQL <literal>SELECT</literal> to load an object and an SQL <literal>UPDATE</literal> to persist its updated state. Hibernate offers an alternate approach by using detached instances."
msgstr ""
#. Tag: para
-#: session_api.xml:529
#, no-c-format
-msgid "Hibernate does not offer its own API for direct execution of <literal>UPDATE</literal> or <literal>DELETE</literal> statements. Hibernate is a <emphasis>state management</emphasis> service, you do not have to think in <emphasis>statements</emphasis> to use it. JDBC is a perfect API for executing SQL statements, you can get a JDBC <literal>Connection</literal> at any time by calling <literal>session.connection()</literal>. Furthermore, the notion of mass operations conflicts with object/relational mapping for online transaction processing-oriented applications. Future versions of Hibernate can, however, provide special mass operation functions. See <xref linkend=\"batch\"/> for some possible batch operation tricks."
+msgid "Hibernate does not offer its own API for direct execution of <literal>UPDATE</literal> or <literal>DELETE</literal> statements. Hibernate is a <emphasis>state management</emphasis> service, you do not have to think in <emphasis>statements</emphasis> to use it. JDBC is a perfect API for executing SQL statements, you can get a JDBC <literal>Connection</literal> at any time by calling <literal>session.connection()</literal>. Furthermore, the notion of mass operations conflicts with object/relational mapping for online transaction processing-oriented applications. Future versions of Hibernate can, however, provide special mass operation functions. See <xref linkend=\"batch\" /> for some possible batch operation tricks."
msgstr ""
#. Tag: title
-#: session_api.xml:546
#, no-c-format
msgid "Modifying detached objects"
msgstr ""
#. Tag: para
-#: session_api.xml:548
#, no-c-format
msgid "Many applications need to retrieve an object in one transaction, send it to the UI layer for manipulation, then save the changes in a new transaction. Applications that use this kind of approach in a high-concurrency environment usually use versioned data to ensure isolation for the \"long\" unit of work."
msgstr ""
#. Tag: para
-#: session_api.xml:555
#, no-c-format
msgid "Hibernate supports this model by providing for reattachment of detached instances using the <literal>Session.update()</literal> or <literal>Session.merge()</literal> methods:"
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:561
-#, no-c-format
-msgid ""
- "<![CDATA[// in the first session\n"
- "Cat cat = (Cat) firstSession.load(Cat.class, catId);\n"
- "Cat potentialMate = new Cat();\n"
- "firstSession.save(potentialMate);\n"
- "\n"
- "// in a higher layer of the application\n"
- "cat.setMate(potentialMate);\n"
- "\n"
- "// later, in a new session\n"
- "secondSession.update(cat); // update cat\n"
- "secondSession.update(mate); // update mate]]>"
-msgstr ""
-
#. Tag: para
-#: session_api.xml:563
#, no-c-format
msgid "If the <literal>Cat</literal> with identifier <literal>catId</literal> had already been loaded by <literal>secondSession</literal> when the application tried to reattach it, an exception would have been thrown."
msgstr ""
#. Tag: para
-#: session_api.xml:569
#, no-c-format
msgid "Use <literal>update()</literal> if you are certain that the session does not contain an already persistent instance with the same identifier. Use <literal>merge()</literal> if you want to merge your modifications at any time without consideration of the state of the session. In other words, <literal>update()</literal> is usually the first method you would call in a fresh session, ensuring that the reattachment of your detached instances is the first operation that is executed."
msgstr ""
#. Tag: para
-#: session_api.xml:578
#, no-c-format
-msgid "The application should individually <literal>update()</literal> detached instances that are reachable from the given detached instance <emphasis>only</emphasis> if it wants their state to be updated. This can be automated using <emphasis>transitive persistence</emphasis>. See <xref linkend=\"objectstate-transitive\"/> for more information."
+msgid "The application should individually <literal>update()</literal> detached instances that are reachable from the given detached instance <emphasis>only</emphasis> if it wants their state to be updated. This can be automated using <emphasis>transitive persistence</emphasis>. See <xref linkend=\"objectstate-transitive\" /> for more information."
msgstr ""
#. Tag: para
-#: session_api.xml:585
#, no-c-format
msgid "The <literal>lock()</literal> method also allows an application to reassociate an object with a new session. However, the detached instance has to be unmodified."
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:590
-#, no-c-format
-msgid ""
- "<![CDATA[//just reassociate:\n"
- "sess.lock(fritz, LockMode.NONE);\n"
- "//do a version check, then reassociate:\n"
- "sess.lock(izi, LockMode.READ);\n"
- "//do a version check, using SELECT ... FOR UPDATE, then reassociate:\n"
- "sess.lock(pk, LockMode.UPGRADE);]]>"
-msgstr ""
-
#. Tag: para
-#: session_api.xml:592
#, no-c-format
msgid "Note that <literal>lock()</literal> can be used with various <literal>LockMode</literal>s. See the API documentation and the chapter on transaction handling for more information. Reattachment is not the only usecase for <literal>lock()</literal>."
msgstr ""
#. Tag: para
-#: session_api.xml:599
#, no-c-format
-msgid "Other models for long units of work are discussed in <xref linkend=\"transactions-optimistic\"/>."
+msgid "Other models for long units of work are discussed in <xref linkend=\"transactions-optimistic\" />."
msgstr ""
#. Tag: title
-#: session_api.xml:606
#, no-c-format
msgid "Automatic state detection"
msgstr ""
#. Tag: para
-#: session_api.xml:608
#, no-c-format
msgid "Hibernate users have requested a general purpose method that either saves a transient instance by generating a new identifier or updates/reattaches the detached instances associated with its current identifier. The <literal>saveOrUpdate()</literal> method implements this functionality."
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:615
-#, no-c-format
-msgid ""
- "<![CDATA[// in the first session\n"
- "Cat cat = (Cat) firstSession.load(Cat.class, catID);\n"
- "\n"
- "// in a higher tier of the application\n"
- "Cat mate = new Cat();\n"
- "cat.setMate(mate);\n"
- "\n"
- "// later, in a new session\n"
- "secondSession.saveOrUpdate(cat); // update existing state (cat has a non-null id)\n"
- "secondSession.saveOrUpdate(mate); // save the new instance (mate has a null id)]]>"
-msgstr ""
-
#. Tag: para
-#: session_api.xml:617
#, no-c-format
msgid "The usage and semantics of <literal>saveOrUpdate()</literal> seems to be confusing for new users. Firstly, so long as you are not trying to use instances from one session in another new session, you should not need to use <literal>update()</literal>, <literal>saveOrUpdate()</literal>, or <literal>merge()</literal>. Some whole applications will never use either of these methods."
msgstr ""
#. Tag: para
-#: session_api.xml:625
#, no-c-format
msgid "Usually <literal>update()</literal> or <literal>saveOrUpdate()</literal> are used in the following scenario:"
msgstr ""
#. Tag: para
-#: session_api.xml:632
#, no-c-format
msgid "the application loads an object in the first session"
msgstr ""
#. Tag: para
-#: session_api.xml:637
#, no-c-format
msgid "the object is passed up to the UI tier"
msgstr ""
#. Tag: para
-#: session_api.xml:642
#, no-c-format
msgid "some modifications are made to the object"
msgstr ""
#. Tag: para
-#: session_api.xml:647
#, no-c-format
msgid "the object is passed back down to the business logic tier"
msgstr ""
#. Tag: para
-#: session_api.xml:652
#, no-c-format
msgid "the application persists these modifications by calling <literal>update()</literal> in a second session"
msgstr ""
#. Tag: para
-#: session_api.xml:659
#, no-c-format
msgid "<literal>saveOrUpdate()</literal> does the following:"
msgstr ""
#. Tag: para
-#: session_api.xml:665
#, no-c-format
msgid "if the object is already persistent in this session, do nothing"
msgstr ""
#. Tag: para
-#: session_api.xml:670
#, no-c-format
msgid "if another object associated with the session has the same identifier, throw an exception"
msgstr ""
#. Tag: para
-#: session_api.xml:676
#, no-c-format
msgid "if the object has no identifier property, <literal>save()</literal> it"
msgstr ""
#. Tag: para
-#: session_api.xml:681
#, no-c-format
msgid "if the object's identifier has the value assigned to a newly instantiated object, <literal>save()</literal> it"
msgstr ""
#. Tag: para
-#: session_api.xml:687
#, no-c-format
msgid "if the object is versioned by a <literal><version></literal> or <literal><timestamp></literal>, and the version property value is the same value assigned to a newly instantiated object, <literal>save()</literal> it"
msgstr ""
#. Tag: para
-#: session_api.xml:695
#, no-c-format
msgid "otherwise <literal>update()</literal> the object"
msgstr ""
#. Tag: para
-#: session_api.xml:701
#, no-c-format
msgid "and <literal>merge()</literal> is very different:"
msgstr ""
#. Tag: para
-#: session_api.xml:707
#, no-c-format
msgid "if there is a persistent instance with the same identifier currently associated with the session, copy the state of the given object onto the persistent instance"
msgstr ""
#. Tag: para
-#: session_api.xml:714
#, no-c-format
msgid "if there is no persistent instance currently associated with the session, try to load it from the database, or create a new persistent instance"
msgstr ""
#. Tag: para
-#: session_api.xml:720
#, no-c-format
msgid "the persistent instance is returned"
msgstr ""
#. Tag: para
-#: session_api.xml:725
#, no-c-format
msgid "the given instance does not become associated with the session, it remains detached"
msgstr ""
#. Tag: title
-#: session_api.xml:735
#, no-c-format
msgid "Deleting persistent objects"
msgstr ""
#. Tag: para
-#: session_api.xml:737
#, no-c-format
msgid "<literal>Session.delete()</literal> will remove an object's state from the database. Your application, however, can still hold a reference to a deleted object. It is best to think of <literal>delete()</literal> as making a persistent instance, transient."
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:744
-#, no-c-format
-msgid "<![CDATA[sess.delete(cat);]]>"
-msgstr ""
-
#. Tag: para
-#: session_api.xml:746
#, no-c-format
msgid "You can delete objects in any order, without risk of foreign key constraint violations. It is still possible to violate a <literal>NOT NULL</literal> constraint on a foreign key column by deleting objects in the wrong order, e.g. if you delete the parent, but forget to delete the children."
msgstr ""
#. Tag: title
-#: session_api.xml:757
#, no-c-format
msgid "Replicating object between two different datastores"
msgstr ""
#. Tag: para
-#: session_api.xml:759
#, no-c-format
msgid "It is sometimes useful to be able to take a graph of persistent instances and make them persistent in a different datastore, without regenerating identifier values."
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:765
-#, no-c-format
-msgid ""
- "<![CDATA[//retrieve a cat from one database\n"
- "Session session1 = factory1.openSession();\n"
- "Transaction tx1 = session1.beginTransaction();\n"
- "Cat cat = session1.get(Cat.class, catId);\n"
- "tx1.commit();\n"
- "session1.close();\n"
- "\n"
- "//reconcile with a second database\n"
- "Session session2 = factory2.openSession();\n"
- "Transaction tx2 = session2.beginTransaction();\n"
- "session2.replicate(cat, ReplicationMode.LATEST_VERSION);\n"
- "tx2.commit();\n"
- "session2.close();]]>"
-msgstr ""
-
#. Tag: para
-#: session_api.xml:767
#, no-c-format
msgid "The <literal>ReplicationMode</literal> determines how <literal>replicate()</literal> will deal with conflicts with existing rows in the database:"
msgstr ""
#. Tag: para
-#: session_api.xml:774
#, no-c-format
msgid "<literal>ReplicationMode.IGNORE</literal>: ignores the object when there is an existing database row with the same identifier"
msgstr ""
#. Tag: para
-#: session_api.xml:780
#, no-c-format
msgid "<literal>ReplicationMode.OVERWRITE</literal>: overwrites any existing database row with the same identifier"
msgstr ""
#. Tag: para
-#: session_api.xml:786
#, no-c-format
msgid "<literal>ReplicationMode.EXCEPTION</literal>: throws an exception if there is an existing database row with the same identifier"
msgstr ""
#. Tag: para
-#: session_api.xml:792
#, no-c-format
msgid "<literal>ReplicationMode.LATEST_VERSION</literal>: overwrites the row if its version number is earlier than the version number of the object, or ignore the object otherwise"
msgstr ""
#. Tag: para
-#: session_api.xml:800
#, no-c-format
msgid "Usecases for this feature include reconciling data entered into different database instances, upgrading system configuration information during product upgrades, rolling back changes made during non-ACID transactions and more."
msgstr ""
#. Tag: title
-#: session_api.xml:809
#, no-c-format
msgid "Flushing the Session"
msgstr ""
#. Tag: para
-#: session_api.xml:811
#, no-c-format
msgid "Sometimes the <literal>Session</literal> will execute the SQL statements needed to synchronize the JDBC connection's state with the state of objects held in memory. This process, called <emphasis>flush</emphasis>, occurs by default at the following points:"
msgstr ""
#. Tag: para
-#: session_api.xml:820
#, no-c-format
msgid "before some query executions"
msgstr ""
#. Tag: para
-#: session_api.xml:825
#, no-c-format
msgid "from <literal>org.hibernate.Transaction.commit()</literal>"
msgstr ""
#. Tag: para
-#: session_api.xml:830
#, no-c-format
msgid "from <literal>Session.flush()</literal>"
msgstr ""
#. Tag: para
-#: session_api.xml:836
#, no-c-format
msgid "The SQL statements are issued in the following order:"
msgstr ""
#. Tag: para
-#: session_api.xml:842
#, no-c-format
msgid "all entity insertions in the same order the corresponding objects were saved using <literal>Session.save()</literal>"
msgstr ""
#. Tag: para
-#: session_api.xml:848
#, no-c-format
msgid "all entity updates"
msgstr ""
#. Tag: para
-#: session_api.xml:853
#, no-c-format
msgid "all collection deletions"
msgstr ""
#. Tag: para
-#: session_api.xml:858
#, no-c-format
msgid "all collection element deletions, updates and insertions"
msgstr ""
#. Tag: para
-#: session_api.xml:863
#, no-c-format
msgid "all collection insertions"
msgstr ""
#. Tag: para
-#: session_api.xml:868
#, no-c-format
msgid "all entity deletions in the same order the corresponding objects were deleted using <literal>Session.delete()</literal>"
msgstr ""
#. Tag: para
-#: session_api.xml:875
#, no-c-format
msgid "An exception is that objects using <literal>native</literal> ID generation are inserted when they are saved."
msgstr ""
#. Tag: para
-#: session_api.xml:880
#, no-c-format
msgid "Except when you explicitly <literal>flush()</literal>, there are absolutely no guarantees about <emphasis>when</emphasis> the <literal>Session</literal> executes the JDBC calls, only the <emphasis>order</emphasis> in which they are executed. However, Hibernate does guarantee that the <literal>Query.list(..)</literal> will never return stale or incorrect data."
msgstr ""
#. Tag: para
-#: session_api.xml:888
#, no-c-format
-msgid "It is possible to change the default behavior so that flush occurs less frequently. The <literal>FlushMode</literal> class defines three different modes: only flush at commit time when the Hibernate <literal>Transaction</literal> API is used, flush automatically using the explained routine, or never flush unless <literal>flush()</literal> is called explicitly. The last mode is useful for long running units of work, where a <literal>Session</literal> is kept open and disconnected for a long time (see <xref linkend=\"transactions-optimistic-longsession\"/>)."
+msgid "It is possible to change the default behavior so that flush occurs less frequently. The <literal>FlushMode</literal> class defines three different modes: only flush at commit time when the Hibernate <literal>Transaction</literal> API is used, flush automatically using the explained routine, or never flush unless <literal>flush()</literal> is called explicitly. The last mode is useful for long running units of work, where a <literal>Session</literal> is kept open and disconnected for a long time (see <xref linkend=\"transactions-optimistic-longsession\" />)."
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:898
-#, no-c-format
-msgid ""
- "<![CDATA[sess = sf.openSession();\n"
- "Transaction tx = sess.beginTransaction();\n"
- "sess.setFlushMode(FlushMode.COMMIT); // allow queries to return stale state\n"
- "\n"
- "Cat izi = (Cat) sess.load(Cat.class, id);\n"
- "izi.setName(iznizi);\n"
- "\n"
- "// might return stale data\n"
- "sess.find(\"from Cat as cat left outer join cat.kittens kitten\");\n"
- "\n"
- "// change to izi is not flushed!\n"
- "...\n"
- "tx.commit(); // flush occurs\n"
- "sess.close();]]>"
-msgstr ""
-
#. Tag: para
-#: session_api.xml:900
#, no-c-format
-msgid "During flush, an exception might occur (e.g. if a DML operation violates a constraint). Since handling exceptions involves some understanding of Hibernate's transactional behavior, we discuss it in <xref linkend=\"transactions\"/>."
+msgid "During flush, an exception might occur (e.g. if a DML operation violates a constraint). Since handling exceptions involves some understanding of Hibernate's transactional behavior, we discuss it in <xref linkend=\"transactions\" />."
msgstr ""
#. Tag: title
-#: session_api.xml:909
#, no-c-format
msgid "Transitive persistence"
msgstr ""
#. Tag: para
-#: session_api.xml:911
#, no-c-format
msgid "It is quite cumbersome to save, delete, or reattach individual objects, especially if you deal with a graph of associated objects. A common case is a parent/child relationship. Consider the following example:"
msgstr ""
#. Tag: para
-#: session_api.xml:917
#, no-c-format
msgid "If the children in a parent/child relationship would be value typed (e.g. a collection of addresses or strings), their life cycle would depend on the parent and no further action would be required for convenient \"cascading\" of state changes. When the parent is saved, the value-typed child objects are saved and when the parent is deleted, the children will be deleted, etc. This works for operations such as the removal of a child from the collection. Since value-typed objects cannot have shared references, Hibernate will detect this and delete the child from the database."
msgstr ""
#. Tag: para
-#: session_api.xml:928
#, no-c-format
msgid "Now consider the same scenario with parent and child objects being entities, not value-types (e.g. categories and items, or parent and child cats). Entities have their own life cycle and support shared references. Removing an entity from the collection does not mean it can be deleted), and there is by default no cascading of state from one entity to any other associated entities. Hibernate does not implement <emphasis>persistence by reachability</emphasis> by default."
msgstr ""
#. Tag: para
-#: session_api.xml:937
#, no-c-format
msgid "For each basic operation of the Hibernate session - including <literal>persist(), merge(), saveOrUpdate(), delete(), lock(), refresh(), evict(), replicate()</literal> - there is a corresponding cascade style. Respectively, the cascade styles are named <literal>create, merge, save-update, delete, lock, refresh, evict, replicate</literal>. If you want an operation to be cascaded along an association, you must indicate that in the mapping document. For example:"
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:946
-#, no-c-format
-msgid "<![CDATA[<one-to-one name=\"person\" cascade=\"persist\"/>]]>"
-msgstr ""
-
#. Tag: para
-#: session_api.xml:948
#, no-c-format
msgid "Cascade styles my be combined:"
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:952
-#, no-c-format
-msgid "<![CDATA[<one-to-one name=\"person\" cascade=\"persist,delete,lock\"/>]]>"
-msgstr ""
-
#. Tag: para
-#: session_api.xml:954
#, no-c-format
msgid "You can even use <literal>cascade=\"all\"</literal> to specify that <emphasis>all</emphasis> operations should be cascaded along the association. The default <literal>cascade=\"none\"</literal> specifies that no operations are to be cascaded."
msgstr ""
#. Tag: para
-#: session_api.xml:960
#, no-c-format
msgid "A special cascade style, <literal>delete-orphan</literal>, applies only to one-to-many associations, and indicates that the <literal>delete()</literal> operation should be applied to any child object that is removed from the association."
msgstr ""
#. Tag: para
-#: session_api.xml:967
#, no-c-format
msgid "Recommendations:"
msgstr ""
#. Tag: para
-#: session_api.xml:973
#, no-c-format
msgid "It does not usually make sense to enable cascade on a <literal><many-to-one></literal> or <literal><many-to-many></literal> association. Cascade is often useful for <literal><one-to-one></literal> and <literal><one-to-many></literal> associations."
msgstr ""
#. Tag: para
-#: session_api.xml:981
#, no-c-format
msgid "If the child object's lifespan is bounded by the lifespan of the parent object, make it a <emphasis>life cycle object</emphasis> by specifying <literal>cascade=\"all,delete-orphan\"</literal>."
msgstr ""
#. Tag: para
-#: session_api.xml:988
#, no-c-format
msgid "Otherwise, you might not need cascade at all. But if you think that you will often be working with the parent and children together in the same transaction, and you want to save yourself some typing, consider using <literal>cascade=\"persist,merge,save-update\"</literal>."
msgstr ""
#. Tag: para
-#: session_api.xml:996
#, no-c-format
msgid "Mapping an association (either a single valued association, or a collection) with <literal>cascade=\"all\"</literal> marks the association as a <emphasis>parent/child</emphasis> style relationship where save/update/delete of the parent results in save/update/delete of the child or children."
msgstr ""
#. Tag: para
-#: session_api.xml:1002
#, no-c-format
msgid "Furthermore, a mere reference to a child from a persistent parent will result in save/update of the child. This metaphor is incomplete, however. A child which becomes unreferenced by its parent is <emphasis>not</emphasis> automatically deleted, except in the case of a <literal><one-to-many></literal> association mapped with <literal>cascade=\"delete-orphan\"</literal>. The precise semantics of cascading operations for a parent/child relationship are as follows:"
msgstr ""
#. Tag: para
-#: session_api.xml:1013
#, no-c-format
msgid "If a parent is passed to <literal>persist()</literal>, all children are passed to <literal>persist()</literal>"
msgstr ""
#. Tag: para
-#: session_api.xml:1019
#, no-c-format
msgid "If a parent is passed to <literal>merge()</literal>, all children are passed to <literal>merge()</literal>"
msgstr ""
#. Tag: para
-#: session_api.xml:1025
#, no-c-format
msgid "If a parent is passed to <literal>save()</literal>, <literal>update()</literal> or <literal>saveOrUpdate()</literal>, all children are passed to <literal>saveOrUpdate()</literal>"
msgstr ""
#. Tag: para
-#: session_api.xml:1031
#, no-c-format
msgid "If a transient or detached child becomes referenced by a persistent parent, it is passed to <literal>saveOrUpdate()</literal>"
msgstr ""
#. Tag: para
-#: session_api.xml:1037
#, no-c-format
msgid "If a parent is deleted, all children are passed to <literal>delete()</literal>"
msgstr ""
#. Tag: para
-#: session_api.xml:1042
#, no-c-format
msgid "If a child is dereferenced by a persistent parent, <emphasis>nothing special happens</emphasis> - the application should explicitly delete the child if necessary - unless <literal>cascade=\"delete-orphan\"</literal>, in which case the \"orphaned\" child is deleted."
msgstr ""
#. Tag: para
-#: session_api.xml:1051
#, no-c-format
msgid "Finally, note that cascading of operations can be applied to an object graph at <emphasis>call time</emphasis> or at <emphasis>flush time</emphasis>. All operations, if enabled, are cascaded to associated entities reachable when the operation is executed. However, <literal>save-update</literal> and <literal>delete-orphan</literal> are transitive for all associated entities reachable during flush of the <literal>Session</literal>."
msgstr ""
#. Tag: title
-#: session_api.xml:1063
#, no-c-format
msgid "Using metadata"
msgstr ""
#. Tag: para
-#: session_api.xml:1065
#, no-c-format
msgid "Hibernate requires a rich meta-level model of all entity and value types. This model can be useful to the application itself. For example, the application might use Hibernate's metadata to implement a \"smart\" deep-copy algorithm that understands which objects should be copied (eg. mutable value types) and which objects that should not (e.g. immutable value types and, possibly, associated entities)."
msgstr ""
#. Tag: para
-#: session_api.xml:1072
#, no-c-format
msgid "Hibernate exposes metadata via the <literal>ClassMetadata</literal> and <literal>CollectionMetadata</literal> interfaces and the <literal>Type</literal> hierarchy. Instances of the metadata interfaces can be obtained from the <literal>SessionFactory</literal>."
msgstr ""
-#. Tag: programlisting
-#: session_api.xml:1079
-#, no-c-format
-msgid ""
- "<![CDATA[Cat fritz = ......;\n"
- "ClassMetadata catMeta = sessionfactory.getClassMetadata(Cat.class);\n"
- "\n"
- "Object[] propertyValues = catMeta.getPropertyValues(fritz);\n"
- "String[] propertyNames = catMeta.getPropertyNames();\n"
- "Type[] propertyTypes = catMeta.getPropertyTypes();\n"
- "\n"
- "// get a Map of all properties which are not collections or associations\n"
- "Map namedValues = new HashMap();\n"
- "for ( int i=0; i<propertyNames.length; i++ ) {\n"
- " if ( !propertyTypes[i].isEntityType() && !propertyTypes[i].isCollectionType() ) {\n"
- " namedValues.put( propertyNames[i], propertyValues[i] );\n"
- " }\n"
- "}]]>"
-msgstr ""
-
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/toolset_guide.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/toolset_guide.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/toolset_guide.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,956 +1,634 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-10 21:02+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:20\n"
+"PO-Revision-Date: 2010-01-08T04:07:20\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
-#: toolset_guide.xml:29
#, no-c-format
msgid "Toolset Guide"
msgstr ""
#. Tag: para
-#: toolset_guide.xml:31
#, no-c-format
msgid "Roundtrip engineering with Hibernate is possible using a set of Eclipse plugins, commandline tools, and Ant tasks."
msgstr ""
#. Tag: para
-#: toolset_guide.xml:36
#, no-c-format
msgid "<emphasis>Hibernate Tools</emphasis> currently include plugins for the Eclipse IDE as well as Ant tasks for reverse engineering of existing databases:"
msgstr ""
#. Tag: para
-#: toolset_guide.xml:42
#, no-c-format
msgid "<emphasis>Mapping Editor:</emphasis> an editor for Hibernate XML mapping files that supports auto-completion and syntax highlighting. It also supports semantic auto-completion for class names and property/field names, making it more versatile than a normal XML editor."
msgstr ""
#. Tag: para
-#: toolset_guide.xml:47
#, no-c-format
msgid "<emphasis>Console:</emphasis> the console is a new view in Eclipse. In addition to a tree overview of your console configurations, you are also provided with an interactive view of your persistent classes and their relationships. The console allows you to execute HQL queries against your database and browse the result directly in Eclipse."
msgstr ""
#. Tag: para
-#: toolset_guide.xml:54
#, no-c-format
msgid "<emphasis>Development Wizards:</emphasis> several wizards are provided with the Hibernate Eclipse tools. You can use a wizard to quickly generate Hibernate configuration (cfg.xml) files, or to reverse engineer an existing database schema into POJO source files and Hibernate mapping files. The reverse engineering wizard supports customizable templates."
msgstr ""
#. Tag: para
-#: toolset_guide.xml:67
#, no-c-format
+msgid "<!-- <emphasis>Ant Tasks:</emphasis> -->"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
msgid "Please refer to the <emphasis>Hibernate Tools</emphasis> package documentation for more information."
msgstr ""
#. Tag: para
-#: toolset_guide.xml:72
#, no-c-format
msgid "However, the Hibernate main package comes bundled with an integrated tool : <emphasis>SchemaExport</emphasis> aka <literal>hbm2ddl</literal>.It can even be used from \"inside\" Hibernate."
msgstr ""
#. Tag: title
-#: toolset_guide.xml:79
#, no-c-format
msgid "Automatic schema generation"
msgstr ""
#. Tag: para
-#: toolset_guide.xml:81
#, no-c-format
msgid "DDL can be generated from your mapping files by a Hibernate utility. The generated schema includes referential integrity constraints, primary and foreign keys, for entity and collection tables. Tables and sequences are also created for mapped identifier generators."
msgstr ""
#. Tag: para
-#: toolset_guide.xml:88
#, no-c-format
msgid "You <emphasis>must</emphasis> specify a SQL <literal>Dialect</literal> via the <literal>hibernate.dialect</literal> property when using this tool, as DDL is highly vendor-specific."
msgstr ""
#. Tag: para
-#: toolset_guide.xml:94
#, no-c-format
msgid "First, you must customize your mapping files to improve the generated schema. The next section covers schema customization."
msgstr ""
#. Tag: title
-#: toolset_guide.xml:99
#, no-c-format
msgid "Customizing the schema"
msgstr ""
#. Tag: para
-#: toolset_guide.xml:101
#, no-c-format
msgid "Many Hibernate mapping elements define optional attributes named <literal>length</literal>, <literal>precision</literal> and <literal>scale</literal>. You can set the length, precision and scale of a column with this attribute."
msgstr ""
-#. Tag: programlisting
-#: toolset_guide.xml:108
-#, no-c-format
-msgid "<![CDATA[<property name=\"zip\" length=\"5\"/>]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: toolset_guide.xml:109
-#, no-c-format
-msgid "<![CDATA[<property name=\"balance\" precision=\"12\" scale=\"2\"/>]]>"
-msgstr ""
-
#. Tag: para
-#: toolset_guide.xml:111
#, no-c-format
msgid "Some tags also accept a <literal>not-null</literal> attribute for generating a <literal>NOT NULL</literal> constraint on table columns, and a <literal>unique</literal> attribute for generating <literal>UNIQUE</literal> constraint on table columns."
msgstr ""
-#. Tag: programlisting
-#: toolset_guide.xml:117
-#, no-c-format
-msgid "<![CDATA[<many-to-one name=\"bar\" column=\"barId\" not-null=\"true\"/>]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: toolset_guide.xml:119
-#, no-c-format
-msgid "<![CDATA[<element column=\"serialNumber\" type=\"long\" not-null=\"true\" unique=\"true\"/>]]>"
-msgstr ""
-
#. Tag: para
-#: toolset_guide.xml:121
#, no-c-format
msgid "A <literal>unique-key</literal> attribute can be used to group columns in a single, unique key constraint. Currently, the specified value of the <literal>unique-key</literal> attribute is <emphasis>not</emphasis> used to name the constraint in the generated DDL. It is only used to group the columns in the mapping file."
msgstr ""
-#. Tag: programlisting
-#: toolset_guide.xml:129
-#, no-c-format
-msgid ""
- "<![CDATA[<many-to-one name=\"org\" column=\"orgId\" unique-key=\"OrgEmployeeId\"/>\n"
- "<property name=\"employeeId\" unique-key=\"OrgEmployee\"/>]]>"
-msgstr ""
-
#. Tag: para
-#: toolset_guide.xml:131
#, no-c-format
msgid "An <literal>index</literal> attribute specifies the name of an index that will be created using the mapped column or columns. Multiple columns can be grouped into the same index by simply specifying the same index name."
msgstr ""
-#. Tag: programlisting
-#: toolset_guide.xml:137
-#, no-c-format
-msgid ""
- "<![CDATA[<property name=\"lastName\" index=\"CustName\"/>\n"
- "<property name=\"firstName\" index=\"CustName\"/>]]>"
-msgstr ""
-
#. Tag: para
-#: toolset_guide.xml:139
#, no-c-format
msgid "A <literal>foreign-key</literal> attribute can be used to override the name of any generated foreign key constraint."
msgstr ""
-#. Tag: programlisting
-#: toolset_guide.xml:144
-#, no-c-format
-msgid "<![CDATA[<many-to-one name=\"bar\" column=\"barId\" foreign-key=\"FKFooBar\"/>]]>"
-msgstr ""
-
#. Tag: para
-#: toolset_guide.xml:146
#, no-c-format
msgid "Many mapping elements also accept a child <literal><column></literal> element. This is particularly useful for mapping multi-column types:"
msgstr ""
-#. Tag: programlisting
-#: toolset_guide.xml:151
-#, no-c-format
-msgid ""
- "<![CDATA[<property name=\"name\" type=\"my.customtypes.Name\"/>\n"
- " <column name=\"last\" not-null=\"true\" index=\"bar_idx\" length=\"30\"/>\n"
- " <column name=\"first\" not-null=\"true\" index=\"bar_idx\" length=\"20\"/>\n"
- " <column name=\"initial\"/>\n"
- "</property>]]>"
-msgstr ""
-
#. Tag: para
-#: toolset_guide.xml:153
#, no-c-format
msgid "The <literal>default</literal> attribute allows you to specify a default value for a column.You should assign the same value to the mapped property before saving a new instance of the mapped class."
msgstr ""
-#. Tag: programlisting
-#: toolset_guide.xml:159
-#, no-c-format
-msgid ""
- "<![CDATA[<property name=\"credits\" type=\"integer\" insert=\"false\">\n"
- " <column name=\"credits\" default=\"10\"/>\n"
- "</property>]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: toolset_guide.xml:161
-#, no-c-format
-msgid ""
- "<![CDATA[<version name=\"version\" type=\"integer\" insert=\"false\">\n"
- " <column name=\"version\" default=\"0\"/>\n"
- "</property>]]>"
-msgstr ""
-
#. Tag: para
-#: toolset_guide.xml:163
#, no-c-format
msgid "The <literal>sql-type</literal> attribute allows the user to override the default mapping of a Hibernate type to SQL datatype."
msgstr ""
-#. Tag: programlisting
-#: toolset_guide.xml:168
-#, no-c-format
-msgid ""
- "<![CDATA[<property name=\"balance\" type=\"float\">\n"
- " <column name=\"balance\" sql-type=\"decimal(13,3)\"/>\n"
- "</property>]]>"
-msgstr ""
-
#. Tag: para
-#: toolset_guide.xml:170
#, no-c-format
msgid "The <literal>check</literal> attribute allows you to specify a check constraint."
msgstr ""
-#. Tag: programlisting
-#: toolset_guide.xml:174
-#, no-c-format
-msgid ""
- "<![CDATA[<property name=\"foo\" type=\"integer\">\n"
- " <column name=\"foo\" check=\"foo > 10\"/>\n"
- "</property>]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: toolset_guide.xml:176
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Foo\" table=\"foos\" check=\"bar < 100.0\">\n"
- " ...\n"
- " <property name=\"bar\" type=\"float\"/>\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: toolset_guide.xml:179
#, no-c-format
msgid "The following table summarizes these optional attributes."
msgstr ""
#. Tag: title
-#: toolset_guide.xml:182
#, no-c-format
msgid "Summary"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:189
+#. Tag: para
#, no-c-format
msgid "Attribute"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:190
+#. Tag: para
#, no-c-format
msgid "Values"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:191
+#. Tag: para
#, no-c-format
msgid "Interpretation"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:196
+#. Tag: para
#, no-c-format
-msgid "length"
+msgid "<literal>length</literal>"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:197 toolset_guide.xml:202 toolset_guide.xml:207
+#. Tag: para
#, no-c-format
msgid "number"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:198
+#. Tag: para
#, no-c-format
msgid "column length"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:201
+#. Tag: para
#, no-c-format
-msgid "precision"
+msgid "<literal>precision</literal>"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:203
+#. Tag: para
#, no-c-format
msgid "column decimal precision"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:206
+#. Tag: para
#, no-c-format
-msgid "scale"
+msgid "<literal>scale</literal>"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:208
+#. Tag: para
#, no-c-format
msgid "column decimal scale"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:211
+#. Tag: para
#, no-c-format
-msgid "not-null"
+msgid "<literal>not-null</literal>"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:212 toolset_guide.xml:217
+#. Tag: para
#, no-c-format
-msgid "true|false"
+msgid "<literal>true|false</literal>"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:213
+#. Tag: para
#, no-c-format
msgid "specifies that the column should be non-nullable"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:216
+#. Tag: para
#, no-c-format
-msgid "unique"
+msgid "<literal>unique</literal>"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:218
+#. Tag: para
#, no-c-format
msgid "specifies that the column should have a unique constraint"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:221
+#. Tag: para
#, no-c-format
-msgid "index"
+msgid "<literal>index</literal>"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:222
+#. Tag: para
#, no-c-format
-msgid "index_name"
+msgid "<literal>index_name</literal>"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:223
+#. Tag: para
#, no-c-format
msgid "specifies the name of a (multi-column) index"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:226
+#. Tag: para
#, no-c-format
-msgid "unique-key"
+msgid "<literal>unique-key</literal>"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:227
+#. Tag: para
#, no-c-format
-msgid "unique_key_name"
+msgid "<literal>unique_key_name</literal>"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:228
+#. Tag: para
#, no-c-format
msgid "specifies the name of a multi-column unique constraint"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:231
+#. Tag: para
#, no-c-format
-msgid "foreign-key"
+msgid "<literal>foreign-key</literal>"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:232
+#. Tag: para
#, no-c-format
-msgid "foreign_key_name"
+msgid "<literal>foreign_key_name</literal>"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:233
+#. Tag: para
#, no-c-format
msgid "specifies the name of the foreign key constraint generated for an association, for a <literal><one-to-one></literal>, <literal><many-to-one></literal>, <literal><key></literal>, or <literal><many-to-many></literal> mapping element. Note that <literal>inverse=\"true\"</literal> sides will not be considered by <literal>SchemaExport</literal>."
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:243
+#. Tag: para
#, no-c-format
-msgid "sql-type"
+msgid "<literal>sql-type</literal>"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:244
+#. Tag: para
#, no-c-format
-msgid "SQL column type"
+msgid "<literal>SQL column type</literal>"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:245
+#. Tag: para
#, no-c-format
msgid "overrides the default column type (attribute of <literal><column></literal> element only)"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:251
+#. Tag: para
#, no-c-format
-msgid "default"
+msgid "<literal>default</literal>"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:252 toolset_guide.xml:259
+#. Tag: para
#, no-c-format
msgid "SQL expression"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:253
+#. Tag: para
#, no-c-format
msgid "specify a default value for the column"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:258
+#. Tag: para
#, no-c-format
-msgid "check"
+msgid "<literal>check</literal>"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:260
+#. Tag: para
#, no-c-format
msgid "create an SQL check constraint on either column or table"
msgstr ""
#. Tag: para
-#: toolset_guide.xml:268
#, no-c-format
msgid "The <literal><comment></literal> element allows you to specify comments for the generated schema."
msgstr ""
-#. Tag: programlisting
-#: toolset_guide.xml:273
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Customer\" table=\"CurCust\">\n"
- " <comment>Current customers only</comment>\n"
- " ...\n"
- "</class>]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: toolset_guide.xml:275
-#, no-c-format
-msgid ""
- "<![CDATA[<property name=\"balance\">\n"
- " <column name=\"bal\">\n"
- " <comment>Balance in USD</comment>\n"
- " </column>\n"
- "</property>]]>"
-msgstr ""
-
#. Tag: para
-#: toolset_guide.xml:277
#, no-c-format
msgid "This results in a <literal>comment on table</literal> or <literal>comment on column</literal> statement in the generated DDL where supported."
msgstr ""
#. Tag: title
-#: toolset_guide.xml:286
#, no-c-format
msgid "Running the tool"
msgstr ""
#. Tag: para
-#: toolset_guide.xml:288
#, no-c-format
msgid "The <literal>SchemaExport</literal> tool writes a DDL script to standard out and/or executes the DDL statements."
msgstr ""
#. Tag: para
-#: toolset_guide.xml:293
#, no-c-format
msgid "The following table displays the <literal>SchemaExport</literal> command line options"
msgstr ""
#. Tag: para
-#: toolset_guide.xml:295
#, no-c-format
msgid "<literal>java -cp </literal><emphasis>hibernate_classpaths</emphasis> <literal>org.hibernate.tool.hbm2ddl.SchemaExport</literal> <emphasis>options mapping_files</emphasis>"
msgstr ""
#. Tag: title
-#: toolset_guide.xml:301
#, no-c-format
msgid "<literal>SchemaExport</literal> Command Line Options"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:307 toolset_guide.xml:457 toolset_guide.xml:526
+#. Tag: para
#, no-c-format
msgid "Option"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:308 toolset_guide.xml:395 toolset_guide.xml:458 toolset_guide.xml:527
+#. Tag: para
#, no-c-format
msgid "Description"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:313 toolset_guide.xml:463
+#. Tag: para
#, no-c-format
-msgid "--quiet"
+msgid "<literal>--quiet</literal>"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:314 toolset_guide.xml:464
+#. Tag: para
#, no-c-format
msgid "do not output the script to stdout"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:317
+#. Tag: para
#, no-c-format
-msgid "--drop"
+msgid "<literal>--drop</literal>"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:318
+#. Tag: para
#, no-c-format
msgid "only drop the tables"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:321
+#. Tag: para
#, no-c-format
-msgid "--create"
+msgid "<literal>--create</literal>"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:322
+#. Tag: para
#, no-c-format
msgid "only create the tables"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:325 toolset_guide.xml:467
+#. Tag: para
#, no-c-format
-msgid "--text"
+msgid "<literal>--text</literal>"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:326
+#. Tag: para
#, no-c-format
msgid "do not export to the database"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:329
+#. Tag: para
#, no-c-format
-msgid "--output=my_schema.ddl"
+msgid "<literal>--output=my_schema.ddl</literal>"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:330
+#. Tag: para
#, no-c-format
msgid "output the ddl script to a file"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:333 toolset_guide.xml:471 toolset_guide.xml:532
+#. Tag: para
#, no-c-format
-msgid "--naming=eg.MyNamingStrategy"
+msgid "<literal>--naming=eg.MyNamingStrategy</literal>"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:334 toolset_guide.xml:472 toolset_guide.xml:533
+#. Tag: para
#, no-c-format
msgid "select a <literal>NamingStrategy</literal>"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:337 toolset_guide.xml:479 toolset_guide.xml:540
+#. Tag: para
#, no-c-format
-msgid "--config=hibernate.cfg.xml"
+msgid "<literal>--config=hibernate.cfg.xml</literal>"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:338
+#. Tag: para
#, no-c-format
msgid "read Hibernate configuration from an XML file"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:341 toolset_guide.xml:475 toolset_guide.xml:536
+#. Tag: para
#, no-c-format
-msgid "--properties=hibernate.properties"
+msgid "<literal>--properties=hibernate.properties</literal>"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:342 toolset_guide.xml:476 toolset_guide.xml:537
+#. Tag: para
#, no-c-format
msgid "read database properties from a file"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:345
+#. Tag: para
#, no-c-format
-msgid "--format"
+msgid "<literal>--format</literal>"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:346
+#. Tag: para
#, no-c-format
msgid "format the generated SQL nicely in the script"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:349
+#. Tag: para
#, no-c-format
-msgid "--delimiter=;"
+msgid "<literal>--delimiter=;</literal>"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:350
+#. Tag: para
#, no-c-format
msgid "set an end of line delimiter for the script"
msgstr ""
#. Tag: para
-#: toolset_guide.xml:356
#, no-c-format
msgid "You can even embed <literal>SchemaExport</literal> in your application:"
msgstr ""
-#. Tag: programlisting
-#: toolset_guide.xml:360
-#, no-c-format
-msgid ""
- "<![CDATA[Configuration cfg = ....;\n"
- "new SchemaExport(cfg).create(false, true);]]>"
-msgstr ""
-
#. Tag: title
-#: toolset_guide.xml:365
#, no-c-format
msgid "Properties"
msgstr ""
#. Tag: para
-#: toolset_guide.xml:367
#, no-c-format
msgid "Database properties can be specified:"
msgstr ""
#. Tag: para
-#: toolset_guide.xml:373
#, no-c-format
msgid "as system properties with <literal>-D</literal><emphasis><property></emphasis>"
msgstr ""
#. Tag: para
-#: toolset_guide.xml:376
#, no-c-format
msgid "in <literal>hibernate.properties</literal>"
msgstr ""
#. Tag: para
-#: toolset_guide.xml:379
#, no-c-format
msgid "in a named properties file with <literal>--properties</literal>"
msgstr ""
#. Tag: para
-#: toolset_guide.xml:383
#, no-c-format
msgid "The needed properties are:"
msgstr ""
#. Tag: title
-#: toolset_guide.xml:388
#, no-c-format
msgid "SchemaExport Connection Properties"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:394
+#. Tag: para
#, no-c-format
msgid "Property Name"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:400
+#. Tag: para
#, no-c-format
-msgid "hibernate.connection.driver_class"
+msgid "<literal>hibernate.connection.driver_class</literal>"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:401
+#. Tag: para
#, no-c-format
msgid "jdbc driver class"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:404
+#. Tag: para
#, no-c-format
-msgid "hibernate.connection.url"
+msgid "<literal>hibernate.connection.url</literal>"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:405
+#. Tag: para
#, no-c-format
msgid "jdbc url"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:408
+#. Tag: para
#, no-c-format
-msgid "hibernate.connection.username"
+msgid "<literal>hibernate.connection.username</literal>"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:409
+#. Tag: para
#, no-c-format
msgid "database user"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:412
+#. Tag: para
#, no-c-format
-msgid "hibernate.connection.password"
+msgid "<literal>hibernate.connection.password</literal>"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:413
+#. Tag: para
#, no-c-format
msgid "user password"
msgstr ""
-#. Tag: literal
-#: toolset_guide.xml:416
+#. Tag: para
#, no-c-format
-msgid "hibernate.dialect"
+msgid "<literal>hibernate.dialect</literal>"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:417
+#. Tag: para
#, no-c-format
msgid "dialect"
msgstr ""
#. Tag: title
-#: toolset_guide.xml:426
#, no-c-format
msgid "Using Ant"
msgstr ""
#. Tag: para
-#: toolset_guide.xml:428
#, no-c-format
msgid "You can call <literal>SchemaExport</literal> from your Ant build script:"
msgstr ""
-#. Tag: programlisting
-#: toolset_guide.xml:432
-#, no-c-format
-msgid ""
- "<![CDATA[<target name=\"schemaexport\">\n"
- " <taskdef name=\"schemaexport\"\n"
- " classname=\"org.hibernate.tool.hbm2ddl.SchemaExportTask\"\n"
- " classpathref=\"class.path\"/>\n"
- " \n"
- " <schemaexport\n"
- " properties=\"hibernate.properties\"\n"
- " quiet=\"no\"\n"
- " text=\"no\"\n"
- " drop=\"no\"\n"
- " delimiter=\";\"\n"
- " output=\"schema-export.sql\">\n"
- " <fileset dir=\"src\">\n"
- " <include name=\"**/*.hbm.xml\"/>\n"
- " </fileset>\n"
- " </schemaexport>\n"
- "</target>]]>"
-msgstr ""
-
#. Tag: title
-#: toolset_guide.xml:437
#, no-c-format
msgid "Incremental schema updates"
msgstr ""
#. Tag: para
-#: toolset_guide.xml:439
#, no-c-format
msgid "The <literal>SchemaUpdate</literal> tool will update an existing schema with \"incremental\" changes. The <literal>SchemaUpdate</literal> depends upon the JDBC metadata API and, as such, will not work with all JDBC drivers."
msgstr ""
#. Tag: para
-#: toolset_guide.xml:445
#, no-c-format
msgid "<literal>java -cp </literal><emphasis>hibernate_classpaths</emphasis> <literal>org.hibernate.tool.hbm2ddl.SchemaUpdate</literal> <emphasis>options mapping_files</emphasis>"
msgstr ""
#. Tag: title
-#: toolset_guide.xml:451
#, no-c-format
msgid "<literal>SchemaUpdate</literal> Command Line Options"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:468
+#. Tag: para
#, no-c-format
msgid "do not export the script to the database"
msgstr ""
-#. Tag: entry
-#: toolset_guide.xml:480 toolset_guide.xml:541
+#. Tag: para
#, no-c-format
msgid "specify a <literal>.cfg.xml</literal> file"
msgstr ""
#. Tag: para
-#: toolset_guide.xml:486
#, no-c-format
msgid "You can embed <literal>SchemaUpdate</literal> in your application:"
msgstr ""
-#. Tag: programlisting
-#: toolset_guide.xml:490
-#, no-c-format
-msgid ""
- "<![CDATA[Configuration cfg = ....;\n"
- "new SchemaUpdate(cfg).execute(false);]]>"
-msgstr ""
-
#. Tag: title
-#: toolset_guide.xml:495
#, no-c-format
msgid "Using Ant for incremental schema updates"
msgstr ""
#. Tag: para
-#: toolset_guide.xml:497
#, no-c-format
msgid "You can call <literal>SchemaUpdate</literal> from the Ant script:"
msgstr ""
-#. Tag: programlisting
-#: toolset_guide.xml:501
-#, no-c-format
-msgid ""
- "<![CDATA[<target name=\"schemaupdate\">\n"
- " <taskdef name=\"schemaupdate\"\n"
- " classname=\"org.hibernate.tool.hbm2ddl.SchemaUpdateTask\"\n"
- " classpathref=\"class.path\"/>\n"
- " \n"
- " <schemaupdate\n"
- " properties=\"hibernate.properties\"\n"
- " quiet=\"no\">\n"
- " <fileset dir=\"src\">\n"
- " <include name=\"**/*.hbm.xml\"/>\n"
- " </fileset>\n"
- " </schemaupdate>\n"
- "</target>]]>"
-msgstr ""
-
#. Tag: title
-#: toolset_guide.xml:506
#, no-c-format
msgid "Schema validation"
msgstr ""
#. Tag: para
-#: toolset_guide.xml:508
#, no-c-format
msgid "The <literal>SchemaValidator</literal> tool will validate that the existing database schema \"matches\" your mapping documents. The <literal>SchemaValidator</literal> depends heavily upon the JDBC metadata API and, as such, will not work with all JDBC drivers. This tool is extremely useful for testing."
msgstr ""
#. Tag: para
-#: toolset_guide.xml:514
#, no-c-format
msgid "<literal>java -cp </literal><emphasis>hibernate_classpaths</emphasis> <literal>org.hibernate.tool.hbm2ddl.SchemaValidator</literal> <emphasis>options mapping_files</emphasis>"
msgstr ""
+#. Tag: para
+#, no-c-format
+msgid "The following table displays the <literal>SchemaValidator</literal> command line options:"
+msgstr ""
+
#. Tag: title
-#: toolset_guide.xml:520
#, no-c-format
msgid "<literal>SchemaValidator</literal> Command Line Options"
msgstr ""
#. Tag: para
-#: toolset_guide.xml:547
#, no-c-format
msgid "You can embed <literal>SchemaValidator</literal> in your application:"
msgstr ""
-#. Tag: programlisting
-#: toolset_guide.xml:551
-#, no-c-format
-msgid ""
- "<![CDATA[Configuration cfg = ....;\n"
- "new SchemaValidator(cfg).validate();]]>"
-msgstr ""
-
#. Tag: title
-#: toolset_guide.xml:556
#, no-c-format
msgid "Using Ant for schema validation"
msgstr ""
#. Tag: para
-#: toolset_guide.xml:558
#, no-c-format
msgid "You can call <literal>SchemaValidator</literal> from the Ant script:"
msgstr ""
-#. Tag: programlisting
-#: toolset_guide.xml:562
-#, no-c-format
-msgid ""
- "<![CDATA[<target name=\"schemavalidate\">\n"
- " <taskdef name=\"schemavalidator\"\n"
- " classname=\"org.hibernate.tool.hbm2ddl.SchemaValidatorTask\"\n"
- " classpathref=\"class.path\"/>\n"
- " \n"
- " <schemavalidator\n"
- " properties=\"hibernate.properties\">\n"
- " <fileset dir=\"src\">\n"
- " <include name=\"**/*.hbm.xml\"/>\n"
- " </fileset>\n"
- " </schemavalidator>\n"
- "</target>]]>"
-msgstr ""
-
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/transactions.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/transactions.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/transactions.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,960 +1,658 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-10 21:02+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:20\n"
+"PO-Revision-Date: 2010-01-08T04:07:20\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
-#: transactions.xml:29
#, no-c-format
msgid "Transactions and Concurrency"
msgstr ""
#. Tag: para
-#: transactions.xml:31
#, no-c-format
msgid "The most important point about Hibernate and concurrency control is that it is easy to understand. Hibernate directly uses JDBC connections and JTA resources without adding any additional locking behavior. It is recommended that you spend some time with the JDBC, ANSI, and transaction isolation specification of your database management system."
msgstr ""
#. Tag: para
-#: transactions.xml:38
#, no-c-format
msgid "Hibernate does not lock objects in memory. Your application can expect the behavior as defined by the isolation level of your database transactions. Through <literal>Session</literal>, which is also a transaction-scoped cache, Hibernate provides repeatable reads for lookup by identifier and entity queries and not reporting queries that return scalar values."
msgstr ""
#. Tag: para
-#: transactions.xml:46
#, no-c-format
msgid "In addition to versioning for automatic optimistic concurrency control, Hibernate also offers, using the <literal>SELECT FOR UPDATE</literal> syntax, a (minor) API for pessimistic locking of rows. Optimistic concurrency control and this API are discussed later in this chapter."
msgstr ""
#. Tag: para
-#: transactions.xml:53
#, no-c-format
msgid "The discussion of concurrency control in Hibernate begins with the granularity of <literal>Configuration</literal>, <literal>SessionFactory</literal>, and <literal>Session</literal>, as well as database transactions and long conversations."
msgstr ""
#. Tag: title
-#: transactions.xml:60
#, no-c-format
msgid "Session and transaction scopes"
msgstr ""
#. Tag: para
-#: transactions.xml:62
#, no-c-format
msgid "A <literal>SessionFactory</literal> is an expensive-to-create, threadsafe object, intended to be shared by all application threads. It is created once, usually on application startup, from a <literal>Configuration</literal> instance."
msgstr ""
#. Tag: para
-#: transactions.xml:68
#, no-c-format
msgid "A <literal>Session</literal> is an inexpensive, non-threadsafe object that should be used once and then discarded for: a single request, a conversation or a single unit of work. A <literal>Session</literal> will not obtain a JDBC <literal>Connection</literal>, or a <literal>Datasource</literal>, unless it is needed. It will not consume any resources until used."
msgstr ""
#. Tag: para
-#: transactions.xml:76
#, no-c-format
msgid "In order to reduce lock contention in the database, a database transaction has to be as short as possible. Long database transactions will prevent your application from scaling to a highly concurrent load. It is not recommended that you hold a database transaction open during user think time until the unit of work is complete."
msgstr ""
#. Tag: para
-#: transactions.xml:84
#, no-c-format
msgid "What is the scope of a unit of work? Can a single Hibernate <literal>Session</literal> span several database transactions, or is this a one-to-one relationship of scopes? When should you open and close a <literal>Session</literal> and how do you demarcate the database transaction boundaries? These questions are addressed in the following sections."
msgstr ""
#. Tag: title
-#: transactions.xml:92
#, no-c-format
msgid "Unit of work"
msgstr ""
#. Tag: para
-#: transactions.xml:94
#, no-c-format
-msgid "First, let's define a unit of work. A unit of work is a design pattern described by Martin Fowler as <quote> [maintaining] a list of objects affected by a business transaction and coordinates the writing out of changes and the resolution of concurrency problems. </quote><citation>PoEAA</citation> In other words, its a series of operations we wish to carry out against the database together. Basically, it is a transaction, though fulfilling a unit of work will often span multiple physical database transactions (see <xref linkend=\"transactions-basics-apptx\"/>). So really we are talking about a more abstract notion of a transaction. The term \"business transaction\" is also sometimes used in lieu of unit of work."
+msgid "First, let's define a unit of work. A unit of work is a design pattern described by Martin Fowler as <quote> [maintaining] a list of objects affected by a business transaction and coordinates the writing out of changes and the resolution of concurrency problems. </quote><citation>PoEAA</citation> In other words, its a series of operations we wish to carry out against the database together. Basically, it is a transaction, though fulfilling a unit of work will often span multiple physical database transactions (see <xref linkend=\"transactions-basics-apptx\" />). So really we are talking about a more abstract notion of a transaction. The term \"business transaction\" is also sometimes used in lieu of unit of work."
msgstr ""
#. Tag: para
-#: transactions.xml:111
#, no-c-format
msgid "Do not use the <emphasis>session-per-operation</emphasis> antipattern: do not open and close a <literal>Session</literal> for every simple database call in a single thread. The same is true for database transactions. Database calls in an application are made using a planned sequence; they are grouped into atomic units of work. This also means that auto-commit after every single SQL statement is useless in an application as this mode is intended for ad-hoc SQL console work. Hibernate disables, or expects the application server to disable, auto-commit mode immediately. Database transactions are never optional. All communication with a database has to occur inside a transaction. Auto-commit behavior for reading data should be avoided, as many small transactions are unlikely to perform better than one clearly defined unit of work. The latter is also more maintainable and extensible."
msgstr ""
#. Tag: para
-#: transactions.xml:126
#, no-c-format
msgid "The most common pattern in a multi-user client/server application is <emphasis>session-per-request</emphasis>. In this model, a request from the client is sent to the server, where the Hibernate persistence layer runs. A new Hibernate <literal>Session</literal> is opened, and all database operations are executed in this unit of work. On completion of the work, and once the response for the client has been prepared, the session is flushed and closed. Use a single database transaction to serve the clients request, starting and committing it when you open and close the <literal>Session</literal>. The relationship between the two is one-to-one and this model is a perfect fit for many applications."
msgstr ""
#. Tag: para
-#: transactions.xml:138
#, no-c-format
msgid "The challenge lies in the implementation. Hibernate provides built-in management of the \"current session\" to simplify this pattern. Start a transaction when a server request has to be processed, and end the transaction before the response is sent to the client. Common solutions are <literal>ServletFilter</literal>, AOP interceptor with a pointcut on the service methods, or a proxy/interception container. An EJB container is a standardized way to implement cross-cutting aspects such as transaction demarcation on EJB session beans, declaratively with CMT. If you use programmatic transaction demarcation, for ease of use and code portability use the Hibernate <literal>Transaction</literal> API shown later in this chapter."
msgstr ""
#. Tag: para
-#: transactions.xml:150
#, no-c-format
-msgid "Your application code can access a \"current session\" to process the request by calling <literal>sessionFactory.getCurrentSession()</literal>. You will always get a <literal>Session</literal> scoped to the current database transaction. This has to be configured for either resource-local or JTA environments, see <xref linkend=\"architecture-current-session\"/>."
+msgid "Your application code can access a \"current session\" to process the request by calling <literal>sessionFactory.getCurrentSession()</literal>. You will always get a <literal>Session</literal> scoped to the current database transaction. This has to be configured for either resource-local or JTA environments, see <xref linkend=\"architecture-current-session\" />."
msgstr ""
#. Tag: para
-#: transactions.xml:158
#, no-c-format
msgid "You can extend the scope of a <literal>Session</literal> and database transaction until the \"view has been rendered\". This is especially useful in servlet applications that utilize a separate rendering phase after the request has been processed. Extending the database transaction until view rendering, is achieved by implementing your own interceptor. However, this will be difficult if you rely on EJBs with container-managed transactions. A transaction will be completed when an EJB method returns, before rendering of any view can start. See the Hibernate website and forum for tips and examples relating to this <emphasis>Open Session in View</emphasis> pattern."
msgstr ""
#. Tag: title
-#: transactions.xml:173
#, no-c-format
msgid "Long conversations"
msgstr ""
#. Tag: para
-#: transactions.xml:175
#, no-c-format
msgid "The session-per-request pattern is not the only way of designing units of work. Many business processes require a whole series of interactions with the user that are interleaved with database accesses. In web and enterprise applications, it is not acceptable for a database transaction to span a user interaction. Consider the following example:"
msgstr ""
#. Tag: para
-#: transactions.xml:185
#, no-c-format
msgid "The first screen of a dialog opens. The data seen by the user has been loaded in a particular <literal>Session</literal> and database transaction. The user is free to modify the objects."
msgstr ""
#. Tag: para
-#: transactions.xml:192
#, no-c-format
msgid "The user clicks \"Save\" after 5 minutes and expects their modifications to be made persistent. The user also expects that they were the only person editing this information and that no conflicting modification has occurred."
msgstr ""
#. Tag: para
-#: transactions.xml:200
#, no-c-format
msgid "From the point of view of the user, we call this unit of work a long-running <emphasis>conversation</emphasis> or <emphasis>application transaction</emphasis>. There are many ways to implement this in your application."
msgstr ""
#. Tag: para
-#: transactions.xml:206
#, no-c-format
msgid "A first naive implementation might keep the <literal>Session</literal> and database transaction open during user think time, with locks held in the database to prevent concurrent modification and to guarantee isolation and atomicity. This is an anti-pattern, since lock contention would not allow the application to scale with the number of concurrent users."
msgstr ""
#. Tag: para
-#: transactions.xml:214
#, no-c-format
msgid "You have to use several database transactions to implement the conversation. In this case, maintaining isolation of business processes becomes the partial responsibility of the application tier. A single conversation usually spans several database transactions. It will be atomic if only one of these database transactions (the last one) stores the updated data. All others simply read data (for example, in a wizard-style dialog spanning several request/response cycles). This is easier to implement than it might sound, especially if you utilize some of Hibernate's features:"
msgstr ""
#. Tag: para
-#: transactions.xml:227
#, no-c-format
msgid "<emphasis>Automatic Versioning</emphasis>: Hibernate can perform automatic optimistic concurrency control for you. It can automatically detect if a concurrent modification occurred during user think time. Check for this at the end of the conversation."
msgstr ""
#. Tag: para
-#: transactions.xml:235
#, no-c-format
msgid "<emphasis>Detached Objects</emphasis>: if you decide to use the <emphasis>session-per-request</emphasis> pattern, all loaded instances will be in the detached state during user think time. Hibernate allows you to reattach the objects and persist the modifications. The pattern is called <emphasis>session-per-request-with-detached-objects</emphasis>. Automatic versioning is used to isolate concurrent modifications."
msgstr ""
#. Tag: para
-#: transactions.xml:245
#, no-c-format
msgid "<emphasis>Extended (or Long) Session</emphasis>: the Hibernate <literal>Session</literal> can be disconnected from the underlying JDBC connection after the database transaction has been committed and reconnected when a new client request occurs. This pattern is known as <emphasis>session-per-conversation</emphasis> and makes even reattachment unnecessary. Automatic versioning is used to isolate concurrent modifications and the <literal>Session</literal> will not be allowed to be flushed automatically, but explicitly."
msgstr ""
#. Tag: para
-#: transactions.xml:258
#, no-c-format
msgid "Both <emphasis>session-per-request-with-detached-objects</emphasis> and <emphasis>session-per-conversation</emphasis> have advantages and disadvantages. These disadvantages are discussed later in this chapter in the context of optimistic concurrency control."
msgstr ""
#. Tag: title
-#: transactions.xml:267
#, no-c-format
msgid "Considering object identity"
msgstr ""
#. Tag: para
-#: transactions.xml:269
#, no-c-format
msgid "An application can concurrently access the same persistent state in two different <literal>Session</literal>s. However, an instance of a persistent class is never shared between two <literal>Session</literal> instances. It is for this reason that there are two different notions of identity:"
msgstr ""
#. Tag: term
-#: transactions.xml:278
#, no-c-format
msgid "Database Identity"
msgstr ""
-#. Tag: literal
-#: transactions.xml:281
+#. Tag: para
#, no-c-format
-msgid "foo.getId().equals( bar.getId() )"
+msgid "<literal>foo.getId().equals( bar.getId() )</literal>"
msgstr ""
#. Tag: term
-#: transactions.xml:286
#, no-c-format
msgid "JVM Identity"
msgstr ""
-#. Tag: literal
-#: transactions.xml:289
+#. Tag: para
#, no-c-format
-msgid "foo==bar"
+msgid "<literal>foo==bar</literal>"
msgstr ""
#. Tag: para
-#: transactions.xml:295
#, no-c-format
msgid "For objects attached to a <emphasis>particular</emphasis> <literal>Session</literal> (i.e., in the scope of a <literal>Session</literal>), the two notions are equivalent and JVM identity for database identity is guaranteed by Hibernate. While the application might concurrently access the \"same\" (persistent identity) business object in two different sessions, the two instances will actually be \"different\" (JVM identity). Conflicts are resolved using an optimistic approach and automatic versioning at flush/commit time."
msgstr ""
#. Tag: para
-#: transactions.xml:304
#, no-c-format
msgid "This approach leaves Hibernate and the database to worry about concurrency. It also provides the best scalability, since guaranteeing identity in single-threaded units of work means that it does not need expensive locking or other means of synchronization. The application does not need to synchronize on any business object, as long as it maintains a single thread per <literal>Session</literal>. Within a <literal>Session</literal> the application can safely use <literal>==</literal> to compare objects."
msgstr ""
#. Tag: para
-#: transactions.xml:313
#, no-c-format
msgid "However, an application that uses <literal>==</literal> outside of a <literal>Session</literal> might produce unexpected results. This might occur even in some unexpected places. For example, if you put two detached instances into the same <literal>Set</literal>, both might have the same database identity (i.e., they represent the same row). JVM identity, however, is by definition not guaranteed for instances in a detached state. The developer has to override the <literal>equals()</literal> and <literal>hashCode()</literal> methods in persistent classes and implement their own notion of object equality. There is one caveat: never use the database identifier to implement equality. Use a business key that is a combination of unique, usually immutable, attributes. The database identifier will change if a transient object is made persistent. If the transient instance (usually together with detached instances) is held in a <literal>Set</literal>, changing the hashcode bre!
aks the contract of the <literal>Set</literal>. Attributes for business keys do not have to be as stable as database primary keys; you only have to guarantee stability as long as the objects are in the same <literal>Set</literal>. See the Hibernate website for a more thorough discussion of this issue. Please note that this is not a Hibernate issue, but simply how Java object identity and equality has to be implemented."
msgstr ""
#. Tag: title
-#: transactions.xml:334
#, no-c-format
msgid "Common issues"
msgstr ""
#. Tag: para
-#: transactions.xml:336
#, no-c-format
msgid "Do not use the anti-patterns <emphasis>session-per-user-session</emphasis> or <emphasis>session-per-application</emphasis> (there are, however, rare exceptions to this rule). Some of the following issues might also arise within the recommended patterns, so ensure that you understand the implications before making a design decision:"
msgstr ""
#. Tag: para
-#: transactions.xml:345
#, no-c-format
msgid "A <literal>Session</literal> is not thread-safe. Things that work concurrently, like HTTP requests, session beans, or Swing workers, will cause race conditions if a <literal>Session</literal> instance is shared. If you keep your Hibernate <literal>Session</literal> in your <literal>HttpSession</literal> (this is discussed later in the chapter), you should consider synchronizing access to your Http session. Otherwise, a user that clicks reload fast enough can use the same <literal>Session</literal> in two concurrently running threads."
msgstr ""
#. Tag: para
-#: transactions.xml:356
#, no-c-format
msgid "An exception thrown by Hibernate means you have to rollback your database transaction and close the <literal>Session</literal> immediately (this is discussed in more detail later in the chapter). If your <literal>Session</literal> is bound to the application, you have to stop the application. Rolling back the database transaction does not put your business objects back into the state they were at the start of the transaction. This means that the database state and the business objects will be out of sync. Usually this is not a problem, because exceptions are not recoverable and you will have to start over after rollback anyway."
msgstr ""
#. Tag: para
-#: transactions.xml:368
#, no-c-format
-msgid "The <literal>Session</literal> caches every object that is in a persistent state (watched and checked for dirty state by Hibernate). If you keep it open for a long time or simply load too much data, it will grow endlessly until you get an OutOfMemoryException. One solution is to call <literal>clear()</literal> and <literal>evict()</literal> to manage the <literal>Session</literal> cache, but you should consider a Stored Procedure if you need mass data operations. Some solutions are shown in <xref linkend=\"batch\"/>. Keeping a <literal>Session</literal> open for the duration of a user session also means a higher probability of stale data."
+msgid "The <literal>Session</literal> caches every object that is in a persistent state (watched and checked for dirty state by Hibernate). If you keep it open for a long time or simply load too much data, it will grow endlessly until you get an OutOfMemoryException. One solution is to call <literal>clear()</literal> and <literal>evict()</literal> to manage the <literal>Session</literal> cache, but you should consider a Stored Procedure if you need mass data operations. Some solutions are shown in <xref linkend=\"batch\" />. Keeping a <literal>Session</literal> open for the duration of a user session also means a higher probability of stale data."
msgstr ""
#. Tag: title
-#: transactions.xml:386
#, no-c-format
msgid "Database transaction demarcation"
msgstr ""
#. Tag: para
-#: transactions.xml:388
#, no-c-format
msgid "Database, or system, transaction boundaries are always necessary. No communication with the database can occur outside of a database transaction (this seems to confuse many developers who are used to the auto-commit mode). Always use clear transaction boundaries, even for read-only operations. Depending on your isolation level and database capabilities this might not be required, but there is no downside if you always demarcate transactions explicitly. Certainly, a single database transaction is going to perform better than many small transactions, even for reading data."
msgstr ""
#. Tag: para
-#: transactions.xml:398
#, no-c-format
msgid "A Hibernate application can run in non-managed (i.e., standalone, simple Web- or Swing applications) and managed J2EE environments. In a non-managed environment, Hibernate is usually responsible for its own database connection pool. The application developer has to manually set transaction boundaries (begin, commit, or rollback database transactions) themselves. A managed environment usually provides container-managed transactions (CMT), with the transaction assembly defined declaratively (in deployment descriptors of EJB session beans, for example). Programmatic transaction demarcation is then no longer necessary."
msgstr ""
#. Tag: para
-#: transactions.xml:408
#, no-c-format
msgid "However, it is often desirable to keep your persistence layer portable between non-managed resource-local environments, and systems that can rely on JTA but use BMT instead of CMT. In both cases use programmatic transaction demarcation. Hibernate offers a wrapper API called <literal>Transaction</literal> that translates into the native transaction system of your deployment environment. This API is actually optional, but we strongly encourage its use unless you are in a CMT session bean."
msgstr ""
#. Tag: para
-#: transactions.xml:417
#, no-c-format
msgid "Ending a <literal>Session</literal> usually involves four distinct phases:"
msgstr ""
#. Tag: para
-#: transactions.xml:423
#, no-c-format
msgid "flush the session"
msgstr ""
#. Tag: para
-#: transactions.xml:428
#, no-c-format
msgid "commit the transaction"
msgstr ""
#. Tag: para
-#: transactions.xml:433
#, no-c-format
msgid "close the session"
msgstr ""
#. Tag: para
-#: transactions.xml:438
#, no-c-format
msgid "handle exceptions"
msgstr ""
#. Tag: para
-#: transactions.xml:444
#, no-c-format
msgid "We discussed Flushing the session earlier, so we will now have a closer look at transaction demarcation and exception handling in both managed and non-managed environments."
msgstr ""
#. Tag: title
-#: transactions.xml:451
#, no-c-format
msgid "Non-managed environment"
msgstr ""
#. Tag: para
-#: transactions.xml:453
#, no-c-format
msgid "If a Hibernate persistence layer runs in a non-managed environment, database connections are usually handled by simple (i.e., non-DataSource) connection pools from which Hibernate obtains connections as needed. The session/transaction handling idiom looks like this:"
msgstr ""
-#. Tag: programlisting
-#: transactions.xml:460
-#, no-c-format
-msgid ""
- "<![CDATA[// Non-managed environment idiom\n"
- "Session sess = factory.openSession();\n"
- "Transaction tx = null;\n"
- "try {\n"
- " tx = sess.beginTransaction();\n"
- "\n"
- " // do some work\n"
- " ...\n"
- "\n"
- " tx.commit();\n"
- "}\n"
- "catch (RuntimeException e) {\n"
- " if (tx != null) tx.rollback();\n"
- " throw e; // or display error message\n"
- "}\n"
- "finally {\n"
- " sess.close();\n"
- "}]]>"
-msgstr ""
-
#. Tag: para
-#: transactions.xml:462
#, no-c-format
-msgid "You do not have to <literal>flush()</literal> the <literal>Session</literal> explicitly: the call to <literal>commit()</literal> automatically triggers the synchronization depending on the <link linkend=\"objectstate-flushing\">FlushMode</link> for the session. A call to <literal>close()</literal> marks the end of a session. The main implication of <literal>close()</literal> is that the JDBC connection will be relinquished by the session. This Java code is portable and runs in both non-managed and JTA environments."
+msgid "You do not have to <literal>flush()</literal> the <literal>Session</literal> explicitly: the call to <literal>commit()</literal> automatically triggers the synchronization depending on the FlushMode for the session (see <xref linkend=\"objectstate-flushing\" />). A call to <literal>close()</literal> marks the end of a session. The main implication of <literal>close()</literal> is that the JDBC connection will be relinquished by the session. This Java code is portable and runs in both non-managed and JTA environments."
msgstr ""
#. Tag: para
-#: transactions.xml:471
#, no-c-format
msgid "As outlined earlier, a much more flexible solution is Hibernate's built-in \"current session\" context management:"
msgstr ""
-#. Tag: programlisting
-#: transactions.xml:476
-#, no-c-format
-msgid ""
- "<![CDATA[// Non-managed environment idiom with getCurrentSession()\n"
- "try {\n"
- " factory.getCurrentSession().beginTransaction();\n"
- "\n"
- " // do some work\n"
- " ...\n"
- "\n"
- " factory.getCurrentSession().getTransaction().commit();\n"
- "}\n"
- "catch (RuntimeException e) {\n"
- " factory.getCurrentSession().getTransaction().rollback();\n"
- " throw e; // or display error message\n"
- "}]]>"
-msgstr ""
-
#. Tag: para
-#: transactions.xml:478
#, no-c-format
msgid "You will not see these code snippets in a regular application; fatal (system) exceptions should always be caught at the \"top\". In other words, the code that executes Hibernate calls in the persistence layer, and the code that handles <literal>RuntimeException</literal> (and usually can only clean up and exit), are in different layers. The current context management by Hibernate can significantly simplify this design by accessing a <literal>SessionFactory</literal>. Exception handling is discussed later in this chapter."
msgstr ""
#. Tag: para
-#: transactions.xml:488
#, no-c-format
msgid "You should select <literal>org.hibernate.transaction.JDBCTransactionFactory</literal>, which is the default, and for the second example select <literal>\"thread\"</literal> as your <literal>hibernate.current_session_context_class</literal>."
msgstr ""
#. Tag: title
-#: transactions.xml:497
#, no-c-format
msgid "Using JTA"
msgstr ""
#. Tag: para
-#: transactions.xml:499
#, no-c-format
msgid "If your persistence layer runs in an application server (for example, behind EJB session beans), every datasource connection obtained by Hibernate will automatically be part of the global JTA transaction. You can also install a standalone JTA implementation and use it without EJB. Hibernate offers two strategies for JTA integration."
msgstr ""
#. Tag: para
-#: transactions.xml:506
#, no-c-format
msgid "If you use bean-managed transactions (BMT), Hibernate will tell the application server to start and end a BMT transaction if you use the <literal>Transaction</literal> API. The transaction management code is identical to the non-managed environment."
msgstr ""
-#. Tag: programlisting
-#: transactions.xml:512
-#, no-c-format
-msgid ""
- "<![CDATA[// BMT idiom\n"
- "Session sess = factory.openSession();\n"
- "Transaction tx = null;\n"
- "try {\n"
- " tx = sess.beginTransaction();\n"
- "\n"
- " // do some work\n"
- " ...\n"
- "\n"
- " tx.commit();\n"
- "}\n"
- "catch (RuntimeException e) {\n"
- " if (tx != null) tx.rollback();\n"
- " throw e; // or display error message\n"
- "}\n"
- "finally {\n"
- " sess.close();\n"
- "}]]>"
-msgstr ""
-
#. Tag: para
-#: transactions.xml:514
#, no-c-format
msgid "If you want to use a transaction-bound <literal>Session</literal>, that is, the <literal>getCurrentSession()</literal> functionality for easy context propagation, use the JTA <literal>UserTransaction</literal> API directly:"
msgstr ""
-#. Tag: programlisting
-#: transactions.xml:520
-#, no-c-format
-msgid ""
- "<![CDATA[// BMT idiom with getCurrentSession()\n"
- "try {\n"
- " UserTransaction tx = (UserTransaction)new InitialContext()\n"
- " .lookup(\"java:comp/UserTransaction\");\n"
- "\n"
- " tx.begin();\n"
- "\n"
- " // Do some work on Session bound to transaction\n"
- " factory.getCurrentSession().load(...);\n"
- " factory.getCurrentSession().persist(...);\n"
- "\n"
- " tx.commit();\n"
- "}\n"
- "catch (RuntimeException e) {\n"
- " tx.rollback();\n"
- " throw e; // or display error message\n"
- "}]]>"
-msgstr ""
-
#. Tag: para
-#: transactions.xml:522
#, no-c-format
msgid "With CMT, transaction demarcation is completed in session bean deployment descriptors, not programmatically. The code is reduced to:"
msgstr ""
-#. Tag: programlisting
-#: transactions.xml:527
-#, no-c-format
-msgid ""
- "<![CDATA[// CMT idiom\n"
- " Session sess = factory.getCurrentSession();\n"
- "\n"
- " // do some work\n"
- " ...\n"
- "]]>"
-msgstr ""
-
#. Tag: para
-#: transactions.xml:529
#, no-c-format
msgid "In a CMT/EJB, even rollback happens automatically. An unhandled <literal>RuntimeException</literal> thrown by a session bean method tells the container to set the global transaction to rollback. <emphasis>You do not need to use the Hibernate <literal>Transaction</literal> API at all with BMT or CMT, and you get automatic propagation of the \"current\" Session bound to the transaction.</emphasis>"
msgstr ""
#. Tag: para
-#: transactions.xml:537
#, no-c-format
msgid "When configuring Hibernate's transaction factory, choose <literal>org.hibernate.transaction.JTATransactionFactory</literal> if you use JTA directly (BMT), and <literal>org.hibernate.transaction.CMTTransactionFactory</literal> in a CMT session bean. Remember to also set <literal>hibernate.transaction.manager_lookup_class</literal>. Ensure that your <literal>hibernate.current_session_context_class</literal> is either unset (backwards compatibility), or is set to <literal>\"jta\"</literal>."
msgstr ""
#. Tag: para
-#: transactions.xml:546
#, no-c-format
msgid "The <literal>getCurrentSession()</literal> operation has one downside in a JTA environment. There is one caveat to the use of <literal>after_statement</literal> connection release mode, which is then used by default. Due to a limitation of the JTA spec, it is not possible for Hibernate to automatically clean up any unclosed <literal>ScrollableResults</literal> or <literal>Iterator</literal> instances returned by <literal>scroll()</literal> or <literal>iterate()</literal>. You <emphasis>must</emphasis> release the underlying database cursor by calling <literal>ScrollableResults.close()</literal> or <literal>Hibernate.close(Iterator)</literal> explicitly from a <literal>finally</literal> block. Most applications can easily avoid using <literal>scroll()</literal> or <literal>iterate()</literal> from the JTA or CMT code.)"
msgstr ""
#. Tag: title
-#: transactions.xml:562
#, no-c-format
msgid "Exception handling"
msgstr ""
#. Tag: para
-#: transactions.xml:564
#, no-c-format
msgid "If the <literal>Session</literal> throws an exception, including any <literal>SQLException</literal>, immediately rollback the database transaction, call <literal>Session.close()</literal> and discard the <literal>Session</literal> instance. Certain methods of <literal>Session</literal> will <emphasis>not</emphasis> leave the session in a consistent state. No exception thrown by Hibernate can be treated as recoverable. Ensure that the <literal>Session</literal> will be closed by calling <literal>close()</literal> in a <literal>finally</literal> block."
msgstr ""
#. Tag: para
-#: transactions.xml:575
#, no-c-format
msgid "The <literal>HibernateException</literal>, which wraps most of the errors that can occur in a Hibernate persistence layer, is an unchecked exception. It was not in older versions of Hibernate. In our opinion, we should not force the application developer to catch an unrecoverable exception at a low layer. In most systems, unchecked and fatal exceptions are handled in one of the first frames of the method call stack (i.e., in higher layers) and either an error message is presented to the application user or some other appropriate action is taken. Note that Hibernate might also throw other unchecked exceptions that are not a <literal>HibernateException</literal>. These are not recoverable and appropriate action should be taken."
msgstr ""
#. Tag: para
-#: transactions.xml:587
#, no-c-format
msgid "Hibernate wraps <literal>SQLException</literal>s thrown while interacting with the database in a <literal>JDBCException</literal>. In fact, Hibernate will attempt to convert the exception into a more meaningful subclass of <literal>JDBCException</literal>. The underlying <literal>SQLException</literal> is always available via <literal>JDBCException.getCause()</literal>. Hibernate converts the <literal>SQLException</literal> into an appropriate <literal>JDBCException</literal> subclass using the <literal>SQLExceptionConverter</literal> attached to the <literal>SessionFactory</literal>. By default, the <literal>SQLExceptionConverter</literal> is defined by the configured dialect. However, it is also possible to plug in a custom implementation. See the javadocs for the <literal>SQLExceptionConverterFactory</literal> class for details. The standard <literal>JDBCException</literal> subtypes are:"
msgstr ""
#. Tag: para
-#: transactions.xml:603
#, no-c-format
msgid "<literal>JDBCConnectionException</literal>: indicates an error with the underlying JDBC communication."
msgstr ""
#. Tag: para
-#: transactions.xml:609
#, no-c-format
msgid "<literal>SQLGrammarException</literal>: indicates a grammar or syntax problem with the issued SQL."
msgstr ""
#. Tag: para
-#: transactions.xml:615
#, no-c-format
msgid "<literal>ConstraintViolationException</literal>: indicates some form of integrity constraint violation."
msgstr ""
#. Tag: para
-#: transactions.xml:621
#, no-c-format
msgid "<literal>LockAcquisitionException</literal>: indicates an error acquiring a lock level necessary to perform the requested operation."
msgstr ""
#. Tag: para
-#: transactions.xml:627
#, no-c-format
msgid "<literal>GenericJDBCException</literal>: a generic exception which did not fall into any of the other categories."
msgstr ""
#. Tag: title
-#: transactions.xml:637
#, no-c-format
msgid "Transaction timeout"
msgstr ""
#. Tag: para
-#: transactions.xml:639
#, no-c-format
msgid "An important feature provided by a managed environment like EJB, that is never provided for non-managed code, is transaction timeout. Transaction timeouts ensure that no misbehaving transaction can indefinitely tie up resources while returning no response to the user. Outside a managed (JTA) environment, Hibernate cannot fully provide this functionality. However, Hibernate can at least control data access operations, ensuring that database level deadlocks and queries with huge result sets are limited by a defined timeout. In a managed environment, Hibernate can delegate transaction timeout to JTA. This functionality is abstracted by the Hibernate <literal>Transaction</literal> object."
msgstr ""
-#. Tag: programlisting
-#: transactions.xml:652
-#, no-c-format
-msgid ""
- "<![CDATA[\n"
- "Session sess = factory.openSession();\n"
- "try {\n"
- " //set transaction timeout to 3 seconds\n"
- " sess.getTransaction().setTimeout(3);\n"
- " sess.getTransaction().begin();\n"
- "\n"
- " // do some work\n"
- " ...\n"
- "\n"
- " sess.getTransaction().commit()\n"
- "}\n"
- "catch (RuntimeException e) {\n"
- " sess.getTransaction().rollback();\n"
- " throw e; // or display error message\n"
- "}\n"
- "finally {\n"
- " sess.close();\n"
- "}]]>"
-msgstr ""
-
#. Tag: para
-#: transactions.xml:654
#, no-c-format
msgid "<literal>setTimeout()</literal> cannot be called in a CMT bean, where transaction timeouts must be defined declaratively."
msgstr ""
#. Tag: title
-#: transactions.xml:664
#, no-c-format
msgid "Optimistic concurrency control"
msgstr ""
#. Tag: para
-#: transactions.xml:666
#, no-c-format
msgid "The only approach that is consistent with high concurrency and high scalability, is optimistic concurrency control with versioning. Version checking uses version numbers, or timestamps, to detect conflicting updates and to prevent lost updates. Hibernate provides three possible approaches to writing application code that uses optimistic concurrency. The use cases we discuss are in the context of long conversations, but version checking also has the benefit of preventing lost updates in single database transactions."
msgstr ""
#. Tag: title
-#: transactions.xml:677
#, no-c-format
msgid "Application version checking"
msgstr ""
#. Tag: para
-#: transactions.xml:679
#, no-c-format
msgid "In an implementation without much help from Hibernate, each interaction with the database occurs in a new <literal>Session</literal> and the developer is responsible for reloading all persistent instances from the database before manipulating them. The application is forced to carry out its own version checking to ensure conversation transaction isolation. This approach is the least efficient in terms of database access. It is the approach most similar to entity EJBs."
msgstr ""
-#. Tag: programlisting
-#: transactions.xml:688
-#, no-c-format
-msgid ""
- "<![CDATA[// foo is an instance loaded by a previous Session\n"
- "session = factory.openSession();\n"
- "Transaction t = session.beginTransaction();\n"
- "\n"
- "int oldVersion = foo.getVersion();\n"
- "session.load( foo, foo.getKey() ); // load the current state\n"
- "if ( oldVersion != foo.getVersion() ) throw new StaleObjectStateException();\n"
- "foo.setProperty(\"bar\");\n"
- "\n"
- "t.commit();\n"
- "session.close();]]>"
-msgstr ""
-
#. Tag: para
-#: transactions.xml:690
#, no-c-format
msgid "The <literal>version</literal> property is mapped using <literal><version></literal>, and Hibernate will automatically increment it during flush if the entity is dirty."
msgstr ""
#. Tag: para
-#: transactions.xml:696
#, no-c-format
msgid "If you are operating in a low-data-concurrency environment, and do not require version checking, you can use this approach and skip the version check. In this case, <emphasis>last commit wins</emphasis> is the default strategy for long conversations. Be aware that this might confuse the users of the application, as they might experience lost updates without error messages or a chance to merge conflicting changes."
msgstr ""
#. Tag: para
-#: transactions.xml:705
#, no-c-format
msgid "Manual version checking is only feasible in trivial circumstances and not practical for most applications. Often not only single instances, but complete graphs of modified objects, have to be checked. Hibernate offers automatic version checking with either an extended <literal>Session</literal> or detached instances as the design paradigm."
msgstr ""
#. Tag: title
-#: transactions.xml:716
#, no-c-format
msgid "Extended session and automatic versioning"
msgstr ""
#. Tag: para
-#: transactions.xml:718
#, no-c-format
msgid "A single <literal>Session</literal> instance and its persistent instances that are used for the whole conversation are known as <emphasis>session-per-conversation</emphasis>. Hibernate checks instance versions at flush time, throwing an exception if concurrent modification is detected. It is up to the developer to catch and handle this exception. Common options are the opportunity for the user to merge changes or to restart the business conversation with non-stale data."
msgstr ""
#. Tag: para
-#: transactions.xml:727
#, no-c-format
msgid "The <literal>Session</literal> is disconnected from any underlying JDBC connection when waiting for user interaction. This approach is the most efficient in terms of database access. The application does not version check or reattach detached instances, nor does it have to reload instances in every database transaction."
msgstr ""
-#. Tag: programlisting
-#: transactions.xml:735
-#, no-c-format
-msgid ""
- "<![CDATA[// foo is an instance loaded earlier by the old session\n"
- "Transaction t = session.beginTransaction(); // Obtain a new JDBC connection, start transaction\n"
- "\n"
- "foo.setProperty(\"bar\");\n"
- "\n"
- "session.flush(); // Only for last transaction in conversation\n"
- "t.commit(); // Also return JDBC connection\n"
- "session.close(); // Only for last transaction in conversation]]>"
-msgstr ""
-
#. Tag: para
-#: transactions.xml:736
#, no-c-format
msgid "The <literal>foo</literal> object knows which <literal>Session</literal> it was loaded in. Beginning a new database transaction on an old session obtains a new connection and resumes the session. Committing a database transaction disconnects a session from the JDBC connection and returns the connection to the pool. After reconnection, to force a version check on data you are not updating, you can call <literal>Session.lock()</literal> with <literal>LockMode.READ</literal> on any objects that might have been updated by another transaction. You do not need to lock any data that you <emphasis>are</emphasis> updating. Usually you would set <literal>FlushMode.MANUAL</literal> on an extended <literal>Session</literal>, so that only the last database transaction cycle is allowed to actually persist all modifications made in this conversation. Only this last database transaction will include the <literal>flush()</literal> operation, and then <literal>close()</literal> the se!
ssion to end the conversation."
msgstr ""
#. Tag: para
-#: transactions.xml:751
#, no-c-format
msgid "This pattern is problematic if the <literal>Session</literal> is too big to be stored during user think time (for example, an <literal>HttpSession</literal> should be kept as small as possible). As the <literal>Session</literal> is also the first-level cache and contains all loaded objects, we can probably use this strategy only for a few request/response cycles. Use a <literal>Session</literal> only for a single conversation as it will soon have stale data."
msgstr ""
#. Tag: title
-#: transactions.xml:762
#, no-c-format
msgid "Note"
msgstr ""
#. Tag: para
-#: transactions.xml:763
#, no-c-format
msgid "Earlier versions of Hibernate required explicit disconnection and reconnection of a <literal>Session</literal>. These methods are deprecated, as beginning and ending a transaction has the same effect."
msgstr ""
#. Tag: para
-#: transactions.xml:769
#, no-c-format
msgid "Keep the disconnected <literal>Session</literal> close to the persistence layer. Use an EJB stateful session bean to hold the <literal>Session</literal> in a three-tier environment. Do not transfer it to the web layer, or even serialize it to a separate tier, to store it in the <literal>HttpSession</literal>."
msgstr ""
#. Tag: para
-#: transactions.xml:777
#, no-c-format
msgid "The extended session pattern, or <emphasis>session-per-conversation</emphasis>, is more difficult to implement with automatic current session context management. You need to supply your own implementation of the <literal>CurrentSessionContext</literal> for this. See the Hibernate Wiki for examples."
msgstr ""
#. Tag: title
-#: transactions.xml:787
#, no-c-format
msgid "Detached objects and automatic versioning"
msgstr ""
#. Tag: para
-#: transactions.xml:789
#, no-c-format
msgid "Each interaction with the persistent store occurs in a new <literal>Session</literal>. However, the same persistent instances are reused for each interaction with the database. The application manipulates the state of detached instances originally loaded in another <literal>Session</literal> and then reattaches them using <literal>Session.update()</literal>, <literal>Session.saveOrUpdate()</literal>, or <literal>Session.merge()</literal>."
msgstr ""
-#. Tag: programlisting
-#: transactions.xml:797
-#, no-c-format
-msgid ""
- "<![CDATA[// foo is an instance loaded by a previous Session\n"
- "foo.setProperty(\"bar\");\n"
- "session = factory.openSession();\n"
- "Transaction t = session.beginTransaction();\n"
- "session.saveOrUpdate(foo); // Use merge() if \"foo\" might have been loaded already\n"
- "t.commit();\n"
- "session.close();]]>"
-msgstr ""
-
#. Tag: para
-#: transactions.xml:799
#, no-c-format
msgid "Again, Hibernate will check instance versions during flush, throwing an exception if conflicting updates occurred."
msgstr ""
#. Tag: para
-#: transactions.xml:804
#, no-c-format
msgid "You can also call <literal>lock()</literal> instead of <literal>update()</literal>, and use <literal>LockMode.READ</literal> (performing a version check and bypassing all caches) if you are sure that the object has not been modified."
msgstr ""
#. Tag: title
-#: transactions.xml:813
#, no-c-format
msgid "Customizing automatic versioning"
msgstr ""
#. Tag: para
-#: transactions.xml:815
#, no-c-format
msgid "You can disable Hibernate's automatic version increment for particular properties and collections by setting the <literal>optimistic-lock</literal> mapping attribute to <literal>false</literal>. Hibernate will then no longer increment versions if the property is dirty."
msgstr ""
#. Tag: para
-#: transactions.xml:822
#, no-c-format
msgid "Legacy database schemas are often static and cannot be modified. Or, other applications might access the same database and will not know how to handle version numbers or even timestamps. In both cases, versioning cannot rely on a particular column in a table. To force a version check with a comparison of the state of all fields in a row but without a version or timestamp property mapping, turn on <literal>optimistic-lock=\"all\"</literal> in the <literal><class></literal> mapping. This conceptually only works if Hibernate can compare the old and the new state (i.e., if you use a single long <literal>Session</literal> and not session-per-request-with-detached-objects)."
msgstr ""
#. Tag: para
-#: transactions.xml:834
#, no-c-format
msgid "Concurrent modification can be permitted in instances where the changes that have been made do not overlap. If you set <literal>optimistic-lock=\"dirty\"</literal> when mapping the <literal><class></literal>, Hibernate will only compare dirty fields during flush."
msgstr ""
#. Tag: para
-#: transactions.xml:840
#, no-c-format
msgid "In both cases, with dedicated version/timestamp columns or with a full/dirty field comparison, Hibernate uses a single <literal>UPDATE</literal> statement, with an appropriate <literal>WHERE</literal> clause, per entity to execute the version check and update the information. If you use transitive persistence to cascade reattachment to associated entities, Hibernate may execute unnecessary updates. This is usually not a problem, but <emphasis>on update</emphasis> triggers in the database might be executed even when no changes have been made to detached instances. You can customize this behavior by setting <literal>select-before-update=\"true\"</literal> in the <literal><class></literal> mapping, forcing Hibernate to <literal>SELECT</literal> the instance to ensure that changes did occur before updating the row."
msgstr ""
#. Tag: title
-#: transactions.xml:858
#, no-c-format
msgid "Pessimistic locking"
msgstr ""
#. Tag: para
-#: transactions.xml:860
#, no-c-format
msgid "It is not intended that users spend much time worrying about locking strategies. It is usually enough to specify an isolation level for the JDBC connections and then simply let the database do all the work. However, advanced users may wish to obtain exclusive pessimistic locks or re-obtain locks at the start of a new transaction."
msgstr ""
#. Tag: para
-#: transactions.xml:867
#, no-c-format
msgid "Hibernate will always use the locking mechanism of the database; it never lock objects in memory."
msgstr ""
#. Tag: para
-#: transactions.xml:872
#, no-c-format
msgid "The <literal>LockMode</literal> class defines the different lock levels that can be acquired by Hibernate. A lock is obtained by the following mechanisms:"
msgstr ""
#. Tag: para
-#: transactions.xml:879
#, no-c-format
msgid "<literal>LockMode.WRITE</literal> is acquired automatically when Hibernate updates or inserts a row."
msgstr ""
#. Tag: para
-#: transactions.xml:885
#, no-c-format
msgid "<literal>LockMode.UPGRADE</literal> can be acquired upon explicit user request using <literal>SELECT ... FOR UPDATE</literal> on databases which support that syntax."
msgstr ""
#. Tag: para
-#: transactions.xml:891
#, no-c-format
msgid "<literal>LockMode.UPGRADE_NOWAIT</literal> can be acquired upon explicit user request using a <literal>SELECT ... FOR UPDATE NOWAIT</literal> under Oracle."
msgstr ""
#. Tag: para
-#: transactions.xml:897
#, no-c-format
msgid "<literal>LockMode.READ</literal> is acquired automatically when Hibernate reads data under Repeatable Read or Serializable isolation level. It can be re-acquired by explicit user request."
msgstr ""
#. Tag: para
-#: transactions.xml:904
#, no-c-format
msgid "<literal>LockMode.NONE</literal> represents the absence of a lock. All objects switch to this lock mode at the end of a <literal>Transaction</literal>. Objects associated with the session via a call to <literal>update()</literal> or <literal>saveOrUpdate()</literal> also start out in this lock mode."
msgstr ""
#. Tag: para
-#: transactions.xml:913
#, no-c-format
msgid "The \"explicit user request\" is expressed in one of the following ways:"
msgstr ""
#. Tag: para
-#: transactions.xml:919
#, no-c-format
msgid "A call to <literal>Session.load()</literal>, specifying a <literal>LockMode</literal>."
msgstr ""
#. Tag: para
-#: transactions.xml:924
#, no-c-format
msgid "A call to <literal>Session.lock()</literal>."
msgstr ""
#. Tag: para
-#: transactions.xml:929
#, no-c-format
msgid "A call to <literal>Query.setLockMode()</literal>."
msgstr ""
#. Tag: para
-#: transactions.xml:935
#, no-c-format
msgid "If <literal>Session.load()</literal> is called with <literal>UPGRADE</literal> or <literal>UPGRADE_NOWAIT</literal>, and the requested object was not yet loaded by the session, the object is loaded using <literal>SELECT ... FOR UPDATE</literal>. If <literal>load()</literal> is called for an object that is already loaded with a less restrictive lock than the one requested, Hibernate calls <literal>lock()</literal> for that object."
msgstr ""
#. Tag: para
-#: transactions.xml:944
#, no-c-format
msgid "<literal>Session.lock()</literal> performs a version number check if the specified lock mode is <literal>READ</literal>, <literal>UPGRADE</literal> or <literal>UPGRADE_NOWAIT</literal>. In the case of <literal>UPGRADE</literal> or <literal>UPGRADE_NOWAIT</literal>, <literal>SELECT ... FOR UPDATE</literal> is used."
msgstr ""
#. Tag: para
-#: transactions.xml:951
#, no-c-format
msgid "If the requested lock mode is not supported by the database, Hibernate uses an appropriate alternate mode instead of throwing an exception. This ensures that applications are portable."
msgstr ""
#. Tag: title
-#: transactions.xml:960
#, no-c-format
msgid "Connection release modes"
msgstr ""
#. Tag: para
-#: transactions.xml:962
#, no-c-format
msgid "One of the legacies of Hibernate 2.x JDBC connection management meant that a <literal>Session</literal> would obtain a connection when it was first required and then maintain that connection until the session was closed. Hibernate 3.x introduced the notion of connection release modes that would instruct a session how to handle its JDBC connections. The following discussion is pertinent only to connections provided through a configured <literal>ConnectionProvider</literal>. User-supplied connections are outside the breadth of this discussion. The different release modes are identified by the enumerated values of <literal>org.hibernate.ConnectionReleaseMode</literal>:"
msgstr ""
#. Tag: para
-#: transactions.xml:976
#, no-c-format
msgid "<literal>ON_CLOSE</literal>: is the legacy behavior described above. The Hibernate session obtains a connection when it first needs to perform some JDBC access and maintains that connection until the session is closed."
msgstr ""
#. Tag: para
-#: transactions.xml:983
#, no-c-format
msgid "<literal>AFTER_TRANSACTION</literal>: releases connections after a <literal>org.hibernate.Transaction</literal> has been completed."
msgstr ""
#. Tag: para
-#: transactions.xml:989
#, no-c-format
msgid "<literal>AFTER_STATEMENT</literal> (also referred to as aggressive release): releases connections after every statement execution. This aggressive releasing is skipped if that statement leaves open resources associated with the given session. Currently the only situation where this occurs is through the use of <literal>org.hibernate.ScrollableResults</literal>."
msgstr ""
#. Tag: para
-#: transactions.xml:999
#, no-c-format
msgid "The configuration parameter <literal>hibernate.connection.release_mode</literal> is used to specify which release mode to use. The possible values are as follows:"
msgstr ""
#. Tag: para
-#: transactions.xml:1006
#, no-c-format
msgid "<literal>auto</literal> (the default): this choice delegates to the release mode returned by the <literal>org.hibernate.transaction.TransactionFactory.getDefaultReleaseMode()</literal> method. For JTATransactionFactory, this returns ConnectionReleaseMode.AFTER_STATEMENT; for JDBCTransactionFactory, this returns ConnectionReleaseMode.AFTER_TRANSACTION. Do not change this default behavior as failures due to the value of this setting tend to indicate bugs and/or invalid assumptions in user code."
msgstr ""
#. Tag: para
-#: transactions.xml:1016
#, no-c-format
msgid "<literal>on_close</literal>: uses ConnectionReleaseMode.ON_CLOSE. This setting is left for backwards compatibility, but its use is discouraged."
msgstr ""
#. Tag: para
-#: transactions.xml:1022
#, no-c-format
msgid "<literal>after_transaction</literal>: uses ConnectionReleaseMode.AFTER_TRANSACTION. This setting should not be used in JTA environments. Also note that with ConnectionReleaseMode.AFTER_TRANSACTION, if a session is considered to be in auto-commit mode, connections will be released as if the release mode were AFTER_STATEMENT."
msgstr ""
#. Tag: para
-#: transactions.xml:1030
#, no-c-format
msgid "<literal>after_statement</literal>: uses ConnectionReleaseMode.AFTER_STATEMENT. Additionally, the configured <literal>ConnectionProvider</literal> is consulted to see if it supports this setting (<literal>supportsAggressiveRelease()</literal>). If not, the release mode is reset to ConnectionReleaseMode.AFTER_TRANSACTION. This setting is only safe in environments where we can either re-acquire the same underlying JDBC connection each time you make a call into <literal>ConnectionProvider.getConnection()</literal> or in auto-commit environments where it does not matter if we re-establish the same connection."
msgstr ""
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/tutorial.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/tutorial.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/tutorial.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,1582 +1,698 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-23 18:41+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:20\n"
+"PO-Revision-Date: 2010-01-08T04:07:20\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
-#: tutorial.xml:31
#, no-c-format
msgid "Tutorial"
msgstr ""
#. Tag: para
-#: tutorial.xml:33
#, no-c-format
msgid "Intended for new users, this chapter provides an step-by-step introduction to Hibernate, starting with a simple application using an in-memory database. The tutorial is based on an earlier tutorial developed by Michael Gloegl. All code is contained in the <filename>tutorials/web</filename> directory of the project source."
msgstr ""
#. Tag: para
-#: tutorial.xml:42
#, no-c-format
msgid "This tutorial expects the user have knowledge of both Java and SQL. If you have a limited knowledge of JAVA or SQL, it is advised that you start with a good introduction to that technology prior to attempting to learn Hibernate."
msgstr ""
#. Tag: para
-#: tutorial.xml:51
#, no-c-format
msgid "The distribution contains another example application under the <filename>tutorial/eg</filename> project source directory."
msgstr ""
#. Tag: title
-#: tutorial.xml:59
#, no-c-format
msgid "Part 1 - The first Hibernate Application"
msgstr ""
#. Tag: para
-#: tutorial.xml:61
#, no-c-format
msgid "For this example, we will set up a small database application that can store events we want to attend and information about the host(s) of these events."
msgstr ""
#. Tag: para
-#: tutorial.xml:67
#, no-c-format
msgid "Although you can use whatever database you feel comfortable using, we will use <ulink url=\"http://hsqldb.org/\">HSQLDB</ulink> (an in-memory, Java database) to avoid describing installation/setup of any particular database servers."
msgstr ""
#. Tag: title
-#: tutorial.xml:76
#, no-c-format
msgid "Setup"
msgstr ""
#. Tag: para
-#: tutorial.xml:78
#, no-c-format
msgid "The first thing we need to do is to set up the development environment. We will be using the \"standard layout\" advocated by alot of build tools such as <ulink url=\"http://maven.org\">Maven</ulink>. Maven, in particular, has a good resource describing this <ulink url=\"http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html\">layout</ulink>. As this tutorial is to be a web application, we will be creating and making use of <filename>src/main/java</filename>, <filename>src/main/resources</filename> and <filename>src/main/webapp</filename> directories."
msgstr ""
#. Tag: para
-#: tutorial.xml:88
#, no-c-format
msgid "We will be using Maven in this tutorial, taking advantage of its transitive dependency management capabilities as well as the ability of many IDEs to automatically set up a project for us based on the maven descriptor."
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:94
-#, no-c-format
-msgid ""
- "<![CDATA[<project xmlns=\"http://maven.apache.org/POM/4.0.0\"\n"
- " xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
- " xsi:schemaLocation=\"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd\">\n"
- "\n"
- " <modelVersion>4.0.0</modelVersion>\n"
- "\n"
- " <groupId>org.hibernate.tutorials</groupId>\n"
- " <artifactId>hibernate-tutorial</artifactId>\n"
- " <version>1.0.0-SNAPSHOT</version>\n"
- " <name>First Hibernate Tutorial</name>\n"
- "\n"
- " <build>\n"
- " <!-- we dont want the version to be part of the generated war file name -->\n"
- " <finalName>${artifactId}</finalName>\n"
- " </build>\n"
- "\n"
- " <dependencies>\n"
- " <dependency>\n"
- " <groupId>org.hibernate</groupId>\n"
- " <artifactId>hibernate-core</artifactId>\n"
- " </dependency>\n"
- "\n"
- " <!-- Because this is a web app, we also have a dependency on the servlet api. -->\n"
- " <dependency>\n"
- " <groupId>javax.servlet</groupId>\n"
- " <artifactId>servlet-api</artifactId>\n"
- " </dependency>\n"
- "\n"
- " <!-- Hibernate uses slf4j for logging, for our purposes here use the simple backend -->\n"
- " <dependency>\n"
- " <groupId>org.slf4j</groupId>\n"
- " <artifactId>slf4j-simple</artifactId>\n"
- " </dependency>\n"
- "\n"
- " <!-- Hibernate gives you a choice of bytecode providers between cglib and javassist -->\n"
- " <dependency>\n"
- " <groupId>javassist</groupId>\n"
- " <artifactId>javassist</artifactId>\n"
- " </dependency>\n"
- " </dependencies>\n"
- "\n"
- "</project>]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:97
#, no-c-format
-msgid "It is not a requirement to use Maven. If you wish to use something else to build this tutoial (such as Ant), the layout will remain the same. The only change is that you will need to manually account for all the needed dependencies. If you use something like <ulink url=\"http://ant.apache.org/ivy/\">Ivy</ulink> providing transitive dependency management you would still use the dependencies mentioned below. Otherwise, you'd need to grab <emphasis>all</emphasis> dependencies, both explicit and transitive, and add them to the project's classpath. If working from the Hibernate distribution bundle, this would mean <filename>hibernate3.jar</filename>, all artifacts in the <filename>lib/required</filename> directory and all files from either the <filename>lib/bytecode/cglib</filename> or <filename>lib/bytecode/javassist</filename> directory; additionally you will need both the servlet-api jar and one of the slf4j logging backends."
+msgid "It is not a requirement to use Maven. If you wish to use another technology to build this tutorial (such as Ant), the layout will remain the same. The only change is that you will need to manually account for all the needed dependencies. If you use <ulink url=\"http://ant.apache.org/ivy/\">Ivy</ulink> to provide transitive dependency management you would still use the dependencies mentioned below. Otherwise, you will need to find all the dependencies, both explicit and transitive, and add them to the projects classpath. If working from the Hibernate distribution bundle, this would mean <filename>hibernate3.jar</filename>, all artifacts in the <filename>lib/required</filename> directory and all files from either the <filename>lib/bytecode/cglib</filename> or <filename>lib/bytecode/javassist</filename> directory; additionally you will need both the servlet-api jar and one of the slf4j logging backends."
msgstr ""
#. Tag: para
-#: tutorial.xml:114
#, no-c-format
msgid "Save this file as <filename>pom.xml</filename> in the project root directory."
msgstr ""
#. Tag: title
-#: tutorial.xml:121
#, no-c-format
msgid "The first class"
msgstr ""
#. Tag: para
-#: tutorial.xml:123
#, no-c-format
msgid "Next, we create a class that represents the event we want to store in the database; it is a simple JavaBean class with some properties:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:128
-#, no-c-format
-msgid ""
- "<![CDATA[package org.hibernate.tutorial.domain;\n"
- "\n"
- "import java.util.Date;\n"
- "\n"
- "public class Event {\n"
- " private Long id;\n"
- "\n"
- " private String title;\n"
- " private Date date;\n"
- "\n"
- " public Event() {}\n"
- "\n"
- " public Long getId() {\n"
- " return id;\n"
- " }\n"
- "\n"
- " private void setId(Long id) {\n"
- " this.id = id;\n"
- " }\n"
- "\n"
- " public Date getDate() {\n"
- " return date;\n"
- " }\n"
- "\n"
- " public void setDate(Date date) {\n"
- " this.date = date;\n"
- " }\n"
- "\n"
- " public String getTitle() {\n"
- " return title;\n"
- " }\n"
- "\n"
- " public void setTitle(String title) {\n"
- " this.title = title;\n"
- " }\n"
- "}]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:130
#, no-c-format
msgid "This class uses standard JavaBean naming conventions for property getter and setter methods, as well as private visibility for the fields. Although this is the recommended design, it is not required. Hibernate can also access fields directly, the benefit of accessor methods is robustness for refactoring."
msgstr ""
#. Tag: para
-#: tutorial.xml:138
#, no-c-format
msgid "The <literal>id</literal> property holds a unique identifier value for a particular event. All persistent entity classes (there are less important dependent classes as well) will need such an identifier property if we want to use the full feature set of Hibernate. In fact, most applications, especially web applications, need to distinguish objects by identifier, so you should consider this a feature rather than a limitation. However, we usually do not manipulate the identity of an object, hence the setter method should be private. Only Hibernate will assign identifiers when an object is saved. Hibernate can access public, private, and protected accessor methods, as well as public, private and protected fields directly. The choice is up to you and you can match it to fit your application design."
msgstr ""
#. Tag: para
-#: tutorial.xml:153
#, no-c-format
msgid "The no-argument constructor is a requirement for all persistent classes; Hibernate has to create objects for you, using Java Reflection. The constructor can be private, however package or public visibility is required for runtime proxy generation and efficient data retrieval without bytecode instrumentation."
msgstr ""
#. Tag: para
-#: tutorial.xml:161
#, no-c-format
msgid "Save this file to the <filename>src/main/java/org/hibernate/tutorial/domain</filename> directory."
msgstr ""
#. Tag: title
-#: tutorial.xml:168
#, no-c-format
msgid "The mapping file"
msgstr ""
#. Tag: para
-#: tutorial.xml:170
#, no-c-format
msgid "Hibernate needs to know how to load and store objects of the persistent class. This is where the Hibernate mapping file comes into play. The mapping file tells Hibernate what table in the database it has to access, and what columns in that table it should use."
msgstr ""
#. Tag: para
-#: tutorial.xml:178
#, no-c-format
msgid "The basic structure of a mapping file looks like this:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:182
-#, no-c-format
-msgid ""
- "<![CDATA[<?xml version=\"1.0\"?>\n"
- "<!DOCTYPE hibernate-mapping PUBLIC\n"
- " \"-//Hibernate/Hibernate Mapping DTD 3.0//EN\"\n"
- " \"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd\">\n"
- "\n"
- "<hibernate-mapping package=\"org.hibernate.tutorial.domain\">\n"
- "[...]\n"
- "</hibernate-mapping>]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:184
#, no-c-format
msgid "Hibernate DTD is sophisticated. You can use it for auto-completion of XML mapping elements and attributes in your editor or IDE. Opening up the DTD file in your text editor is the easiest way to get an overview of all elements and attributes, and to view the defaults, as well as some comments. Hibernate will not load the DTD file from the web, but first look it up from the classpath of the application. The DTD file is included in <filename>hibernate-core.jar</filename> (it is also included in the <filename>hibernate3.jar</filename>, if using the distribution bundle)."
msgstr ""
#. Tag: para
-#: tutorial.xml:197
#, no-c-format
msgid "We will omit the DTD declaration in future examples to shorten the code. It is, of course, not optional."
msgstr ""
#. Tag: para
-#: tutorial.xml:203
#, no-c-format
msgid "Between the two <literal>hibernate-mapping</literal> tags, include a <literal>class</literal> element. All persistent entity classes (again, there might be dependent classes later on, which are not first-class entities) need a mapping to a table in the SQL database:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:210
-#, no-c-format
-msgid ""
- "<![CDATA[<hibernate-mapping package=\"org.hibernate.tutorial.domain\">\n"
- "\n"
- " <class name=\"Event\" table=\"EVENTS\">\n"
- "\n"
- " </class>\n"
- "\n"
- "</hibernate-mapping>]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:212
#, no-c-format
msgid "So far we have told Hibernate how to persist and load object of class <literal>Event</literal> to the table <literal>EVENTS</literal>. Each instance is now represented by a row in that table. Now we can continue by mapping the unique identifier property to the tables primary key. As we do not want to care about handling this identifier, we configure Hibernate's identifier generation strategy for a surrogate primary key column:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:222
-#, no-c-format
-msgid ""
- "<![CDATA[<hibernate-mapping package=\"org.hibernate.tutorial.domain\">\n"
- "\n"
- " <class name=\"Event\" table=\"EVENTS\">\n"
- " <id name=\"id\" column=\"EVENT_ID\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " </class>\n"
- "\n"
- "</hibernate-mapping>]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:224
#, no-c-format
msgid "The <literal>id</literal> element is the declaration of the identifier property. The <literal>name=\"id\"</literal> mapping attribute declares the name of the JavaBean property and tells Hibernate to use the <literal>getId()</literal> and <literal>setId()</literal> methods to access the property. The column attribute tells Hibernate which column of the <literal>EVENTS</literal> table holds the primary key value."
msgstr ""
#. Tag: para
-#: tutorial.xml:234
#, no-c-format
msgid "The nested <literal>generator</literal> element specifies the identifier generation strategy (aka how are identifier values generated?). In this case we choose <literal>native</literal>, which offers a level of portability depending on the configured database dialect. Hibernate supports database generated, globally unique, as well as application assigned, identifiers. Identifier value generation is also one of Hibernate's many extension points and you can plugin in your own strategy."
msgstr ""
#. Tag: para
-#: tutorial.xml:246
#, no-c-format
-msgid "<literal>native</literal> is no longer consider the best strategy in terms of portability. for further discussion, see"
+msgid "<literal>native</literal> is no longer considered the best strategy in terms of portability. for further discussion, see <xref linkend=\"portability-idgen\" />"
msgstr ""
#. Tag: para
-#: tutorial.xml:252
#, no-c-format
msgid "Lastly, we need to tell Hibernate about the remaining entity class properties. By default, no properties of the class are considered persistent:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:258
-#, no-c-format
-msgid ""
- "<![CDATA[\n"
- "<hibernate-mapping package=\"org.hibernate.tutorial.domain\">\n"
- "\n"
- " <class name=\"Event\" table=\"EVENTS\">\n"
- " <id name=\"id\" column=\"EVENT_ID\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <property name=\"date\" type=\"timestamp\" column=\"EVENT_DATE\"/>\n"
- " <property name=\"title\"/>\n"
- " </class>\n"
- "\n"
- "</hibernate-mapping>]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:260
#, no-c-format
msgid "Similar to the <literal>id</literal> element, the <literal>name</literal> attribute of the <literal>property</literal> element tells Hibernate which getter and setter methods to use. In this case, Hibernate will search for <literal>getDate()</literal>, <literal>setDate()</literal>, <literal>getTitle()</literal> and <literal>setTitle()</literal> methods."
msgstr ""
#. Tag: para
-#: tutorial.xml:271
#, no-c-format
msgid "Why does the <literal>date</literal> property mapping include the <literal>column</literal> attribute, but the <literal>title</literal> does not? Without the <literal>column</literal> attribute, Hibernate by default uses the property name as the column name. This works for <literal>title</literal>, however, <literal>date</literal> is a reserved keyword in most databases so you will need to map it to a different name."
msgstr ""
#. Tag: para
-#: tutorial.xml:281
#, no-c-format
msgid "The <literal>title</literal> mapping also lacks a <literal>type</literal> attribute. The types declared and used in the mapping files are not Java data types; they are not SQL database types either. These types are called <emphasis>Hibernate mapping types</emphasis>, converters which can translate from Java to SQL data types and vice versa. Again, Hibernate will try to determine the correct conversion and mapping type itself if the <literal>type</literal> attribute is not present in the mapping. In some cases this automatic detection using Reflection on the Java class might not have the default you expect or need. This is the case with the <literal>date</literal> property. Hibernate cannot know if the property, which is of <literal>java.util.Date</literal>, should map to a SQL <literal>date</literal>, <literal>timestamp</literal>, or <literal>time</literal> column. Full date and time information is preserved by mapping the property with a <literal>timestamp</literal>!
converter."
msgstr ""
#. Tag: para
-#: tutorial.xml:297
#, no-c-format
msgid "Hibernate makes this mapping type determination using reflection when the mapping files are processed. This can take time and resources, so if startup performance is important you should consider explicitly defining the type to use."
msgstr ""
#. Tag: para
-#: tutorial.xml:304
#, no-c-format
msgid "Save this mapping file as <filename>src/main/resources/org/hibernate/tutorial/domain/Event.hbm.xml</filename>."
msgstr ""
#. Tag: title
-#: tutorial.xml:312
#, no-c-format
msgid "Hibernate configuration"
msgstr ""
#. Tag: para
-#: tutorial.xml:314
#, no-c-format
msgid "At this point, you should have the persistent class and its mapping file in place. It is now time to configure Hibernate. First let's set up HSQLDB to run in \"server mode\""
msgstr ""
#. Tag: para
-#: tutorial.xml:321
#, no-c-format
-msgid "We do this do that the data remains between runs."
+msgid "We do this so that the data remains between runs."
msgstr ""
#. Tag: para
-#: tutorial.xml:326
#, no-c-format
msgid "We will utilize the Maven exec plugin to launch the HSQLDB server by running: <command> mvn exec:java -Dexec.mainClass=\"org.hsqldb.Server\" -Dexec.args=\"-database.0 file:target/data/tutorial\"</command> You will see it start up and bind to a TCP/IP socket; this is where our application will connect later. If you want to start with a fresh database during this tutorial, shutdown HSQLDB, delete all files in the <filename>target/data</filename> directory, and start HSQLDB again."
msgstr ""
#. Tag: para
-#: tutorial.xml:337
#, no-c-format
msgid "Hibernate will be connecting to the database on behalf of your application, so it needs to know how to obtain connections. For this tutorial we will be using a standalone connection pool (as opposed to a <interfacename>javax.sql.DataSource</interfacename>). Hibernate comes with support for two third-party open source JDBC connection pools: <ulink url=\"https://sourceforge.net/projects/c3p0\">c3p0</ulink> and <ulink url=\"http://proxool.sourceforge.net/\">proxool</ulink>. However, we will be using the Hibernate built-in connection pool for this tutorial."
msgstr ""
#. Tag: para
-#: tutorial.xml:348
#, no-c-format
-msgid "The built-in Hibernate connection pool is in no way intended for production use. It lacks several features found on any decent connection pool."
+msgid "The built-in Hibernate connection pool is not intended for production use."
msgstr ""
#. Tag: para
-#: tutorial.xml:354
#, no-c-format
msgid "For Hibernate's configuration, we can use a simple <literal>hibernate.properties</literal> file, a more sophisticated <literal>hibernate.cfg.xml</literal> file, or even complete programmatic setup. Most users prefer the XML configuration file:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:360
-#, no-c-format
-msgid ""
- "<![CDATA[<?xml version='1.0' encoding='utf-8'?>\n"
- "<!DOCTYPE hibernate-configuration PUBLIC\n"
- " \"-//Hibernate/Hibernate Configuration DTD 3.0//EN\"\n"
- " \"http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd\">\n"
- "\n"
- "<hibernate-configuration>\n"
- "\n"
- " <session-factory>\n"
- "\n"
- " <!-- Database connection settings -->\n"
- " <property name=\"connection.driver_class\">org.hsqldb.jdbcDriver</property>\n"
- " <property name=\"connection.url\">jdbc:hsqldb:hsql://localhost</property>\n"
- " <property name=\"connection.username\">sa</property>\n"
- " <property name=\"connection.password\"></property>\n"
- "\n"
- " <!-- JDBC connection pool (use the built-in) -->\n"
- " <property name=\"connection.pool_size\">1</property>\n"
- "\n"
- " <!-- SQL dialect -->\n"
- " <property name=\"dialect\">org.hibernate.dialect.HSQLDialect</property>\n"
- "\n"
- " <!-- Enable Hibernate's automatic session context management -->\n"
- " <property name=\"current_session_context_class\">thread</property>\n"
- "\n"
- " <!-- Disable the second-level cache -->\n"
- " <property name=\"cache.provider_class\">org.hibernate.cache.NoCacheProvider</property>\n"
- "\n"
- " <!-- Echo all executed SQL to stdout -->\n"
- " <property name=\"show_sql\">true</property>\n"
- "\n"
- " <!-- Drop and re-create the database schema on startup -->\n"
- " <property name=\"hbm2ddl.auto\">update</property>\n"
- "\n"
- " <mapping resource=\"org/hibernate/tutorial/domain/Event.hbm.xml\"/>\n"
- "\n"
- " </session-factory>\n"
- "\n"
- "</hibernate-configuration>]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:363
#, no-c-format
msgid "Notice that this configuration file specifies a different DTD"
msgstr ""
#. Tag: para
-#: tutorial.xml:366
#, no-c-format
msgid "You configure Hibernate's <literal>SessionFactory</literal>. SessionFactory is a global factory responsible for a particular database. If you have several databases, for easier startup you should use several <literal><session-factory></literal> configurations in several configuration files."
msgstr ""
#. Tag: para
-#: tutorial.xml:373
#, no-c-format
msgid "The first four <literal>property</literal> elements contain the necessary configuration for the JDBC connection. The dialect <literal>property</literal> element specifies the particular SQL variant Hibernate generates."
msgstr ""
#. Tag: para
-#: tutorial.xml:380
#, no-c-format
-msgid "In most cases, Hibernate is able to properly determine which dialect to use. See <xref linkend=\"portability-dialectresolver\"/> for more information."
+msgid "Hibernate is able to correctly determine which dialect to use in most cases. See <xref linkend=\"portability-dialectresolver\" /> for more information."
msgstr ""
#. Tag: para
-#: tutorial.xml:386
#, no-c-format
msgid "Hibernate's automatic session management for persistence contexts is particularly useful in this context. The <literal>hbm2ddl.auto</literal> option turns on automatic generation of database schemas directly into the database. This can also be turned off by removing the configuration option, or redirected to a file with the help of the <literal>SchemaExport</literal> Ant task. Finally, add the mapping file(s) for persistent classes to the configuration."
msgstr ""
#. Tag: para
-#: tutorial.xml:395
#, no-c-format
msgid "Save this file as <filename>hibernate.cfg.xml</filename> into the <filename>src/main/resources</filename> directory."
msgstr ""
#. Tag: title
-#: tutorial.xml:403
#, no-c-format
msgid "Building with Maven"
msgstr ""
#. Tag: para
-#: tutorial.xml:405
#, no-c-format
msgid "We will now build the tutorial with Maven. You will need to have Maven installed; it is available from the <ulink url=\"http://maven.apache.org/download.html\">Maven download page</ulink>. Maven will read the <filename>/pom.xml</filename> file we created earlier and know how to perform some basic project tasks. First, lets run the <literal>compile</literal> goal to make sure we can compile everything so far:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:415
-#, no-c-format
-msgid ""
- "<![CDATA[[hibernateTutorial]$ mvn compile\n"
- "[INFO] Scanning for projects...\n"
- "[INFO] ------------------------------------------------------------------------\n"
- "[INFO] Building First Hibernate Tutorial\n"
- "[INFO] task-segment: [compile]\n"
- "[INFO] ------------------------------------------------------------------------\n"
- "[INFO] [resources:resources]\n"
- "[INFO] Using default encoding to copy filtered resources.\n"
- "[INFO] [compiler:compile]\n"
- "[INFO] Compiling 1 source file to /home/steve/projects/sandbox/hibernateTutorial/target/classes\n"
- "[INFO] ------------------------------------------------------------------------\n"
- "[INFO] BUILD SUCCESSFUL\n"
- "[INFO] ------------------------------------------------------------------------\n"
- "[INFO] Total time: 2 seconds\n"
- "[INFO] Finished at: Tue Jun 09 12:25:25 CDT 2009\n"
- "[INFO] Final Memory: 5M/547M\n"
- "[INFO] ------------------------------------------------------------------------]]>"
-msgstr ""
-
#. Tag: title
-#: tutorial.xml:420
#, no-c-format
msgid "Startup and helpers"
msgstr ""
#. Tag: para
-#: tutorial.xml:422
#, no-c-format
msgid "It is time to load and store some <literal>Event</literal> objects, but first you have to complete the setup with some infrastructure code. You have to startup Hibernate by building a global <interfacename>org.hibernate.SessionFactory</interfacename> object and storing it somewhere for easy access in application code. A <interfacename>org.hibernate.SessionFactory</interfacename> is used to obtain <interfacename>org.hibernate.Session</interfacename> instances. A <interfacename>org.hibernate.Session</interfacename> represents a single-threaded unit of work. The <interfacename>org.hibernate.SessionFactory</interfacename> is a thread-safe global object that is instantiated once."
msgstr ""
#. Tag: para
-#: tutorial.xml:436
#, no-c-format
msgid "We will create a <literal>HibernateUtil</literal> helper class that takes care of startup and makes accessing the <interfacename>org.hibernate.SessionFactory</interfacename> more convenient."
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:442
-#, no-c-format
-msgid ""
- "<![CDATA[package org.hibernate.tutorial.util;\n"
- "\n"
- "import org.hibernate.SessionFactory;\n"
- "import org.hibernate.cfg.Configuration;\n"
- "\n"
- "public class HibernateUtil {\n"
- "\n"
- " private static final SessionFactory sessionFactory = buildSessionFactory();\n"
- "\n"
- " private static SessionFactory buildSessionFactory() {\n"
- " try {\n"
- " // Create the SessionFactory from hibernate.cfg.xml\n"
- " return new Configuration().configure().buildSessionFactory();\n"
- " }\n"
- " catch (Throwable ex) {\n"
- " // Make sure you log the exception, as it might be swallowed\n"
- " System.err.println(\"Initial SessionFactory creation failed.\" + ex);\n"
- " throw new ExceptionInInitializerError(ex);\n"
- " }\n"
- " }\n"
- "\n"
- " public static SessionFactory getSessionFactory() {\n"
- " return sessionFactory;\n"
- " }\n"
- "\n"
- "}]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:444
#, no-c-format
msgid "Save this code as <filename>src/main/java/org/hibernate/tutorial/util/HibernateUtil.java</filename>"
msgstr ""
#. Tag: para
-#: tutorial.xml:449
#, no-c-format
msgid "This class not only produces the global <interfacename>org.hibernate.SessionFactory</interfacename> reference in its static initializer; it also hides the fact that it uses a static singleton. We might just as well have looked up the <interfacename>org.hibernate.SessionFactory</interfacename> reference from JNDI in an application server or any other location for that matter."
msgstr ""
#. Tag: para
-#: tutorial.xml:458
#, no-c-format
msgid "If you give the <interfacename>org.hibernate.SessionFactory</interfacename> a name in your configuration, Hibernate will try to bind it to JNDI under that name after it has been built. Another, better option is to use a JMX deployment and let the JMX-capable container instantiate and bind a <literal>HibernateService</literal> to JNDI. Such advanced options are discussed later."
msgstr ""
#. Tag: para
-#: tutorial.xml:467
#, no-c-format
msgid "You now need to configure a logging system. Hibernate uses commons logging and provides two choices: Log4j and JDK 1.4 logging. Most developers prefer Log4j: copy <literal>log4j.properties</literal> from the Hibernate distribution in the <literal>etc/</literal> directory to your <literal>src</literal> directory, next to <literal>hibernate.cfg.xml</literal>. If you prefer to have more verbose output than that provided in the example configuration, you can change the settings. By default, only the Hibernate startup message is shown on stdout."
msgstr ""
#. Tag: para
-#: tutorial.xml:477
#, no-c-format
msgid "The tutorial infrastructure is complete and you are now ready to do some real work with Hibernate."
msgstr ""
#. Tag: title
-#: tutorial.xml:485
#, no-c-format
msgid "Loading and storing objects"
msgstr ""
#. Tag: para
-#: tutorial.xml:487
#, no-c-format
msgid "We are now ready to start doing some real worjk with Hibernate. Let's start by writing an <literal>EventManager</literal> class with a <literal>main()</literal> method:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:493
-#, no-c-format
-msgid ""
- "<![CDATA[package org.hibernate.tutorial;\n"
- "\n"
- "import org.hibernate.Session;\n"
- "\n"
- "import java.util.*;\n"
- "\n"
- "import org.hibernate.tutorial.domain.Event;\n"
- "import org.hibernate.tutorial.util.HibernateUtil;\n"
- "\n"
- "public class EventManager {\n"
- "\n"
- " public static void main(String[] args) {\n"
- " EventManager mgr = new EventManager();\n"
- "\n"
- " if (args[0].equals(\"store\")) {\n"
- " mgr.createAndStoreEvent(\"My Event\", new Date());\n"
- " }\n"
- "\n"
- " HibernateUtil.getSessionFactory().close();\n"
- " }\n"
- "\n"
- " private void createAndStoreEvent(String title, Date theDate) {\n"
- " Session session = HibernateUtil.getSessionFactory().getCurrentSession();\n"
- " session.beginTransaction();\n"
- "\n"
- " Event theEvent = new Event();\n"
- " theEvent.setTitle(title);\n"
- " theEvent.setDate(theDate);\n"
- " session.save(theEvent);\n"
- "\n"
- " session.getTransaction().commit();\n"
- " }\n"
- "\n"
- "}]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:495
#, no-c-format
msgid "In <literal>createAndStoreEvent()</literal> we created a new <literal>Event</literal> object and handed it over to Hibernate. At that point, Hibernate takes care of the SQL and executes an <literal>INSERT</literal> on the database."
msgstr ""
#. Tag: para
-#: tutorial.xml:502
#, no-c-format
msgid "A <interface>org.hibernate.Session</interface> is designed to represent a single unit of work (a single atmoic piece of work to be performed). For now we will keep things simple and assume a one-to-one granularity between a Hibernate <interface>org.hibernate.Session</interface> and a database transaction. To shield our code from the actual underlying transaction system we use the Hibernate <interfacename>org.hibernate.Transaction</interfacename> API. In this particular case we are using JDBC-based transactional semantics, but it could also run with JTA."
msgstr ""
#. Tag: para
-#: tutorial.xml:515
#, no-c-format
msgid "What does <literal>sessionFactory.getCurrentSession()</literal> do? First, you can call it as many times and anywhere you like once you get hold of your <interfacename>org.hibernate.SessionFactory</interfacename>. The <literal>getCurrentSession()</literal> method always returns the \"current\" unit of work. Remember that we switched the configuration option for this mechanism to \"thread\" in our <filename>src/main/resources/hibernate.cfg.xml</filename>? Due to that setting, the context of a current unit of work is bound to the current Java thread that executes the application."
msgstr ""
#. Tag: para
-#: tutorial.xml:529
#, no-c-format
msgid "Hibernate offers three methods of current session tracking. The \"thread\" based method is not intended for production use; it is merely useful for prototyping and tutorials such as this one. Current session tracking is discussed in more detail later on."
msgstr ""
#. Tag: para
-#: tutorial.xml:538
#, no-c-format
msgid "A <interface>org.hibernate.Session</interface> begins when the first call to <literal>getCurrentSession()</literal> is made for the current thread. It is then bound by Hibernate to the current thread. When the transaction ends, either through commit or rollback, Hibernate automatically unbinds the <interface>org.hibernate.Session</interface> from the thread and closes it for you. If you call <literal>getCurrentSession()</literal> again, you get a new <interface>org.hibernate.Session</interface> and can start a new unit of work."
msgstr ""
#. Tag: para
-#: tutorial.xml:551
#, no-c-format
msgid "Related to the unit of work scope, should the Hibernate <interface>org.hibernate.Session</interface> be used to execute one or several database operations? The above example uses one <interface>org.hibernate.Session</interface> for one operation. However this is pure coincidence; the example is just not complex enough to show any other approach. The scope of a Hibernate <interface>org.hibernate.Session</interface> is flexible but you should never design your application to use a new Hibernate <interface>org.hibernate.Session</interface> for <emphasis>every</emphasis> database operation. Even though it is used in the following examples, consider <emphasis>session-per-operation</emphasis> an anti-pattern. A real web application is shown later in the tutorial which will help illustrate this."
msgstr ""
#. Tag: para
-#: tutorial.xml:568
#, no-c-format
-msgid "See <xref linkend=\"transactions\"/> for more information about transaction handling and demarcation. The previous example also skipped any error handling and rollback."
+msgid "See <xref linkend=\"transactions\" /> for more information about transaction handling and demarcation. The previous example also skipped any error handling and rollback."
msgstr ""
#. Tag: para
-#: tutorial.xml:574
#, no-c-format
msgid "To run this, we will make use of the Maven exec plugin to call our class with the necessary classpath setup: <command>mvn exec:java -Dexec.mainClass=\"org.hibernate.tutorial.EventManager\" -Dexec.args=\"store\"</command>"
msgstr ""
#. Tag: para
-#: tutorial.xml:581
#, no-c-format
msgid "You may need to perform <command>mvn compile</command> first."
msgstr ""
#. Tag: para
-#: tutorial.xml:586
#, no-c-format
msgid "You should see Hibernate starting up and, depending on your configuration, lots of log output. Towards the end, the following line will be displayed:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:591
-#, no-c-format
-msgid "<![CDATA[[java] Hibernate: insert into EVENTS (EVENT_DATE, title, EVENT_ID) values (?, ?, ?)]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:593
#, no-c-format
msgid "This is the <literal>INSERT</literal> executed by Hibernate."
msgstr ""
#. Tag: para
-#: tutorial.xml:597
#, no-c-format
msgid "To list stored events an option is added to the main method:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:601
-#, no-c-format
-msgid ""
- "<![CDATA[ if (args[0].equals(\"store\")) {\n"
- " mgr.createAndStoreEvent(\"My Event\", new Date());\n"
- " }\n"
- " else if (args[0].equals(\"list\")) {\n"
- " List events = mgr.listEvents();\n"
- " for (int i = 0; i < events.size(); i++) {\n"
- " Event theEvent = (Event) events.get(i);\n"
- " System.out.println(\n"
- " \"Event: \" + theEvent.getTitle() + \" Time: \" + theEvent.getDate()\n"
- " );\n"
- " }\n"
- " }]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:603
#, no-c-format
msgid "A new <literal>listEvents() method is also added</literal>:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:607
-#, no-c-format
-msgid ""
- "<![CDATA[ private List listEvents() {\n"
- " Session session = HibernateUtil.getSessionFactory().getCurrentSession();\n"
- " session.beginTransaction();\n"
- " List result = session.createQuery(\"from Event\").list();\n"
- " session.getTransaction().commit();\n"
- " return result;\n"
- " }]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:609
#, no-c-format
-msgid "Here, we are using a Hibernate Query Language (HQL) query to load all existing <literal>Event</literal> objects from the database. Hibernate will generate the appropriate SQL, send it to the database and populate <literal>Event</literal> objects with the data. You can create more complex queries with HQL. See <xref linkend=\"queryhql\"/> for more information."
+msgid "Here, we are using a Hibernate Query Language (HQL) query to load all existing <literal>Event</literal> objects from the database. Hibernate will generate the appropriate SQL, send it to the database and populate <literal>Event</literal> objects with the data. You can create more complex queries with HQL. See <xref linkend=\"queryhql\" /> for more information."
msgstr ""
#. Tag: para
-#: tutorial.xml:617
#, no-c-format
msgid "Now we can call our new functionality, again using the Maven exec plugin: <command>mvn exec:java -Dexec.mainClass=\"org.hibernate.tutorial.EventManager\" -Dexec.args=\"list\"</command>"
msgstr ""
#. Tag: title
-#: tutorial.xml:627
#, no-c-format
msgid "Part 2 - Mapping associations"
msgstr ""
#. Tag: para
-#: tutorial.xml:629
#, no-c-format
msgid "So far we have mapped a single persistent entity class to a table in isolation. Let's expand on that a bit and add some class associations. We will add people to the application and store a list of events in which they participate."
msgstr ""
#. Tag: title
-#: tutorial.xml:637
#, no-c-format
msgid "Mapping the Person class"
msgstr ""
#. Tag: para
-#: tutorial.xml:639
#, no-c-format
msgid "The first cut of the <literal>Person</literal> class looks like this:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:643
-#, no-c-format
-msgid ""
- "<![CDATA[package org.hibernate.tutorial.domain;\n"
- "\n"
- "public class Person {\n"
- "\n"
- " private Long id;\n"
- " private int age;\n"
- " private String firstname;\n"
- " private String lastname;\n"
- "\n"
- " public Person() {}\n"
- "\n"
- " // Accessor methods for all properties, private setter for 'id'\n"
- "\n"
- "}]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:645
#, no-c-format
msgid "Save this to a file named <filename>src/main/java/org/hibernate/tutorial/domain/Person.java</filename>"
msgstr ""
#. Tag: para
-#: tutorial.xml:650
#, no-c-format
msgid "Next, create the new mapping file as <filename>src/main/resources/org/hibernate/tutorial/domain/Person.hbm.xml</filename>"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:655
-#, no-c-format
-msgid ""
- "<![CDATA[<hibernate-mapping package=\"org.hibernate.tutorial.domain\">\n"
- "\n"
- " <class name=\"Person\" table=\"PERSON\">\n"
- " <id name=\"id\" column=\"PERSON_ID\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <property name=\"age\"/>\n"
- " <property name=\"firstname\"/>\n"
- " <property name=\"lastname\"/>\n"
- " </class>\n"
- "\n"
- "</hibernate-mapping>]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:657
#, no-c-format
msgid "Finally, add the new mapping to Hibernate's configuration:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:661
-#, no-c-format
-msgid ""
- "<![CDATA[<mapping resource=\"events/Event.hbm.xml\"/>\n"
- "<mapping resource=\"events/Person.hbm.xml\"/>]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:663
#, no-c-format
msgid "Create an association between these two entities. Persons can participate in events, and events have participants. The design questions you have to deal with are: directionality, multiplicity, and collection behavior."
msgstr ""
#. Tag: title
-#: tutorial.xml:673
#, no-c-format
msgid "A unidirectional Set-based association"
msgstr ""
#. Tag: para
-#: tutorial.xml:675
#, no-c-format
msgid "By adding a collection of events to the <literal>Person</literal> class, you can easily navigate to the events for a particular person, without executing an explicit query - by calling <literal>Person#getEvents</literal>. Multi-valued associations are represented in Hibernate by one of the Java Collection Framework contracts; here we choose a <interfacename>java.util.Set</interfacename> because the collection will not contain duplicate elements and the ordering is not relevant to our examples:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:686
-#, no-c-format
-msgid ""
- "<![CDATA[public class Person {\n"
- "\n"
- " private Set events = new HashSet();\n"
- "\n"
- " public Set getEvents() {\n"
- " return events;\n"
- " }\n"
- "\n"
- " public void setEvents(Set events) {\n"
- " this.events = events;\n"
- " }\n"
- "}]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:688
#, no-c-format
msgid "Before mapping this association, let's consider the other side. We could just keep this unidirectional or create another collection on the <literal>Event</literal>, if we wanted to be able to navigate it from both directions. This is not necessary, from a functional perspective. You can always execute an explicit query to retrieve the participants for a particular event. This is a design choice left to you, but what is clear from this discussion is the multiplicity of the association: \"many\" valued on both sides is called a <emphasis>many-to-many</emphasis> association. Hence, we use Hibernate's many-to-many mapping:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:701
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Person\" table=\"PERSON\">\n"
- " <id name=\"id\" column=\"PERSON_ID\">\n"
- " <generator class=\"native\"/>\n"
- " </id>\n"
- " <property name=\"age\"/>\n"
- " <property name=\"firstname\"/>\n"
- " <property name=\"lastname\"/>\n"
- "\n"
- " <set name=\"events\" table=\"PERSON_EVENT\">\n"
- " <key column=\"PERSON_ID\"/>\n"
- " <many-to-many column=\"EVENT_ID\" class=\"Event\"/>\n"
- " </set>\n"
- "\n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:703
#, no-c-format
msgid "Hibernate supports a broad range of collection mappings, a <literal>set</literal> being most common. For a many-to-many association, or <emphasis>n:m</emphasis> entity relationship, an association table is required. Each row in this table represents a link between a person and an event. The table name is decalred using the <literal>table</literal> attribute of the <literal>set</literal> element. The identifier column name in the association, for the person side, is defined with the <literal>key</literal> element, the column name for the event's side with the <literal>column</literal> attribute of the <literal>many-to-many</literal>. You also have to tell Hibernate the class of the objects in your collection (the class on the other side of the collection of references)."
msgstr ""
#. Tag: para
-#: tutorial.xml:719
#, no-c-format
msgid "The database schema for this mapping is therefore:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:723
-#, no-c-format
-msgid ""
- "<![CDATA[\n"
- " _____________ __________________\n"
- " | | | | _____________\n"
- " | EVENTS | | PERSON_EVENT | | |\n"
- " |_____________| |__________________| | PERSON |\n"
- " | | | | |_____________|\n"
- " | *EVENT_ID | <--> | *EVENT_ID | | |\n"
- " | EVENT_DATE | | *PERSON_ID | <--> | *PERSON_ID |\n"
- " | TITLE | |__________________| | AGE |\n"
- " |_____________| | FIRSTNAME |\n"
- " | LASTNAME |\n"
- " |_____________|\n"
- " ]]>"
-msgstr ""
-
#. Tag: title
-#: tutorial.xml:728
#, no-c-format
msgid "Working the association"
msgstr ""
#. Tag: para
-#: tutorial.xml:730
#, no-c-format
msgid "Now we will bring some people and events together in a new method in <literal>EventManager</literal>:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:734
-#, no-c-format
-msgid ""
- "<![CDATA[ private void addPersonToEvent(Long personId, Long eventId) {\n"
- " Session session = HibernateUtil.getSessionFactory().getCurrentSession();\n"
- " session.beginTransaction();\n"
- "\n"
- " Person aPerson = (Person) session.load(Person.class, personId);\n"
- " Event anEvent = (Event) session.load(Event.class, eventId);\n"
- " aPerson.getEvents().add(anEvent);\n"
- "\n"
- " session.getTransaction().commit();\n"
- " }]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:736
#, no-c-format
msgid "After loading a <literal>Person</literal> and an <literal>Event</literal>, simply modify the collection using the normal collection methods. There is no explicit call to <literal>update()</literal> or <literal>save()</literal>; Hibernate automatically detects that the collection has been modified and needs to be updated. This is called <emphasis>automatic dirty checking</emphasis>. You can also try it by modifying the name or the date property of any of your objects. As long as they are in <emphasis>persistent</emphasis> state, that is, bound to a particular Hibernate <interfacename>org.hibernate.Session</interfacename>, Hibernate monitors any changes and executes SQL in a write-behind fashion. The process of synchronizing the memory state with the database, usually only at the end of a unit of work, is called <emphasis>flushing</emphasis>. In our code, the unit of work ends with a commit, or rollback, of the database transaction."
msgstr ""
#. Tag: para
-#: tutorial.xml:755
#, no-c-format
msgid "You can load person and event in different units of work. Or you can modify an object outside of a <interfacename>org.hibernate.Session</interfacename>, when it is not in persistent state (if it was persistent before, this state is called <emphasis>detached</emphasis>). You can even modify a collection when it is detached:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:764
-#, no-c-format
-msgid ""
- "<![CDATA[ private void addPersonToEvent(Long personId, Long eventId) {\n"
- " Session session = HibernateUtil.getSessionFactory().getCurrentSession();\n"
- " session.beginTransaction();\n"
- "\n"
- " Person aPerson = (Person) session\n"
- " .createQuery(\"select p from Person p left join fetch p.events where p.id = :pid\")\n"
- " .setParameter(\"pid\", personId)\n"
- " .uniqueResult(); // Eager fetch the collection so we can use it detached\n"
- " Event anEvent = (Event) session.load(Event.class, eventId);\n"
- "\n"
- " session.getTransaction().commit();\n"
- "\n"
- " // End of first unit of work\n"
- "\n"
- " aPerson.getEvents().add(anEvent); // aPerson (and its collection) is detached\n"
- "\n"
- " // Begin second unit of work\n"
- "\n"
- " Session session2 = HibernateUtil.getSessionFactory().getCurrentSession();\n"
- " session2.beginTransaction();\n"
- " session2.update(aPerson); // Reattachment of aPerson\n"
- "\n"
- " session2.getTransaction().commit();\n"
- " }]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:766
#, no-c-format
msgid "The call to <literal>update</literal> makes a detached object persistent again by binding it to a new unit of work, so any modifications you made to it while detached can be saved to the database. This includes any modifications (additions/deletions) you made to a collection of that entity object."
msgstr ""
#. Tag: para
-#: tutorial.xml:775
#, no-c-format
msgid "This is not much use in our example, but it is an important concept you can incorporate into your own application. Complete this exercise by adding a new action to the main method of the <literal>EventManager</literal> and call it from the command line. If you need the identifiers of a person and an event - the <literal>save()</literal> method returns it (you might have to modify some of the previous methods to return that identifier):"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:783
-#, no-c-format
-msgid ""
- "<![CDATA[ else if (args[0].equals(\"addpersontoevent\")) {\n"
- " Long eventId = mgr.createAndStoreEvent(\"My Event\", new Date());\n"
- " Long personId = mgr.createAndStorePerson(\"Foo\", \"Bar\");\n"
- " mgr.addPersonToEvent(personId, eventId);\n"
- " System.out.println(\"Added person \" + personId + \" to event \" + eventId);\n"
- " }]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:785
#, no-c-format
msgid "This is an example of an association between two equally important classes : two entities. As mentioned earlier, there are other classes and types in a typical model, usually \"less important\". Some you have already seen, like an <literal>int</literal> or a <classname>java.lang.String</classname>. We call these classes <emphasis>value types</emphasis>, and their instances <emphasis>depend</emphasis> on a particular entity. Instances of these types do not have their own identity, nor are they shared between entities. Two persons do not reference the same <literal>firstname</literal> object, even if they have the same first name. Value types cannot only be found in the JDK , but you can also write dependent classes yourself such as an <literal>Address</literal> or <literal>MonetaryAmount</literal> class. In fact, in a Hibernate application all JDK classes are considered value types."
msgstr ""
#. Tag: para
-#: tutorial.xml:803
#, no-c-format
msgid "You can also design a collection of value types. This is conceptually different from a collection of references to other entities, but looks almost the same in Java."
msgstr ""
#. Tag: title
-#: tutorial.xml:812
#, no-c-format
msgid "Collection of values"
msgstr ""
#. Tag: para
-#: tutorial.xml:814
#, no-c-format
msgid "Let's add a collection of email addresses to the <literal>Person</literal> entity. This will be represented as a <interfacename>java.util.Set</interfacename> of <classname>java.lang.String</classname> instances:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:820
-#, no-c-format
-msgid ""
- "<![CDATA[ private Set emailAddresses = new HashSet();\n"
- "\n"
- " public Set getEmailAddresses() {\n"
- " return emailAddresses;\n"
- " }\n"
- "\n"
- " public void setEmailAddresses(Set emailAddresses) {\n"
- " this.emailAddresses = emailAddresses;\n"
- " }]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:822
#, no-c-format
msgid "The mapping of this <literal>Set</literal> is as follows:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:826
-#, no-c-format
-msgid ""
- "<![CDATA[ <set name=\"emailAddresses\" table=\"PERSON_EMAIL_ADDR\">\n"
- " <key column=\"PERSON_ID\"/>\n"
- " <element type=\"string\" column=\"EMAIL_ADDR\"/>\n"
- " </set>]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:828
#, no-c-format
msgid "The difference compared with the earlier mapping is the use of the <literal>element</literal> part which tells Hibernate that the collection does not contain references to another entity, but is rather a collection whose elements are values types, here specifically of type <literal>string</literal>. The lowercase name tells you it is a Hibernate mapping type/converter. Again the <literal>table</literal> attribute of the <literal>set</literal> element determines the table name for the collection. The <literal>key</literal> element defines the foreign-key column name in the collection table. The <literal>column</literal> attribute in the <literal>element</literal> element defines the column name where the email address values will actually be stored."
msgstr ""
#. Tag: para
-#: tutorial.xml:844
#, no-c-format
msgid "Here is the updated schema:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:848
-#, no-c-format
-msgid ""
- "<![CDATA[\n"
- " _____________ __________________\n"
- " | | | | _____________\n"
- " | EVENTS | | PERSON_EVENT | | | ___________________\n"
- " |_____________| |__________________| | PERSON | | |\n"
- " | | | | |_____________| | PERSON_EMAIL_ADDR |\n"
- " | *EVENT_ID | <--> | *EVENT_ID | | | |___________________|\n"
- " | EVENT_DATE | | *PERSON_ID | <--> | *PERSON_ID | <--> | *PERSON_ID |\n"
- " | TITLE | |__________________| | AGE | | *EMAIL_ADDR |\n"
- " |_____________| | FIRSTNAME | |___________________|\n"
- " | LASTNAME |\n"
- " |_____________|\n"
- " ]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:850
#, no-c-format
msgid "You can see that the primary key of the collection table is in fact a composite key that uses both columns. This also implies that there cannot be duplicate email addresses per person, which is exactly the semantics we need for a set in Java."
msgstr ""
#. Tag: para
-#: tutorial.xml:856
#, no-c-format
msgid "You can now try to add elements to this collection, just like we did before by linking persons and events. It is the same code in Java:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:861
-#, no-c-format
-msgid ""
- "<![CDATA[ private void addEmailToPerson(Long personId, String emailAddress) {\n"
- " Session session = HibernateUtil.getSessionFactory().getCurrentSession();\n"
- " session.beginTransaction();\n"
- "\n"
- " Person aPerson = (Person) session.load(Person.class, personId);\n"
- " // adding to the emailAddress collection might trigger a lazy load of the collection\n"
- " aPerson.getEmailAddresses().add(emailAddress);\n"
- "\n"
- " session.getTransaction().commit();\n"
- " }]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:863
#, no-c-format
msgid "This time we did not use a <emphasis>fetch</emphasis> query to initialize the collection. Monitor the SQL log and try to optimize this with an eager fetch."
msgstr ""
#. Tag: title
-#: tutorial.xml:872
#, no-c-format
msgid "Bi-directional associations"
msgstr ""
#. Tag: para
-#: tutorial.xml:874
#, no-c-format
msgid "Next you will map a bi-directional association. You will make the association between person and event work from both sides in Java. The database schema does not change, so you will still have many-to-many multiplicity."
msgstr ""
#. Tag: para
-#: tutorial.xml:882
#, no-c-format
msgid "A relational database is more flexible than a network programming language, in that it does not need a navigation direction; data can be viewed and retrieved in any possible way."
msgstr ""
#. Tag: para
-#: tutorial.xml:890
#, no-c-format
msgid "First, add a collection of participants to the <literal>Event</literal> class:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:895
-#, no-c-format
-msgid ""
- "<![CDATA[ private Set participants = new HashSet();\n"
- "\n"
- " public Set getParticipants() {\n"
- " return participants;\n"
- " }\n"
- "\n"
- " public void setParticipants(Set participants) {\n"
- " this.participants = participants;\n"
- " }]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:897
#, no-c-format
msgid "Now map this side of the association in <literal>Event.hbm.xml</literal>."
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:901
-#, no-c-format
-msgid ""
- "<![CDATA[ <set name=\"participants\" table=\"PERSON_EVENT\" inverse=\"true\">\n"
- " <key column=\"EVENT_ID\"/>\n"
- " <many-to-many column=\"PERSON_ID\" class=\"events.Person\"/>\n"
- " </set>]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:903
#, no-c-format
msgid "These are normal <literal>set</literal> mappings in both mapping documents. Notice that the column names in <literal>key</literal> and <literal>many-to-many</literal> swap in both mapping documents. The most important addition here is the <literal>inverse=\"true\"</literal> attribute in the <literal>set</literal> element of the <literal>Event</literal>'s collection mapping."
msgstr ""
#. Tag: para
-#: tutorial.xml:911
#, no-c-format
msgid "What this means is that Hibernate should take the other side, the <literal>Person</literal> class, when it needs to find out information about the link between the two. This will be a lot easier to understand once you see how the bi-directional link between our two entities is created."
msgstr ""
#. Tag: title
-#: tutorial.xml:920
#, no-c-format
msgid "Working bi-directional links"
msgstr ""
#. Tag: para
-#: tutorial.xml:922
#, no-c-format
msgid "First, keep in mind that Hibernate does not affect normal Java semantics. How did we create a link between a <literal>Person</literal> and an <literal>Event</literal> in the unidirectional example? You add an instance of <literal>Event</literal> to the collection of event references, of an instance of <literal>Person</literal>. If you want to make this link bi-directional, you have to do the same on the other side by adding a <literal>Person</literal> reference to the collection in an <literal>Event</literal>. This process of \"setting the link on both sides\" is absolutely necessary with bi-directional links."
msgstr ""
#. Tag: para
-#: tutorial.xml:932
#, no-c-format
msgid "Many developers program defensively and create link management methods to correctly set both sides (for example, in <literal>Person</literal>):"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:937
-#, no-c-format
-msgid ""
- "<![CDATA[ protected Set getEvents() {\n"
- " return events;\n"
- " }\n"
- "\n"
- " protected void setEvents(Set events) {\n"
- " this.events = events;\n"
- " }\n"
- "\n"
- " public void addToEvent(Event event) {\n"
- " this.getEvents().add(event);\n"
- " event.getParticipants().add(this);\n"
- " }\n"
- "\n"
- " public void removeFromEvent(Event event) {\n"
- " this.getEvents().remove(event);\n"
- " event.getParticipants().remove(this);\n"
- " }]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:939
#, no-c-format
msgid "The get and set methods for the collection are now protected. This allows classes in the same package and subclasses to still access the methods, but prevents everybody else from altering the collections directly. Repeat the steps for the collection on the other side."
msgstr ""
#. Tag: para
-#: tutorial.xml:946
#, no-c-format
msgid "What about the <literal>inverse</literal> mapping attribute? For you, and for Java, a bi-directional link is simply a matter of setting the references on both sides correctly. Hibernate, however, does not have enough information to correctly arrange SQL <literal>INSERT</literal> and <literal>UPDATE</literal> statements (to avoid constraint violations). Making one side of the association <literal>inverse</literal> tells Hibernate to consider it a <emphasis>mirror</emphasis> of the other side. That is all that is necessary for Hibernate to resolve any issues that arise when transforming a directional navigation model to a SQL database schema. The rules are straightforward: all bi-directional associations need one side as <literal>inverse</literal>. In a one-to-many association it has to be the many-side, and in many-to-many association you can select either side."
msgstr ""
#. Tag: title
-#: tutorial.xml:962
#, no-c-format
msgid "Part 3 - The EventManager web application"
msgstr ""
#. Tag: para
-#: tutorial.xml:964
#, no-c-format
msgid "A Hibernate web application uses <literal>Session</literal> and <literal>Transaction</literal> almost like a standalone application. However, some common patterns are useful. You can now write an <literal>EventManagerServlet</literal>. This servlet can list all events stored in the database, and it provides an HTML form to enter new events."
msgstr ""
#. Tag: title
-#: tutorial.xml:972
#, no-c-format
msgid "Writing the basic servlet"
msgstr ""
#. Tag: para
-#: tutorial.xml:974
#, no-c-format
msgid "First we need create our basic processing servlet. Since our servlet only handles HTTP <literal>GET</literal> requests, we will only implement the <literal>doGet()</literal> method:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:980
-#, no-c-format
-msgid ""
- "<![CDATA[package org.hibernate.tutorial.web;\n"
- "\n"
- "// Imports\n"
- "\n"
- "public class EventManagerServlet extends HttpServlet {\n"
- "\n"
- " protected void doGet(\n"
- " HttpServletRequest request,\n"
- " HttpServletResponse response) throws ServletException, IOException {\n"
- "\n"
- " SimpleDateFormat dateFormatter = new SimpleDateFormat( \"dd.MM.yyyy\" );\n"
- "\n"
- " try {\n"
- " // Begin unit of work\n"
- " HibernateUtil.getSessionFactory().getCurrentSession().beginTransaction();\n"
- "\n"
- " // Process request and render page...\n"
- "\n"
- " // End unit of work\n"
- " HibernateUtil.getSessionFactory().getCurrentSession().getTransaction().commit();\n"
- " }\n"
- " catch (Exception ex) {\n"
- " HibernateUtil.getSessionFactory().getCurrentSession().getTransaction().rollback();\n"
- " if ( ServletException.class.isInstance( ex ) ) {\n"
- " throw ( ServletException ) ex;\n"
- " }\n"
- " else {\n"
- " throw new ServletException( ex );\n"
- " }\n"
- " }\n"
- " }\n"
- "\n"
- "}]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:982
#, no-c-format
msgid "Save this servlet as <filename>src/main/java/org/hibernate/tutorial/web/EventManagerServlet.java</filename>"
msgstr ""
#. Tag: para
-#: tutorial.xml:987
#, no-c-format
msgid "The pattern applied here is called <emphasis>session-per-request</emphasis>. When a request hits the servlet, a new Hibernate <literal>Session</literal> is opened through the first call to <literal>getCurrentSession()</literal> on the <literal>SessionFactory</literal>. A database transaction is then started. All data access occurs inside a transaction irrespective of whether the data is read or written. Do not use the auto-commit mode in applications."
msgstr ""
#. Tag: para
-#: tutorial.xml:996
#, no-c-format
msgid "Do <emphasis>not</emphasis> use a new Hibernate <literal>Session</literal> for every database operation. Use one Hibernate <literal>Session</literal> that is scoped to the whole request. Use <literal>getCurrentSession()</literal>, so that it is automatically bound to the current Java thread."
msgstr ""
#. Tag: para
-#: tutorial.xml:1003
#, no-c-format
msgid "Next, the possible actions of the request are processed and the response HTML is rendered. We will get to that part soon."
msgstr ""
#. Tag: para
-#: tutorial.xml:1008
#, no-c-format
msgid "Finally, the unit of work ends when processing and rendering are complete. If any problems occurred during processing or rendering, an exception will be thrown and the database transaction rolled back. This completes the <literal>session-per-request</literal> pattern. Instead of the transaction demarcation code in every servlet, you could also write a servlet filter. See the Hibernate website and Wiki for more information about this pattern called <emphasis>Open Session in View</emphasis>. You will need it as soon as you consider rendering your view in JSP, not in a servlet."
msgstr ""
#. Tag: title
-#: tutorial.xml:1022
#, no-c-format
msgid "Processing and rendering"
msgstr ""
#. Tag: para
-#: tutorial.xml:1024
#, no-c-format
msgid "Now you can implement the processing of the request and the rendering of the page."
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:1028
-#, no-c-format
-msgid ""
- "<![CDATA[ // Write HTML header\n"
- " PrintWriter out = response.getWriter();\n"
- " out.println(\"<html><head><title>Event Manager</title></head><body>\");\n"
- "\n"
- " // Handle actions\n"
- " if ( \"store\".equals(request.getParameter(\"action\")) ) {\n"
- "\n"
- " String eventTitle = request.getParameter(\"eventTitle\");\n"
- " String eventDate = request.getParameter(\"eventDate\");\n"
- "\n"
- " if ( \"\".equals(eventTitle) || \"\".equals(eventDate) ) {\n"
- " out.println(\"<b><i>Please enter event title and date.</i></b>\");\n"
- " }\n"
- " else {\n"
- " createAndStoreEvent(eventTitle, dateFormatter.parse(eventDate));\n"
- " out.println(\"<b><i>Added event.</i></b>\");\n"
- " }\n"
- " }\n"
- "\n"
- " // Print page\n"
- " printEventForm(out);\n"
- " listEvents(out, dateFormatter);\n"
- "\n"
- " // Write HTML footer\n"
- " out.println(\"</body></html>\");\n"
- " out.flush();\n"
- " out.close();]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:1030
#, no-c-format
msgid "This coding style, with a mix of Java and HTML, would not scale in a more complex application—keep in mind that we are only illustrating basic Hibernate concepts in this tutorial. The code prints an HTML header and a footer. Inside this page, an HTML form for event entry and a list of all events in the database are printed. The first method is trivial and only outputs HTML:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:1039
-#, no-c-format
-msgid ""
- "<![CDATA[ private void printEventForm(PrintWriter out) {\n"
- " out.println(\"<h2>Add new event:</h2>\");\n"
- " out.println(\"<form>\");\n"
- " out.println(\"Title: <input name='eventTitle' length='50'/><br/>\");\n"
- " out.println(\"Date (e.g. 24.12.2009): <input name='eventDate' length='10'/><br/>\");\n"
- " out.println(\"<input type='submit' name='action' value='store'/>\");\n"
- " out.println(\"</form>\");\n"
- " }]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:1041
#, no-c-format
msgid "The <literal>listEvents()</literal> method uses the Hibernate <literal>Session</literal> bound to the current thread to execute a query:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:1047
-#, no-c-format
-msgid ""
- "<![CDATA[ private void listEvents(PrintWriter out, SimpleDateFormat dateFormatter) {\n"
- "\n"
- " List result = HibernateUtil.getSessionFactory()\n"
- " .getCurrentSession().createCriteria(Event.class).list();\n"
- " if (result.size() > 0) {\n"
- " out.println(\"<h2>Events in database:</h2>\");\n"
- " out.println(\"<table border='1'>\");\n"
- " out.println(\"<tr>\");\n"
- " out.println(\"<th>Event title</th>\");\n"
- " out.println(\"<th>Event date</th>\");\n"
- " out.println(\"</tr>\");\n"
- " Iterator it = result.iterator();\n"
- " while (it.hasNext()) {\n"
- " Event event = (Event) it.next();\n"
- " out.println(\"<tr>\");\n"
- " out.println(\"<td>\" + event.getTitle() + \"</td>\");\n"
- " out.println(\"<td>\" + dateFormatter.format(event.getDate()) + \"</td>\");\n"
- " out.println(\"</tr>\");\n"
- " }\n"
- " out.println(\"</table>\");\n"
- " }\n"
- " }]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:1049
#, no-c-format
msgid "Finally, the <literal>store</literal> action is dispatched to the <literal>createAndStoreEvent()</literal> method, which also uses the <literal>Session</literal> of the current thread:"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:1055
-#, no-c-format
-msgid ""
- "<![CDATA[ protected void createAndStoreEvent(String title, Date theDate) {\n"
- " Event theEvent = new Event();\n"
- " theEvent.setTitle(title);\n"
- " theEvent.setDate(theDate);\n"
- "\n"
- " HibernateUtil.getSessionFactory()\n"
- " .getCurrentSession().save(theEvent);\n"
- " }]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:1057
#, no-c-format
msgid "The servlet is now complete. A request to the servlet will be processed in a single <literal>Session</literal> and <literal>Transaction</literal>. As earlier in the standalone application, Hibernate can automatically bind these objects to the current thread of execution. This gives you the freedom to layer your code and access the <literal>SessionFactory</literal> in any way you like. Usually you would use a more sophisticated design and move the data access code into data access objects (the DAO pattern). See the Hibernate Wiki for more examples."
msgstr ""
#. Tag: title
-#: tutorial.xml:1071
#, no-c-format
msgid "Deploying and testing"
msgstr ""
#. Tag: para
-#: tutorial.xml:1073
#, no-c-format
msgid "To deploy this application for testing we must create a Web ARchive (WAR). First we must define the WAR descriptor as <filename>src/main/webapp/WEB-INF/web.xml</filename>"
msgstr ""
-#. Tag: programlisting
-#: tutorial.xml:1079
-#, no-c-format
-msgid ""
- "<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
- "<web-app version=\"2.4\"\n"
- " xmlns=\"http://java.sun.com/xml/ns/j2ee\"\n"
- " xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
- " xsi:schemaLocation=\"http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd\">\n"
- "\n"
- " <servlet>\n"
- " <servlet-name>Event Manager</servlet-name>\n"
- " <servlet-class>org.hibernate.tutorial.web.EventManagerServlet</servlet-class>\n"
- " </servlet>\n"
- "\n"
- " <servlet-mapping>\n"
- " <servlet-name>Event Manager</servlet-name>\n"
- " <url-pattern>/eventmanager</url-pattern>\n"
- " </servlet-mapping>\n"
- "</web-app>]]>"
-msgstr ""
-
#. Tag: para
-#: tutorial.xml:1081
#, no-c-format
msgid "To build and deploy call <literal>mvn package</literal> in your project directory and copy the <filename>hibernate-tutorial.war</filename> file into your Tomcat <filename>webapps</filename> directory."
msgstr ""
#. Tag: para
-#: tutorial.xml:1088
#, no-c-format
-msgid "If you do not have Tomcat installed, download it from <ulink url=\"http://tomcat.apache.org/\"></ulink> and follow the installation instructions. Our application requires no changes to the standard Tomcat configuration."
+msgid "If you do not have Tomcat installed, download it from <ulink url=\"http://tomcat.apache.org/\" /> and follow the installation instructions. Our application requires no changes to the standard Tomcat configuration."
msgstr ""
#. Tag: para
-#: tutorial.xml:1096
#, no-c-format
msgid "Once deployed and Tomcat is running, access the application at <literal>http://localhost:8080/hibernate-tutorial/eventmanager</literal>. Make sure you watch the Tomcat log to see Hibernate initialize when the first request hits your servlet (the static initializer in <literal>HibernateUtil</literal> is called) and to get the detailed output if any exceptions occurs."
msgstr ""
#. Tag: title
-#: tutorial.xml:1109
#, no-c-format
msgid "Summary"
msgstr ""
#. Tag: para
-#: tutorial.xml:1111
#, no-c-format
msgid "This tutorial covered the basics of writing a simple standalone Hibernate application and a small web application. More tutorials are available from the Hibernate <ulink url=\"http://hibernate.org\">website</ulink>."
msgstr ""
Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/xml.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/xml.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/content/xml.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,355 +1,143 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-10 21:02+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-01-08T04:07:20\n"
+"PO-Revision-Date: 2010-01-08T04:07:20\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
-#: xml.xml:29
#, no-c-format
msgid "XML Mapping"
msgstr ""
-#. Tag: emphasis
-#: xml.xml:31
+#. Tag: para
#, no-c-format
-msgid "XML Mapping is an experimental feature in Hibernate 3.0 and is currently under active development."
+msgid "<emphasis> XML Mapping is an experimental feature in Hibernate 3.0 and is currently under active development. </emphasis>"
msgstr ""
#. Tag: title
-#: xml.xml:37
#, no-c-format
msgid "Working with XML data"
msgstr ""
#. Tag: para
-#: xml.xml:39
#, no-c-format
msgid "Hibernate allows you to work with persistent XML data in much the same way you work with persistent POJOs. A parsed XML tree can be thought of as another way of representing the relational data at the object level, instead of POJOs."
msgstr ""
#. Tag: para
-#: xml.xml:46
#, no-c-format
msgid "Hibernate supports dom4j as API for manipulating XML trees. You can write queries that retrieve dom4j trees from the database and have any modification you make to the tree automatically synchronized to the database. You can even take an XML document, parse it using dom4j, and write it to the database with any of Hibernate's basic operations: <literal>persist(), saveOrUpdate(), merge(), delete(), replicate()</literal> (merging is not yet supported)."
msgstr ""
#. Tag: para
-#: xml.xml:56
#, no-c-format
msgid "This feature has many applications including data import/export, externalization of entity data via JMS or SOAP and XSLT-based reporting."
msgstr ""
#. Tag: para
-#: xml.xml:61
#, no-c-format
msgid "A single mapping can be used to simultaneously map properties of a class and nodes of an XML document to the database, or, if there is no class to map, it can be used to map just the XML."
msgstr ""
#. Tag: title
-#: xml.xml:68
#, no-c-format
msgid "Specifying XML and class mapping together"
msgstr ""
#. Tag: para
-#: xml.xml:70
#, no-c-format
msgid "Here is an example of mapping a POJO and XML simultaneously:"
msgstr ""
-#. Tag: programlisting
-#: xml.xml:74
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Account\" \n"
- " table=\"ACCOUNTS\" \n"
- " node=\"account\">\n"
- " \n"
- " <id name=\"accountId\" \n"
- " column=\"ACCOUNT_ID\" \n"
- " node=\"@id\"/>\n"
- " \n"
- " <many-to-one name=\"customer\" \n"
- " column=\"CUSTOMER_ID\" \n"
- " node=\"customer/@id\" \n"
- " embed-xml=\"false\"/>\n"
- " \n"
- " <property name=\"balance\" \n"
- " column=\"BALANCE\" \n"
- " node=\"balance\"/>\n"
- " \n"
- " ...\n"
- " \n"
- "</class>]]>"
-msgstr ""
-
#. Tag: title
-#: xml.xml:78
#, no-c-format
msgid "Specifying only an XML mapping"
msgstr ""
#. Tag: para
-#: xml.xml:80
#, no-c-format
msgid "Here is an example where there is no POJO class:"
msgstr ""
-#. Tag: programlisting
-#: xml.xml:84
-#, no-c-format
-msgid ""
- "<![CDATA[<class entity-name=\"Account\" \n"
- " table=\"ACCOUNTS\" \n"
- " node=\"account\">\n"
- " \n"
- " <id name=\"id\" \n"
- " column=\"ACCOUNT_ID\" \n"
- " node=\"@id\" \n"
- " type=\"string\"/>\n"
- " \n"
- " <many-to-one name=\"customerId\" \n"
- " column=\"CUSTOMER_ID\" \n"
- " node=\"customer/@id\" \n"
- " embed-xml=\"false\" \n"
- " entity-name=\"Customer\"/>\n"
- " \n"
- " <property name=\"balance\" \n"
- " column=\"BALANCE\" \n"
- " node=\"balance\" \n"
- " type=\"big_decimal\"/>\n"
- " \n"
- " ...\n"
- " \n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: xml.xml:86
#, no-c-format
msgid "This mapping allows you to access the data as a dom4j tree, or as a graph of property name/value pairs or java <literal>Map</literal>s. The property names are purely logical constructs that can be referred to in HQL queries."
msgstr ""
#. Tag: title
-#: xml.xml:97
#, no-c-format
msgid "XML mapping metadata"
msgstr ""
#. Tag: para
-#: xml.xml:99
#, no-c-format
msgid "A range of Hibernate mapping elements accept the <literal>node</literal> attribute. This lets you specify the name of an XML attribute or element that holds the property or entity data. The format of the <literal>node</literal> attribute must be one of the following:"
msgstr ""
#. Tag: para
-#: xml.xml:108
#, no-c-format
msgid "<literal>\"element-name\"</literal>: map to the named XML element"
msgstr ""
#. Tag: para
-#: xml.xml:111
#, no-c-format
msgid "<literal>\"@attribute-name\"</literal>: map to the named XML attribute"
msgstr ""
#. Tag: para
-#: xml.xml:114
#, no-c-format
msgid "<literal>\".\"</literal>: map to the parent element"
msgstr ""
#. Tag: para
-#: xml.xml:117
#, no-c-format
msgid "<literal>\"element-name/@attribute-name\"</literal>: map to the named attribute of the named element"
msgstr ""
#. Tag: para
-#: xml.xml:124
#, no-c-format
msgid "For collections and single valued associations, there is an additional <literal>embed-xml</literal> attribute. If <literal>embed-xml=\"true\"</literal>, the default, the XML tree for the associated entity (or collection of value type) will be embedded directly in the XML tree for the entity that owns the association. Otherwise, if <literal>embed-xml=\"false\"</literal>, then only the referenced identifier value will appear in the XML for single point associations and collections will not appear at all."
msgstr ""
#. Tag: para
-#: xml.xml:134
#, no-c-format
msgid "Do not leave <literal>embed-xml=\"true\"</literal> for too many associations, since XML does not deal well with circularity."
msgstr ""
-#. Tag: programlisting
-#: xml.xml:139
-#, no-c-format
-msgid ""
- "<![CDATA[<class name=\"Customer\" \n"
- " table=\"CUSTOMER\" \n"
- " node=\"customer\">\n"
- " \n"
- " <id name=\"id\" \n"
- " column=\"CUST_ID\" \n"
- " node=\"@id\"/>\n"
- " \n"
- " <map name=\"accounts\" \n"
- " node=\".\" \n"
- " embed-xml=\"true\">\n"
- " <key column=\"CUSTOMER_ID\" \n"
- " not-null=\"true\"/>\n"
- " <map-key column=\"SHORT_DESC\" \n"
- " node=\"@short-desc\" \n"
- " type=\"string\"/>\n"
- " <one-to-many entity-name=\"Account\"\n"
- " embed-xml=\"false\" \n"
- " node=\"account\"/>\n"
- " </map>\n"
- " \n"
- " <component name=\"name\" \n"
- " node=\"name\">\n"
- " <property name=\"firstName\" \n"
- " node=\"first-name\"/>\n"
- " <property name=\"initial\" \n"
- " node=\"initial\"/>\n"
- " <property name=\"lastName\" \n"
- " node=\"last-name\"/>\n"
- " </component>\n"
- " \n"
- " ...\n"
- " \n"
- "</class>]]>"
-msgstr ""
-
#. Tag: para
-#: xml.xml:141
#, no-c-format
msgid "In this case, the collection of account ids is embedded, but not the actual account data. The following HQL query:"
msgstr ""
-#. Tag: programlisting
-#: xml.xml:146
-#, no-c-format
-msgid "<![CDATA[from Customer c left join fetch c.accounts where c.lastName like :lastName]]>"
-msgstr ""
-
#. Tag: para
-#: xml.xml:148
#, no-c-format
msgid "would return datasets such as this:"
msgstr ""
-#. Tag: programlisting
-#: xml.xml:152
-#, no-c-format
-msgid ""
- "<![CDATA[<customer id=\"123456789\">\n"
- " <account short-desc=\"Savings\">987632567</account>\n"
- " <account short-desc=\"Credit Card\">985612323</account>\n"
- " <name>\n"
- " <first-name>Gavin</first-name>\n"
- " <initial>A</initial>\n"
- " <last-name>King</last-name>\n"
- " </name>\n"
- " ...\n"
- "</customer>]]>"
-msgstr ""
-
#. Tag: para
-#: xml.xml:154
#, no-c-format
msgid "If you set <literal>embed-xml=\"true\"</literal> on the <literal><one-to-many></literal> mapping, the data might look more like this:"
msgstr ""
-#. Tag: programlisting
-#: xml.xml:159
-#, no-c-format
-msgid ""
- "<![CDATA[<customer id=\"123456789\">\n"
- " <account id=\"987632567\" short-desc=\"Savings\">\n"
- " <customer id=\"123456789\"/>\n"
- " <balance>100.29</balance>\n"
- " </account>\n"
- " <account id=\"985612323\" short-desc=\"Credit Card\">\n"
- " <customer id=\"123456789\"/>\n"
- " <balance>-2370.34</balance>\n"
- " </account>\n"
- " <name>\n"
- " <first-name>Gavin</first-name>\n"
- " <initial>A</initial>\n"
- " <last-name>King</last-name>\n"
- " </name>\n"
- " ...\n"
- "</customer>]]>"
-msgstr ""
-
#. Tag: title
-#: xml.xml:165
#, no-c-format
msgid "Manipulating XML data"
msgstr ""
#. Tag: para
-#: xml.xml:167
#, no-c-format
msgid "You can also re-read and update XML documents in the application. You can do this by obtaining a dom4j session:"
msgstr ""
-#. Tag: programlisting
-#: xml.xml:172
-#, no-c-format
-msgid ""
- "<![CDATA[Document doc = ....;\n"
- " \n"
- "Session session = factory.openSession();\n"
- "Session dom4jSession = session.getSession(EntityMode.DOM4J);\n"
- "Transaction tx = session.beginTransaction();\n"
- "\n"
- "List results = dom4jSession\n"
- " .createQuery(\"from Customer c left join fetch c.accounts where c.lastName like :lastName\")\n"
- " .list();\n"
- "for ( int i=0; i<results.size(); i++ ) {\n"
- " //add the customer data to the XML document\n"
- " Element customer = (Element) results.get(i);\n"
- " doc.add(customer);\n"
- "}\n"
- "\n"
- "tx.commit();\n"
- "session.close();]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: xml.xml:174
-#, no-c-format
-msgid ""
- "<![CDATA[Session session = factory.openSession();\n"
- "Session dom4jSession = session.getSession(EntityMode.DOM4J);\n"
- "Transaction tx = session.beginTransaction();\n"
- "\n"
- "Element cust = (Element) dom4jSession.get(\"Customer\", customerId);\n"
- "for ( int i=0; i<results.size(); i++ ) {\n"
- " Element customer = (Element) results.get(i);\n"
- " //change the customer name in the XML and database\n"
- " Element name = customer.element(\"name\");\n"
- " name.element(\"first-name\").setText(firstName);\n"
- " name.element(\"initial\").setText(initial);\n"
- " name.element(\"last-name\").setText(lastName);\n"
- "}\n"
- "\n"
- "tx.commit();\n"
- "session.close();]]>"
-msgstr ""
-
#. Tag: para
-#: xml.xml:176
#, no-c-format
msgid "When implementing XML-based data import/export, it is useful to combine this feature with Hibernate's <literal>replicate()</literal> operation."
msgstr ""
Deleted: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/legal_notice.pot
===================================================================
--- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/legal_notice.pot 2010-02-08 04:50:03 UTC (rev 18716)
+++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pot/legal_notice.pot 2010-02-08 04:56:55 UTC (rev 18717)
@@ -1,58 +0,0 @@
-# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
-#
-#, fuzzy
-msgid ""
-msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-06-16 18:47+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-xml2pot; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#: legal_notice.xml:28
-#, no-c-format
-msgid "Legal Notice"
-msgstr ""
-
-#. Tag: address
-#: legal_notice.xml:30
-#, no-c-format
-msgid "<street>1801 Varsity Drive</street> <city>Raleigh</city>, <state>NC</state><postcode>27606-2072</postcode><country>USA</country> <phone>Phone: +1 919 754 3700</phone> <phone>Phone: 888 733 4281</phone> <fax>Fax: +1 919 754 3701</fax> <pob>PO Box 13588</pob><city>Research Triangle Park</city>, <state>NC</state><postcode>27709</postcode><country>USA</country>"
-msgstr ""
-
-#. Tag: para
-#: legal_notice.xml:39
-#, no-c-format
-msgid "Copyright <trademark class=\"copyright\"></trademark> 2007 by Red Hat, Inc. This copyrighted material is made available to anyone wishing to use, modify, copy, or redistribute it subject to the terms and conditions of the GNU <ulink url=\"http://www.gnu.org/licenses/lgpl-2.1.html\">Lesser General Public License</ulink>, as published by the Free Software Foundation."
-msgstr ""
-
-#. Tag: para
-#: legal_notice.xml:45
-#, no-c-format
-msgid "Red Hat and the Red Hat \"Shadow Man\" logo are registered trademarks of Red Hat, Inc. in the United States and other countries."
-msgstr ""
-
-#. Tag: para
-#: legal_notice.xml:48
-#, no-c-format
-msgid "All other trademarks referenced herein are the property of their respective owners."
-msgstr ""
-
-#. Tag: para
-#: legal_notice.xml:51
-#, no-c-format
-msgid "The GPG fingerprint of the security at redhat.com key is:"
-msgstr ""
-
-#. Tag: para
-#: legal_notice.xml:54
-#, no-c-format
-msgid "CA 20 86 86 2B D6 9D FC 65 F6 EC C4 21 91 80 CD DB 42 A6 0E"
-msgstr ""
-
More information about the hibernate-commits
mailing list