[hibernate-commits] Hibernate SVN: r14128 - in
core/trunk/documentation/manual: pot and 14 other directories.
hibernate-commits at lists.jboss.org
hibernate-commits at lists.jboss.org
Mon Oct 22 11:48:12 EDT 2007
Author: steve.ebersole at jboss.com
Date: 2007-10-22 11:48:10 -0400 (Mon, 22 Oct 2007)
New Revision: 14128
Added:
core/trunk/documentation/manual/pot/
core/trunk/documentation/manual/pot/Hibernate_Reference.pot
core/trunk/documentation/manual/pot/content/
core/trunk/documentation/manual/pot/content/architecture.pot
core/trunk/documentation/manual/pot/content/association_mapping.pot
core/trunk/documentation/manual/pot/content/basic_mapping.pot
core/trunk/documentation/manual/pot/content/batch.pot
core/trunk/documentation/manual/pot/content/best_practices.pot
core/trunk/documentation/manual/pot/content/collection_mapping.pot
core/trunk/documentation/manual/pot/content/component_mapping.pot
core/trunk/documentation/manual/pot/content/configuration.pot
core/trunk/documentation/manual/pot/content/events.pot
core/trunk/documentation/manual/pot/content/example_mappings.pot
core/trunk/documentation/manual/pot/content/example_parentchild.pot
core/trunk/documentation/manual/pot/content/example_weblog.pot
core/trunk/documentation/manual/pot/content/filters.pot
core/trunk/documentation/manual/pot/content/inheritance_mapping.pot
core/trunk/documentation/manual/pot/content/performance.pot
core/trunk/documentation/manual/pot/content/persistent_classes.pot
core/trunk/documentation/manual/pot/content/preface.pot
core/trunk/documentation/manual/pot/content/query_criteria.pot
core/trunk/documentation/manual/pot/content/query_hql.pot
core/trunk/documentation/manual/pot/content/query_sql.pot
core/trunk/documentation/manual/pot/content/session_api.pot
core/trunk/documentation/manual/pot/content/toolset_guide.pot
core/trunk/documentation/manual/pot/content/transactions.pot
core/trunk/documentation/manual/pot/content/tutorial.pot
core/trunk/documentation/manual/pot/content/xml.pot
core/trunk/documentation/manual/pot/legal_notice.pot
core/trunk/documentation/manual/translations/
core/trunk/documentation/manual/translations/es-ES/
core/trunk/documentation/manual/translations/es-ES/Hibernate_Reference.po
core/trunk/documentation/manual/translations/es-ES/content/
core/trunk/documentation/manual/translations/es-ES/content/architecture.po
core/trunk/documentation/manual/translations/es-ES/content/association_mapping.po
core/trunk/documentation/manual/translations/es-ES/content/basic_mapping.po
core/trunk/documentation/manual/translations/es-ES/content/batch.po
core/trunk/documentation/manual/translations/es-ES/content/best_practices.po
core/trunk/documentation/manual/translations/es-ES/content/collection_mapping.po
core/trunk/documentation/manual/translations/es-ES/content/component_mapping.po
core/trunk/documentation/manual/translations/es-ES/content/configuration.po
core/trunk/documentation/manual/translations/es-ES/content/events.po
core/trunk/documentation/manual/translations/es-ES/content/example_mappings.po
core/trunk/documentation/manual/translations/es-ES/content/example_parentchild.po
core/trunk/documentation/manual/translations/es-ES/content/example_weblog.po
core/trunk/documentation/manual/translations/es-ES/content/filters.po
core/trunk/documentation/manual/translations/es-ES/content/inheritance_mapping.po
core/trunk/documentation/manual/translations/es-ES/content/performance.po
core/trunk/documentation/manual/translations/es-ES/content/persistent_classes.po
core/trunk/documentation/manual/translations/es-ES/content/preface.po
core/trunk/documentation/manual/translations/es-ES/content/query_criteria.po
core/trunk/documentation/manual/translations/es-ES/content/query_hql.po
core/trunk/documentation/manual/translations/es-ES/content/query_sql.po
core/trunk/documentation/manual/translations/es-ES/content/quickstart.po
core/trunk/documentation/manual/translations/es-ES/content/session_api.po
core/trunk/documentation/manual/translations/es-ES/content/toolset_guide.po
core/trunk/documentation/manual/translations/es-ES/content/transactions.po
core/trunk/documentation/manual/translations/es-ES/content/tutorial.po
core/trunk/documentation/manual/translations/es-ES/content/xml.po
core/trunk/documentation/manual/translations/es-ES/legal_notice.po
core/trunk/documentation/manual/translations/fr-FR/
core/trunk/documentation/manual/translations/fr-FR/Hibernate_Reference.po
core/trunk/documentation/manual/translations/fr-FR/content/
core/trunk/documentation/manual/translations/fr-FR/content/architecture.po
core/trunk/documentation/manual/translations/fr-FR/content/association_mapping.po
core/trunk/documentation/manual/translations/fr-FR/content/basic_mapping.po
core/trunk/documentation/manual/translations/fr-FR/content/batch.po
core/trunk/documentation/manual/translations/fr-FR/content/best_practices.po
core/trunk/documentation/manual/translations/fr-FR/content/collection_mapping.po
core/trunk/documentation/manual/translations/fr-FR/content/component_mapping.po
core/trunk/documentation/manual/translations/fr-FR/content/configuration.po
core/trunk/documentation/manual/translations/fr-FR/content/events.po
core/trunk/documentation/manual/translations/fr-FR/content/example_mappings.po
core/trunk/documentation/manual/translations/fr-FR/content/example_parentchild.po
core/trunk/documentation/manual/translations/fr-FR/content/example_weblog.po
core/trunk/documentation/manual/translations/fr-FR/content/filters.po
core/trunk/documentation/manual/translations/fr-FR/content/inheritance_mapping.po
core/trunk/documentation/manual/translations/fr-FR/content/performance.po
core/trunk/documentation/manual/translations/fr-FR/content/persistent_classes.po
core/trunk/documentation/manual/translations/fr-FR/content/preface.po
core/trunk/documentation/manual/translations/fr-FR/content/query_criteria.po
core/trunk/documentation/manual/translations/fr-FR/content/query_hql.po
core/trunk/documentation/manual/translations/fr-FR/content/query_sql.po
core/trunk/documentation/manual/translations/fr-FR/content/quickstart.po
core/trunk/documentation/manual/translations/fr-FR/content/session_api.po
core/trunk/documentation/manual/translations/fr-FR/content/toolset_guide.po
core/trunk/documentation/manual/translations/fr-FR/content/transactions.po
core/trunk/documentation/manual/translations/fr-FR/content/tutorial.po
core/trunk/documentation/manual/translations/fr-FR/content/xml.po
core/trunk/documentation/manual/translations/fr-FR/legal_notice.po
core/trunk/documentation/manual/translations/ja-JP/
core/trunk/documentation/manual/translations/ja-JP/Hibernate_Reference.po
core/trunk/documentation/manual/translations/ja-JP/content/
core/trunk/documentation/manual/translations/ja-JP/content/architecture.po
core/trunk/documentation/manual/translations/ja-JP/content/association_mapping.po
core/trunk/documentation/manual/translations/ja-JP/content/basic_mapping.po
core/trunk/documentation/manual/translations/ja-JP/content/batch.po
core/trunk/documentation/manual/translations/ja-JP/content/best_practices.po
core/trunk/documentation/manual/translations/ja-JP/content/collection_mapping.po
core/trunk/documentation/manual/translations/ja-JP/content/component_mapping.po
core/trunk/documentation/manual/translations/ja-JP/content/configuration.po
core/trunk/documentation/manual/translations/ja-JP/content/events.po
core/trunk/documentation/manual/translations/ja-JP/content/example_mappings.po
core/trunk/documentation/manual/translations/ja-JP/content/example_parentchild.po
core/trunk/documentation/manual/translations/ja-JP/content/example_weblog.po
core/trunk/documentation/manual/translations/ja-JP/content/filters.po
core/trunk/documentation/manual/translations/ja-JP/content/inheritance_mapping.po
core/trunk/documentation/manual/translations/ja-JP/content/performance.po
core/trunk/documentation/manual/translations/ja-JP/content/persistent_classes.po
core/trunk/documentation/manual/translations/ja-JP/content/preface.po
core/trunk/documentation/manual/translations/ja-JP/content/query_criteria.po
core/trunk/documentation/manual/translations/ja-JP/content/query_hql.po
core/trunk/documentation/manual/translations/ja-JP/content/query_sql.po
core/trunk/documentation/manual/translations/ja-JP/content/quickstart.po
core/trunk/documentation/manual/translations/ja-JP/content/session_api.po
core/trunk/documentation/manual/translations/ja-JP/content/toolset_guide.po
core/trunk/documentation/manual/translations/ja-JP/content/transactions.po
core/trunk/documentation/manual/translations/ja-JP/content/tutorial.po
core/trunk/documentation/manual/translations/ja-JP/content/xml.po
core/trunk/documentation/manual/translations/ja-JP/legal_notice.po
core/trunk/documentation/manual/translations/ko-KR/
core/trunk/documentation/manual/translations/ko-KR/Hibernate_Reference.po
core/trunk/documentation/manual/translations/ko-KR/content/
core/trunk/documentation/manual/translations/ko-KR/content/architecture.po
core/trunk/documentation/manual/translations/ko-KR/content/association_mapping.po
core/trunk/documentation/manual/translations/ko-KR/content/basic_mapping.po
core/trunk/documentation/manual/translations/ko-KR/content/batch.po
core/trunk/documentation/manual/translations/ko-KR/content/best_practices.po
core/trunk/documentation/manual/translations/ko-KR/content/collection_mapping.po
core/trunk/documentation/manual/translations/ko-KR/content/component_mapping.po
core/trunk/documentation/manual/translations/ko-KR/content/configuration.po
core/trunk/documentation/manual/translations/ko-KR/content/events.po
core/trunk/documentation/manual/translations/ko-KR/content/example_mappings.po
core/trunk/documentation/manual/translations/ko-KR/content/example_parentchild.po
core/trunk/documentation/manual/translations/ko-KR/content/example_weblog.po
core/trunk/documentation/manual/translations/ko-KR/content/filters.po
core/trunk/documentation/manual/translations/ko-KR/content/inheritance_mapping.po
core/trunk/documentation/manual/translations/ko-KR/content/performance.po
core/trunk/documentation/manual/translations/ko-KR/content/persistent_classes.po
core/trunk/documentation/manual/translations/ko-KR/content/preface.po
core/trunk/documentation/manual/translations/ko-KR/content/query_criteria.po
core/trunk/documentation/manual/translations/ko-KR/content/query_hql.po
core/trunk/documentation/manual/translations/ko-KR/content/query_sql.po
core/trunk/documentation/manual/translations/ko-KR/content/quickstart.po
core/trunk/documentation/manual/translations/ko-KR/content/session_api.po
core/trunk/documentation/manual/translations/ko-KR/content/toolset_guide.po
core/trunk/documentation/manual/translations/ko-KR/content/transactions.po
core/trunk/documentation/manual/translations/ko-KR/content/tutorial.po
core/trunk/documentation/manual/translations/ko-KR/content/xml.po
core/trunk/documentation/manual/translations/ko-KR/legal_notice.po
core/trunk/documentation/manual/translations/pt-BR/
core/trunk/documentation/manual/translations/pt-BR/Hibernate_Reference.po
core/trunk/documentation/manual/translations/pt-BR/content/
core/trunk/documentation/manual/translations/pt-BR/content/architecture.po
core/trunk/documentation/manual/translations/pt-BR/content/association_mapping.po
core/trunk/documentation/manual/translations/pt-BR/content/basic_mapping.po
core/trunk/documentation/manual/translations/pt-BR/content/batch.po
core/trunk/documentation/manual/translations/pt-BR/content/best_practices.po
core/trunk/documentation/manual/translations/pt-BR/content/collection_mapping.po
core/trunk/documentation/manual/translations/pt-BR/content/component_mapping.po
core/trunk/documentation/manual/translations/pt-BR/content/configuration.po
core/trunk/documentation/manual/translations/pt-BR/content/events.po
core/trunk/documentation/manual/translations/pt-BR/content/example_mappings.po
core/trunk/documentation/manual/translations/pt-BR/content/example_parentchild.po
core/trunk/documentation/manual/translations/pt-BR/content/example_weblog.po
core/trunk/documentation/manual/translations/pt-BR/content/filters.po
core/trunk/documentation/manual/translations/pt-BR/content/inheritance_mapping.po
core/trunk/documentation/manual/translations/pt-BR/content/performance.po
core/trunk/documentation/manual/translations/pt-BR/content/persistent_classes.po
core/trunk/documentation/manual/translations/pt-BR/content/preface.po
core/trunk/documentation/manual/translations/pt-BR/content/query_criteria.po
core/trunk/documentation/manual/translations/pt-BR/content/query_hql.po
core/trunk/documentation/manual/translations/pt-BR/content/query_sql.po
core/trunk/documentation/manual/translations/pt-BR/content/quickstart.po
core/trunk/documentation/manual/translations/pt-BR/content/session_api.po
core/trunk/documentation/manual/translations/pt-BR/content/toolset_guide.po
core/trunk/documentation/manual/translations/pt-BR/content/transactions.po
core/trunk/documentation/manual/translations/pt-BR/content/tutorial.po
core/trunk/documentation/manual/translations/pt-BR/content/xml.po
core/trunk/documentation/manual/translations/pt-BR/legal_notice.po
core/trunk/documentation/manual/translations/zh-CN/
core/trunk/documentation/manual/translations/zh-CN/Hibernate_Reference.po
core/trunk/documentation/manual/translations/zh-CN/content/
core/trunk/documentation/manual/translations/zh-CN/content/architecture.po
core/trunk/documentation/manual/translations/zh-CN/content/association_mapping.po
core/trunk/documentation/manual/translations/zh-CN/content/basic_mapping.po
core/trunk/documentation/manual/translations/zh-CN/content/batch.po
core/trunk/documentation/manual/translations/zh-CN/content/best_practices.po
core/trunk/documentation/manual/translations/zh-CN/content/collection_mapping.po
core/trunk/documentation/manual/translations/zh-CN/content/component_mapping.po
core/trunk/documentation/manual/translations/zh-CN/content/configuration.po
core/trunk/documentation/manual/translations/zh-CN/content/events.po
core/trunk/documentation/manual/translations/zh-CN/content/example_mappings.po
core/trunk/documentation/manual/translations/zh-CN/content/example_parentchild.po
core/trunk/documentation/manual/translations/zh-CN/content/example_weblog.po
core/trunk/documentation/manual/translations/zh-CN/content/filters.po
core/trunk/documentation/manual/translations/zh-CN/content/inheritance_mapping.po
core/trunk/documentation/manual/translations/zh-CN/content/performance.po
core/trunk/documentation/manual/translations/zh-CN/content/persistent_classes.po
core/trunk/documentation/manual/translations/zh-CN/content/preface.po
core/trunk/documentation/manual/translations/zh-CN/content/query_criteria.po
core/trunk/documentation/manual/translations/zh-CN/content/query_hql.po
core/trunk/documentation/manual/translations/zh-CN/content/query_sql.po
core/trunk/documentation/manual/translations/zh-CN/content/quickstart.po
core/trunk/documentation/manual/translations/zh-CN/content/session_api.po
core/trunk/documentation/manual/translations/zh-CN/content/toolset_guide.po
core/trunk/documentation/manual/translations/zh-CN/content/transactions.po
core/trunk/documentation/manual/translations/zh-CN/content/tutorial.po
core/trunk/documentation/manual/translations/zh-CN/content/xml.po
core/trunk/documentation/manual/translations/zh-CN/legal_notice.po
Log:
translation po/gettext conversion
Added: core/trunk/documentation/manual/pot/Hibernate_Reference.pot
===================================================================
--- core/trunk/documentation/manual/pot/Hibernate_Reference.pot (rev 0)
+++ core/trunk/documentation/manual/pot/Hibernate_Reference.pot 2007-10-22 15:48:10 UTC (rev 14128)
@@ -0,0 +1,34 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2007-10-19 10:23-0500\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
+"Language-Team: LANGUAGE <LL at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./Hibernate_Reference.xml:33(None) ./Hibernate_Reference.xml:36(None)
+msgid "@@image: 'images/hibernate_logo_a.png'; md5=38bd6cfd79e676660440f316f4ab452c"
+msgstr ""
+
+#: ./Hibernate_Reference.xml:26(title)
+msgid "HIBERNATE - Relational Persistence for Idiomatic Java"
+msgstr ""
+
+#: ./Hibernate_Reference.xml:27(subtitle)
+msgid "Hibernate Reference Documentation"
+msgstr ""
+
+#: ./Hibernate_Reference.xml:30(issuenum)
+msgid "1"
+msgstr ""
+
+#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
+#: ./Hibernate_Reference.xml:0(None)
+msgid "translator-credits"
+msgstr ""
+
Added: core/trunk/documentation/manual/pot/content/architecture.pot
===================================================================
--- core/trunk/documentation/manual/pot/content/architecture.pot (rev 0)
+++ core/trunk/documentation/manual/pot/content/architecture.pot 2007-10-22 15:48:10 UTC (rev 14128)
@@ -0,0 +1,256 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2007-10-19 10:28-0500\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
+"Language-Team: LANGUAGE <LL at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: architecture.xml:32(None)
+msgid "@@image: '../images/overview.svg'; md5=2d9211eace02ecef615f7dd42beec14c"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: architecture.xml:35(None)
+msgid "@@image: '../images/overview.png'; md5=a2b5f0f7dc75d9773305d4d824880e8c"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: architecture.xml:54(None)
+msgid "@@image: '../images/lite.svg'; md5=2178e70b3b165736d33b085dcad93699"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: architecture.xml:57(None)
+msgid "@@image: '../images/lite.png'; md5=7dd864188937e2dfef42a706235f74c3"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: architecture.xml:68(None)
+msgid "@@image: '../images/full_cream.svg'; md5=4ef192f03e90e451e5dcb287d2709687"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: architecture.xml:71(None)
+msgid "@@image: '../images/full_cream.png'; md5=c3ee197b49364a876bc5867d5c2c6db7"
+msgstr ""
+
+#: architecture.xml:21(title)
+msgid "Architecture"
+msgstr ""
+
+#: architecture.xml:24(title)
+msgid "Overview"
+msgstr ""
+
+#: architecture.xml:26(para)
+msgid "A (very) high-level view of the Hibernate architecture:"
+msgstr ""
+
+#: architecture.xml:39(para)
+msgid "This diagram shows Hibernate using the database and configuration data to provide persistence services (and persistent objects) to the application."
+msgstr ""
+
+#: architecture.xml:44(para)
+msgid "We would like to show a more detailed view of the runtime architecture. Unfortunately, Hibernate is flexible and supports several approaches. We will show the two extremes. The \"lite\" 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 ""
+
+#: architecture.xml:61(para)
+msgid "The \"full cream\" architecture abstracts the application away from the underlying JDBC/JTA APIs and lets Hibernate take care of the details."
+msgstr ""
+
+#: architecture.xml:80(term)
+msgid "SessionFactory (<literal>org.hibernate.SessionFactory</literal>)"
+msgstr ""
+
+#: architecture.xml:82(para)
+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>. Might hold an optional (second-level) cache of data that is reusable between transactions, at a process- or cluster-level."
+msgstr ""
+
+#: architecture.xml:92(term)
+msgid "Session (<literal>org.hibernate.Session</literal>)"
+msgstr ""
+
+#: architecture.xml:94(para)
+msgid "A single-threaded, short-lived object representing a conversation between the application and the persistent store. Wraps a JDBC connection. Factory for <literal>Transaction</literal>. Holds a mandatory (first-level) cache of persistent objects, used when navigating the object graph or looking up objects by identifier."
+msgstr ""
+
+#: architecture.xml:104(term)
+msgid "Persistent objects and collections"
+msgstr ""
+
+#: architecture.xml:106(para)
+msgid "Short-lived, single threaded objects containing persistent state and business function. These might be ordinary JavaBeans/POJOs, the only special thing about them is that they are currently associated with (exactly one) <literal>Session</literal>. As soon as the <literal>Session</literal> is closed, they will be detached and free to use in any application layer (e.g. directly as data transfer objects to and from presentation)."
+msgstr ""
+
+#: architecture.xml:117(term)
+msgid "Transient and detached objects and collections"
+msgstr ""
+
+#: architecture.xml:119(para)
+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 ""
+
+#: architecture.xml:128(term)
+msgid "Transaction (<literal>org.hibernate.Transaction</literal>)"
+msgstr ""
+
+#: architecture.xml:130(para)
+msgid "(Optional) A single-threaded, short-lived object used by the application to specify atomic units of work. Abstracts application from 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 ""
+
+#: architecture.xml:141(term)
+msgid "ConnectionProvider (<literal>org.hibernate.connection.ConnectionProvider</literal>)"
+msgstr ""
+
+#: architecture.xml:143(para)
+msgid "(Optional) A factory for (and pool of) JDBC connections. Abstracts application from underlying <literal>Datasource</literal> or <literal>DriverManager</literal>. Not exposed to application, but can be extended/implemented by the developer."
+msgstr ""
+
+#: architecture.xml:151(term)
+msgid "TransactionFactory (<literal>org.hibernate.TransactionFactory</literal>)"
+msgstr ""
+
+#: architecture.xml:153(para)
+msgid "(Optional) A factory for <literal>Transaction</literal> instances. Not exposed to the application, but can be extended/implemented by the developer."
+msgstr ""
+
+#: architecture.xml:160(emphasis)
+msgid "Extension Interfaces"
+msgstr ""
+
+#: architecture.xml:162(para)
+msgid "Hibernate offers many optional extension interfaces you can implement to customize the behavior of your persistence layer. See the API documentation for details."
+msgstr ""
+
+#: architecture.xml:75(para)
+msgid "Heres some definitions of the objects in the diagrams: <placeholder-1/>"
+msgstr ""
+
+#: architecture.xml:171(para)
+msgid "Given a \"lite\" architecture, the application bypasses the <literal>Transaction</literal>/<literal>TransactionFactory</literal> and/or <literal>ConnectionProvider</literal> APIs to talk to JTA or JDBC directly."
+msgstr ""
+
+#: architecture.xml:179(title)
+msgid "Instance states"
+msgstr ""
+
+#: architecture.xml:180(para)
+msgid "An instance of a persistent classes may be in one of three different states, which are defined with respect to a <emphasis>persistence context</emphasis>. The Hibernate <literal>Session</literal> object is the persistence context:"
+msgstr ""
+
+#: architecture.xml:188(term)
+msgid "transient"
+msgstr ""
+
+#: architecture.xml:190(para)
+msgid "The instance is not, and has never been associated with any persistence context. It has no persistent identity (primary key value)."
+msgstr ""
+
+#: architecture.xml:198(term)
+msgid "persistent"
+msgstr ""
+
+#: architecture.xml:200(para)
+msgid "The instance is currently associated with a persistence context. It has a persistent identity (primary key value) and, perhaps, a corresponding row in the database. For a particular persistence context, Hibernate <emphasis>guarantees</emphasis> that persistent identity is equivalent to Java identity (in-memory location of the object)."
+msgstr ""
+
+#: architecture.xml:212(term)
+msgid "detached"
+msgstr ""
+
+#: architecture.xml:214(para)
+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, perhaps, a corrsponding row in the database. For detached instances, Hibernate makes no guarantees about the relationship between persistent identity and Java identity."
+msgstr ""
+
+#: architecture.xml:229(title)
+msgid "JMX Integration"
+msgstr ""
+
+#: architecture.xml:231(para)
+msgid "JMX is the J2EE standard for management of Java components. Hibernate may be managed via a JMX standard service. We provide an MBean implementation in the distribution, <literal>org.hibernate.jmx.HibernateService</literal>."
+msgstr ""
+
+#: architecture.xml:237(para)
+msgid "For an example how to deploy Hibernate as a JMX service on the JBoss Application Server, please see the JBoss User Guide. On JBoss AS, you also get these benefits if you deploy using JMX:"
+msgstr ""
+
+#: architecture.xml:245(para)
+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 you no longer have to manually open and close the <literal>Session</literal>, this becomes the job of a JBoss EJB interceptor. You also don't have to worry about transaction demarcation in your code anymore (unless you'd like to write a portable persistence layer of course, use the optional Hibernate <literal>Transaction</literal> API for this). You call the <literal>HibernateContext</literal> to access a <literal>Session</literal>."
+msgstr ""
+
+#: architecture.xml:257(para)
+msgid "<emphasis>HAR deployment:</emphasis> Usually you deploy the Hibernate JMX service using a JBoss service deployment descriptor (in an EAR and/or SAR file), it supports all the usual configuration options of a Hibernate <literal>SessionFactory</literal>. However, you still have to name all your mapping files in the deployment descriptor. If you decide to use the optional HAR deployment, JBoss will automatically detect all mapping files in your HAR file."
+msgstr ""
+
+#: architecture.xml:268(para)
+msgid "Consult the JBoss AS user guide for more information about these options."
+msgstr ""
+
+#: architecture.xml:272(para)
+msgid "Another feature available as a JMX service are runtime Hibernate statistics. See <xref linkend=\"configuration-optional-statistics\"/>."
+msgstr ""
+
+#: architecture.xml:279(title)
+msgid "JCA Support"
+msgstr ""
+
+#: architecture.xml:280(para)
+msgid "Hibernate may also be configured as a JCA connector. Please see the website for more details. Please note that Hibernate JCA support is still considered experimental."
+msgstr ""
+
+#: architecture.xml:287(title)
+msgid "Contextual Sessions"
+msgstr ""
+
+#: architecture.xml:288(para)
+msgid "Most applications using Hibernate need some form of \"contextual\" sessions, 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; and 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 ""
+
+#: architecture.xml:297(para)
+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. The Hibernate team maintains that, given the maturity of the numerous stand-alone <literal>JTA TransactionManager</literal> implementations out there, 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 is all you should ever need to use."
+msgstr ""
+
+#: architecture.xml:307(para)
+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 ""
+
+#: architecture.xml:314(para)
+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 ""
+
+#: architecture.xml:324(para)
+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 ""
+
+#: architecture.xml:332(para)
+msgid "<literal>org.hibernate.context.ThreadLocalSessionContext</literal> - current sessions are tracked by thread of execution. Again, see the Javadocs for details."
+msgstr ""
+
+#: architecture.xml:338(para)
+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 never open, flush, or close a <literal>Session</literal>."
+msgstr ""
+
+#: architecture.xml:347(para)
+msgid "The first two implementations provide a \"one session - one database transaction\" programming model, 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 programatic transaction demarcation in plain JSE without JTA, you are adviced to use the Hibernate <literal>Transaction</literal> API to hide the underlying transaction system from your code. If you use JTA, use the JTA interfaces to demarcate transactions. If you execute in an EJB container that supports CMT, transaction boundaries are defined declaratively and you don't need any transaction or session demarcation operations in your code. Refer to <xref linkend=\"transactions\"/> for more information and code examples."
+msgstr ""
+
+#: architecture.xml:359(para)
+msgid "The <literal>hibernate.current_session_context_class</literal> configuration parameter defines which <literal>org.hibernate.context.CurrentSessionContext</literal> implementation should be used. Note that for backwards compatibility, if this config param 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 ""
+
+#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
+#: architecture.xml:0(None)
+msgid "translator-credits"
+msgstr ""
+
Added: core/trunk/documentation/manual/pot/content/association_mapping.pot
===================================================================
--- core/trunk/documentation/manual/pot/content/association_mapping.pot (rev 0)
+++ core/trunk/documentation/manual/pot/content/association_mapping.pot 2007-10-22 15:48:10 UTC (rev 14128)
@@ -0,0 +1,160 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2007-10-19 10:28-0500\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
+"Language-Team: LANGUAGE <LL at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: association_mapping.xml:6(title)
+msgid "Association Mappings"
+msgstr ""
+
+#: association_mapping.xml:9(title)
+msgid "Introduction"
+msgstr ""
+
+#: association_mapping.xml:11(para)
+msgid "Association mappings are the often most difficult thing to get right. In this section we'll go through the canonical cases one by one, starting with unidirectional mappings, and then considering the bidirectional cases. We'll use <literal>Person</literal> and <literal>Address</literal> in all the examples."
+msgstr ""
+
+#: association_mapping.xml:19(para)
+msgid "We'll classify associations by whether or not they map to an intervening join table, and by multiplicity."
+msgstr ""
+
+#: association_mapping.xml:24(para)
+msgid "Nullable foreign keys are not considered good practice in traditional data modelling, so all our examples use not null foreign keys. This is not a requirement of Hibernate, and the mappings will all work if you drop the nullability constraints."
+msgstr ""
+
+#: association_mapping.xml:34(title)
+msgid "Unidirectional associations"
+msgstr ""
+
+#: association_mapping.xml:37(title) association_mapping.xml:195(title)
+msgid "many to one"
+msgstr ""
+
+#: association_mapping.xml:39(para)
+msgid "A <emphasis>unidirectional many-to-one association</emphasis> is the most common kind of unidirectional association."
+msgstr ""
+
+#: association_mapping.xml:66(title) association_mapping.xml:229(title) association_mapping.xml:373(title) association_mapping.xml:479(title)
+msgid "one to one"
+msgstr ""
+
+#: association_mapping.xml:68(para)
+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 ""
+
+#: association_mapping.xml:93(para)
+msgid "A <emphasis>unidirectional one-to-one association on a primary key</emphasis> usually uses a special id generator. (Notice that we've reversed the direction of the association in this example.)"
+msgstr ""
+
+#: association_mapping.xml:121(title) association_mapping.xml:161(title)
+msgid "one to many"
+msgstr ""
+
+#: association_mapping.xml:123(para)
+msgid "A <emphasis>unidirectional one-to-many association on a foreign key</emphasis> is a very unusual case, and is not really recommended."
+msgstr ""
+
+#: association_mapping.xml:149(para)
+msgid "We think it's better to use a join table for this kind of association."
+msgstr ""
+
+#: association_mapping.xml:158(title)
+msgid "Unidirectional associations with join tables"
+msgstr ""
+
+#: association_mapping.xml:163(para)
+msgid "A <emphasis>unidirectional one-to-many association on a join table</emphasis> is much preferred. Notice that by specifying <literal>unique=\"true\"</literal>, we have changed the multiplicity from many-to-many to one-to-many."
+msgstr ""
+
+#: association_mapping.xml:197(para)
+msgid "A <emphasis>unidirectional many-to-one association on a join table</emphasis> is quite common when the association is optional."
+msgstr ""
+
+#: association_mapping.xml:231(para)
+msgid "A <emphasis>unidirectional one-to-one association on a join table</emphasis> is extremely unusual, but possible."
+msgstr ""
+
+#: association_mapping.xml:265(title) association_mapping.xml:525(title)
+msgid "many to many"
+msgstr ""
+
+#: association_mapping.xml:267(para)
+msgid "Finally, we have a <emphasis>unidirectional many-to-many association</emphasis>."
+msgstr ""
+
+#: association_mapping.xml:298(title)
+msgid "Bidirectional associations"
+msgstr ""
+
+#: association_mapping.xml:301(title) association_mapping.xml:436(title)
+msgid "one to many / many to one"
+msgstr ""
+
+#: association_mapping.xml:303(para)
+msgid "A <emphasis>bidirectional many-to-one association</emphasis> is the most common kind of association. (This is the standard parent/child relationship.)"
+msgstr ""
+
+#: association_mapping.xml:333(para)
+msgid "If you use a <literal>List</literal> (or other indexed collection) you need to set the <literal>key</literal> column of the foreign key to <literal>not null</literal>, and let Hibernate 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 ""
+
+#: association_mapping.xml:361(para)
+msgid "It is important that you define <literal>not-null=\"true\"</literal> on the <literal><key></literal> element of the collection mapping if the underlying foreign key column is <literal>NOT NULL</literal>. Don't only declare <literal>not-null=\"true\"</literal> on a possible nested <literal><column></literal> element, but on the <literal><key></literal> element."
+msgstr ""
+
+#: association_mapping.xml:375(para)
+msgid "A <emphasis>bidirectional one-to-one association on a foreign key</emphasis> is quite common."
+msgstr ""
+
+#: association_mapping.xml:402(para)
+msgid "A <emphasis>bidirectional one-to-one association on a primary key</emphasis> uses the special id generator."
+msgstr ""
+
+#: association_mapping.xml:433(title)
+msgid "Bidirectional associations with join tables"
+msgstr ""
+
+#: association_mapping.xml:438(para)
+msgid "A <emphasis>bidirectional one-to-many association on a join table</emphasis>. Note that the <literal>inverse=\"true\"</literal> can go on either end of the association, on the collection, or on the join."
+msgstr ""
+
+#: association_mapping.xml:481(para)
+msgid "A <emphasis>bidirectional one-to-one association on a join table</emphasis> is extremely unusual, but possible."
+msgstr ""
+
+#: association_mapping.xml:527(para)
+msgid "Finally, we have a <emphasis>bidirectional many-to-many association</emphasis>."
+msgstr ""
+
+#: association_mapping.xml:564(title)
+msgid "More complex association mappings"
+msgstr ""
+
+#: association_mapping.xml:566(para)
+msgid "More complex association joins are <emphasis>extremely</emphasis> rare. Hibernate makes it possible to handle more complex situations 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, mapped as follows:"
+msgstr ""
+
+#: association_mapping.xml:584(para)
+msgid "Then we can map an association to the <emphasis>current</emphasis> instance (the one with null <literal>effectiveEndDate</literal>) using:"
+msgstr ""
+
+#: association_mapping.xml:596(para)
+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. Then an association to the employee's <emphasis>most recent</emphasis> employer (the one with the most recent <literal>startDate</literal>) might be mapped this way:"
+msgstr ""
+
+#: association_mapping.xml:617(para)
+msgid "You can get quite creative with this functionality, but it is usually more practical to handle these kinds of cases using HQL or a criteria query."
+msgstr ""
+
+#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
+#: association_mapping.xml:0(None)
+msgid "translator-credits"
+msgstr ""
+
Added: core/trunk/documentation/manual/pot/content/basic_mapping.pot
===================================================================
--- core/trunk/documentation/manual/pot/content/basic_mapping.pot (rev 0)
+++ core/trunk/documentation/manual/pot/content/basic_mapping.pot 2007-10-22 15:48:10 UTC (rev 14128)
@@ -0,0 +1,1532 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2007-10-19 10:29-0500\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
+"Language-Team: LANGUAGE <LL at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: basic_mapping.xml:5(title)
+msgid "Basic O/R Mapping"
+msgstr ""
+
+#: basic_mapping.xml:8(title)
+msgid "Mapping declaration"
+msgstr ""
+
+#: basic_mapping.xml:10(para)
+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, not table declarations."
+msgstr ""
+
+#: basic_mapping.xml:17(para)
+msgid "Note that, even though many Hibernate users choose to write the XML by hand, a number of tools exist to generate the mapping document, including XDoclet, Middlegen and AndroMDA."
+msgstr ""
+
+#: basic_mapping.xml:23(para)
+msgid "Lets kick off with an example mapping:"
+msgstr ""
+
+#: basic_mapping.xml:92(para)
+msgid "We will now discuss the content of the mapping document. We will only describe 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 ""
+
+#: basic_mapping.xml:103(title)
+msgid "Doctype"
+msgstr ""
+
+#: basic_mapping.xml:105(para)
+msgid "All XML mappings should declare the doctype shown. The actual DTD may 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 your DTD declaration against the contents of your claspath."
+msgstr ""
+
+#: basic_mapping.xml:115(title)
+msgid "EntityResolver"
+msgstr ""
+
+#: basic_mapping.xml:116(para)
+msgid "As mentioned previously, Hibernate will first attempt to resolve DTDs in its classpath. The manner in which 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 ""
+
+#: basic_mapping.xml:124(para)
+msgid "a <literal>hibernate namespace</literal> is recognized whenever the resolver encounteres a systemId starting with <literal>http://hibernate.sourceforge.net/</literal>; the resolver attempts to resolve these entities via the classlaoder which loaded the Hibernate classes."
+msgstr ""
+
+#: basic_mapping.xml:133(para)
+msgid "a <literal>user namespace</literal> is recognized whenever the resolver encounteres 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 ""
+
+#: basic_mapping.xml:142(para)
+msgid "An example of utilizing user namespacing:"
+msgstr ""
+
+#: basic_mapping.xml:160(para)
+msgid "Where <literal>types.xml</literal> is a resource in the <literal>your.domain</literal> package and contains a custom <xref linkend=\"mapping-types-custom\">typedef</xref>."
+msgstr ""
+
+#: basic_mapping.xml:168(title)
+msgid "hibernate-mapping"
+msgstr ""
+
+#: basic_mapping.xml:170(para)
+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 specified, tablenames will be qualified by the given schema and catalog names. If missing, tablenames will be unqualified. The <literal>default-cascade</literal> attribute specifies what cascade style should be assumed for properties and collections which do not specify a <literal>cascade</literal> attribute. The <literal>auto-import</literal> attribute lets us use unqualified class names in the query language, by default."
+msgstr ""
+
+#: basic_mapping.xml:202(para)
+msgid "<literal>schema</literal> (optional): The name of a database schema."
+msgstr ""
+
+#: basic_mapping.xml:207(para)
+msgid "<literal>catalog</literal> (optional): The name of a database catalog."
+msgstr ""
+
+#: basic_mapping.xml:212(para)
+msgid "<literal>default-cascade</literal> (optional - defaults to <literal>none</literal>): A default cascade style."
+msgstr ""
+
+#: basic_mapping.xml:218(para)
+msgid "<literal>default-access</literal> (optional - defaults to <literal>property</literal>): The strategy Hibernate should use for accessing all properties. Can be a custom implementation of <literal>PropertyAccessor</literal>."
+msgstr ""
+
+#: basic_mapping.xml:225(para)
+msgid "<literal>default-lazy</literal> (optional - defaults to <literal>true</literal>): The default value for unspecifed <literal>lazy</literal> attributes of class and collection mappings."
+msgstr ""
+
+#: basic_mapping.xml:232(para)
+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 ""
+
+#: basic_mapping.xml:239(para)
+msgid "<literal>package</literal> (optional): Specifies a package prefix to assume for unqualified class names in the mapping document."
+msgstr ""
+
+#: basic_mapping.xml:247(para)
+msgid "If you have two persistent classes with the same (unqualified) name, you should set <literal>auto-import=\"false\"</literal>. Hibernate will throw an exception if you attempt to assign two classes to the same \"imported\" name."
+msgstr ""
+
+#: basic_mapping.xml:253(para)
+msgid "Note that 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, e.g. <literal>Cat.hbm.xml</literal>, <literal>Dog.hbm.xml</literal>, or if using inheritance, <literal>Animal.hbm.xml</literal>."
+msgstr ""
+
+#: basic_mapping.xml:266(title) basic_mapping.xml:3077(literal)
+msgid "class"
+msgstr ""
+
+#: basic_mapping.xml:268(para)
+msgid "You may declare a persistent class using the <literal>class</literal> element:"
+msgstr ""
+
+#: basic_mapping.xml:322(para)
+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 ""
+
+#: basic_mapping.xml:329(para)
+msgid "<literal>table</literal> (optional - defaults to the unqualified class name): The name of its database table."
+msgstr ""
+
+#: basic_mapping.xml:335(para)
+msgid "<literal>discriminator-value</literal> (optional - defaults to the class name): A value that distiguishes individual subclasses, used for polymorphic behaviour. Acceptable values include <literal>null</literal> and <literal>not null</literal>."
+msgstr ""
+
+#: basic_mapping.xml:342(para)
+msgid "<literal>mutable</literal> (optional, defaults to <literal>true</literal>): Specifies that instances of the class are (not) mutable."
+msgstr ""
+
+#: basic_mapping.xml:348(para) basic_mapping.xml:2605(para)
+msgid "<literal>schema</literal> (optional): Override the schema name specified by the root <literal><hibernate-mapping></literal> element."
+msgstr ""
+
+#: basic_mapping.xml:354(para) basic_mapping.xml:2611(para)
+msgid "<literal>catalog</literal> (optional): Override the catalog name specified by the root <literal><hibernate-mapping></literal> element."
+msgstr ""
+
+#: basic_mapping.xml:360(para)
+msgid "<literal>proxy</literal> (optional): Specifies an interface to use for lazy initializing proxies. You may specify the name of the class itself."
+msgstr ""
+
+#: basic_mapping.xml:366(para)
+msgid "<literal>dynamic-update</literal> (optional, defaults to <literal>false</literal>): Specifies that <literal>UPDATE</literal> SQL should be generated at runtime and contain only those columns whose values have changed."
+msgstr ""
+
+#: basic_mapping.xml:373(para)
+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 ""
+
+#: basic_mapping.xml:380(para)
+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. In certain cases (actually, only when a transient object has been associated with a new session using <literal>update()</literal>), this means that Hibernate will perform an extra SQL <literal>SELECT</literal> to determine if an <literal>UPDATE</literal> is actually required."
+msgstr ""
+
+#: basic_mapping.xml:390(para)
+msgid "<literal>polymorphism</literal> (optional, defaults to <literal>implicit</literal>): Determines whether implicit or explicit query polymorphism is used."
+msgstr ""
+
+#: basic_mapping.xml:396(para)
+msgid "<literal>where</literal> (optional) specify an arbitrary SQL <literal>WHERE</literal> condition to be used when retrieving objects of this class"
+msgstr ""
+
+#: basic_mapping.xml:402(para)
+msgid "<literal>persister</literal> (optional): Specifies a custom <literal>ClassPersister</literal>."
+msgstr ""
+
+#: basic_mapping.xml:407(para)
+msgid "<literal>batch-size</literal> (optional, defaults to <literal>1</literal>) specify a \"batch size\" for fetching instances of this class by identifier."
+msgstr ""
+
+#: basic_mapping.xml:413(para)
+msgid "<literal>optimistic-lock</literal> (optional, defaults to <literal>version</literal>): Determines the optimistic locking strategy."
+msgstr ""
+
+#: basic_mapping.xml:419(para)
+msgid "<literal>lazy</literal> (optional): Lazy fetching may be completely disabled by setting <literal>lazy=\"false\"</literal>."
+msgstr ""
+
+#: basic_mapping.xml:425(para)
+msgid "<literal>entity-name</literal> (optional, defaults to the class name): Hibernate3 allows a class to be mapped multiple times (to different tables, potentially), and 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 ""
+
+#: basic_mapping.xml:435(para)
+msgid "<literal>check</literal> (optional): A SQL expression used to generate a multi-row <emphasis>check</emphasis> constraint for automatic schema generation."
+msgstr ""
+
+#: basic_mapping.xml:441(para)
+msgid "<literal>rowid</literal> (optional): Hibernate can use so called ROWIDs on databases which support. E.g. on Oracle, Hibernate can use the <literal>rowid</literal> extra column for fast updates if you set this option to <literal>rowid</literal>. A ROWID is an implementation detail and represents the physical location of a stored tuple."
+msgstr ""
+
+#: basic_mapping.xml:449(para)
+msgid "<literal>subselect</literal> (optional): Maps an immutable and read-only entity to a database subselect. Useful if you want to have a view instead of a base table, but don't. See below for more information."
+msgstr ""
+
+#: basic_mapping.xml:456(para)
+msgid "<literal>abstract</literal> (optional): Used to mark abstract superclasses in <literal><union-subclass></literal> hierarchies."
+msgstr ""
+
+#: basic_mapping.xml:464(para)
+msgid "It is perfectly acceptable for the named persistent class to be an interface. You would then declare implementing classes of that interface using the <literal><subclass></literal> element. You may persist any <emphasis>static</emphasis> inner class. You should specify the class name using the standard form ie. <literal>eg.Foo$Bar</literal>."
+msgstr ""
+
+#: basic_mapping.xml:471(para)
+msgid "Immutable classes, <literal>mutable=\"false\"</literal>, may not be updated or deleted by the application. This allows Hibernate to make some minor performance optimizations."
+msgstr ""
+
+#: basic_mapping.xml:476(para)
+msgid "The optional <literal>proxy</literal> attribute enables lazy initialization of persistent instances of the class. Hibernate will initially return CGLIB proxies which implement the named interface. The actual persistent object will be loaded when a method of the proxy is invoked. See \"Initializing collections and proxies\" below."
+msgstr ""
+
+#: basic_mapping.xml:483(para)
+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 the 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 and that 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 ""
+
+#: basic_mapping.xml:495(para)
+msgid "The <literal>persister</literal> attribute lets you customize the persistence strategy used for the class. You may, for example, specify your own subclass of <literal>org.hibernate.persister.EntityPersister</literal> or you might even provide a completely new implementation of the interface <literal>org.hibernate.persister.ClassPersister</literal> that implements persistence via, for example, 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 ""
+
+#: basic_mapping.xml:506(para)
+msgid "Note that the <literal>dynamic-update</literal> and <literal>dynamic-insert</literal> settings are not inherited by subclasses and so may also be specified on the <literal><subclass></literal> or <literal><joined-subclass></literal> elements. These settings may increase performance in some cases, but might actually decrease performance in others. Use judiciously."
+msgstr ""
+
+#: basic_mapping.xml:514(para)
+msgid "Use of <literal>select-before-update</literal> will usually decrease performance. It is very useful to prevent a database update trigger being called unnecessarily if you reattach a graph of detached instances to a <literal>Session</literal>."
+msgstr ""
+
+#: basic_mapping.xml:520(para)
+msgid "If you enable <literal>dynamic-update</literal>, you will have a choice of optimistic locking strategies:"
+msgstr ""
+
+#: basic_mapping.xml:526(para)
+msgid "<literal>version</literal> check the version/timestamp columns"
+msgstr ""
+
+#: basic_mapping.xml:531(para)
+msgid "<literal>all</literal> check all columns"
+msgstr ""
+
+#: basic_mapping.xml:536(para)
+msgid "<literal>dirty</literal> check the changed columns, allowing some concurrent updates"
+msgstr ""
+
+#: basic_mapping.xml:541(para)
+msgid "<literal>none</literal> do not use optimistic locking"
+msgstr ""
+
+#: basic_mapping.xml:546(para)
+msgid "We <emphasis>very</emphasis> strongly recommend that you use version/timestamp columns for optimistic locking with Hibernate. This is the optimal strategy with respect to performance and is the only strategy that correctly handles modifications made to detached instances (ie. when <literal>Session.merge()</literal> is used)."
+msgstr ""
+
+#: basic_mapping.xml:553(para)
+msgid "There is no difference between a view and a base table for a Hibernate mapping, as expected this is transparent at the database level (note that some DBMS don't support views properly, especially with updates). Sometimes you want to use a view, but can't create one in the database (ie. with a legacy schema). In this case, you can map an immutable and read-only entity to a given SQL subselect expression:"
+msgstr ""
+
+#: basic_mapping.xml:574(para)
+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 as both as an attribute and a nested mapping element."
+msgstr ""
+
+#: basic_mapping.xml:584(title)
+msgid "id"
+msgstr ""
+
+#: basic_mapping.xml:586(para)
+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 ""
+
+#: basic_mapping.xml:613(para)
+msgid "<literal>name</literal> (optional): The name of the identifier property."
+msgstr ""
+
+#: basic_mapping.xml:618(para)
+msgid "<literal>type</literal> (optional): A name that indicates the Hibernate type."
+msgstr ""
+
+#: basic_mapping.xml:623(para)
+msgid "<literal>column</literal> (optional - defaults to the property name): The name of the primary key column."
+msgstr ""
+
+#: basic_mapping.xml:629(para)
+msgid "<literal>unsaved-value</literal> (optional - defaults to a \"sensible\" value): An identifier 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."
+msgstr ""
+
+#: basic_mapping.xml:637(para) basic_mapping.xml:1187(para) basic_mapping.xml:1343(para) basic_mapping.xml:1433(para) basic_mapping.xml:1559(para) basic_mapping.xml:1775(para) basic_mapping.xml:1963(para) basic_mapping.xml:2162(para) basic_mapping.xml:2914(para)
+msgid "<literal>access</literal> (optional - defaults to <literal>property</literal>): The strategy Hibernate should use for accessing the property value."
+msgstr ""
+
+#: basic_mapping.xml:645(para)
+msgid "If the <literal>name</literal> attribute is missing, it is assumed that the class has no identifier property."
+msgstr ""
+
+#: basic_mapping.xml:650(para)
+msgid "The <literal>unsaved-value</literal> attribute is almost never needed in Hibernate3."
+msgstr ""
+
+#: basic_mapping.xml:654(para)
+msgid "There is an alternative <literal><composite-id></literal> declaration to allow access to legacy data with composite keys. We strongly discourage its use for anything else."
+msgstr ""
+
+#: basic_mapping.xml:660(title)
+msgid "Generator"
+msgstr ""
+
+#: basic_mapping.xml:662(para)
+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 ""
+
+#: basic_mapping.xml:684(literal)
+msgid "increment"
+msgstr ""
+
+#: basic_mapping.xml:686(para)
+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 ""
+
+#: basic_mapping.xml:695(literal)
+msgid "identity"
+msgstr ""
+
+#: basic_mapping.xml:697(para)
+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 ""
+
+#: basic_mapping.xml:705(literal)
+msgid "sequence"
+msgstr ""
+
+#: basic_mapping.xml:707(para)
+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 ""
+
+#: basic_mapping.xml:715(literal)
+msgid "hilo"
+msgstr ""
+
+#: basic_mapping.xml:717(para)
+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 ""
+
+#: basic_mapping.xml:727(literal)
+msgid "seqhilo"
+msgstr ""
+
+#: basic_mapping.xml:729(para)
+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 ""
+
+#: basic_mapping.xml:737(literal)
+msgid "uuid"
+msgstr ""
+
+#: basic_mapping.xml:739(para)
+msgid "uses a 128-bit UUID algorithm to generate identifiers of type string, unique within a network (the IP address is used). The UUID is encoded as a string of hexadecimal digits of length 32."
+msgstr ""
+
+#: basic_mapping.xml:747(literal)
+msgid "guid"
+msgstr ""
+
+#: basic_mapping.xml:749(para)
+msgid "uses a database-generated GUID string on MS SQL Server and MySQL."
+msgstr ""
+
+#: basic_mapping.xml:755(literal)
+msgid "native"
+msgstr ""
+
+#: basic_mapping.xml:757(para)
+msgid "picks <literal>identity</literal>, <literal>sequence</literal> or <literal>hilo</literal> depending upon the capabilities of the underlying database."
+msgstr ""
+
+#: basic_mapping.xml:765(literal)
+msgid "assigned"
+msgstr ""
+
+#: basic_mapping.xml:767(para)
+msgid "lets the application to 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 ""
+
+#: basic_mapping.xml:775(literal)
+msgid "select"
+msgstr ""
+
+#: basic_mapping.xml:777(para)
+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 ""
+
+#: basic_mapping.xml:784(literal)
+msgid "foreign"
+msgstr ""
+
+#: basic_mapping.xml:786(para)
+msgid "uses the identifier of another associated object. Usually used in conjunction with a <literal><one-to-one></literal> primary key association."
+msgstr ""
+
+#: basic_mapping.xml:793(literal)
+msgid "sequence-identity"
+msgstr ""
+
+#: basic_mapping.xml:795(para)
+msgid "a specialized sequence generation strategy which utilizes a database sequence for the actual value generation, but combines this with JDBC3 getGeneratedKeys to actually return the generated identifier value as part of the insert statement execution. This strategy is only known to be supported on Oracle 10g drivers targetted for JDK 1.4. Note comments on these insert statements are disabled due to a bug in the Oracle drivers."
+msgstr ""
+
+#: basic_mapping.xml:676(para)
+msgid "All generators implement the interface <literal>org.hibernate.id.IdentifierGenerator</literal>. This is a very simple interface; some applications may choose to provide their own specialized implementations. However, Hibernate provides a range of built-in implementations. There are shortcut names for the built-in generators: <placeholder-1/>"
+msgstr ""
+
+#: basic_mapping.xml:812(title)
+msgid "Hi/lo algorithm"
+msgstr ""
+
+#: basic_mapping.xml:813(para)
+msgid "The <literal>hilo</literal> and <literal>seqhilo</literal> generators provide two alternate implementations of the hi/lo algorithm, a favorite approach to identifier generation. The first implementation requires a \"special\" database table to hold the next available \"hi\" value. The second uses an Oracle-style sequence (where supported)."
+msgstr ""
+
+#: basic_mapping.xml:835(para)
+msgid "Unfortunately, you can't use <literal>hilo</literal> when supplying your own <literal>Connection</literal> to Hibernate. When Hibernate is using an application server datasource to obtain connections enlisted with JTA, you must properly configure the <literal>hibernate.transaction.manager_lookup_class</literal>."
+msgstr ""
+
+#: basic_mapping.xml:844(title)
+msgid "UUID algorithm"
+msgstr ""
+
+#: basic_mapping.xml:845(para)
+msgid "The UUID contains: IP address, startup time of the JVM (accurate to a quarter second), system time and a counter value (unique within the JVM). It's not possible to obtain a MAC address or memory address from Java code, so this is the best we can do without using JNI."
+msgstr ""
+
+#: basic_mapping.xml:854(title)
+msgid "Identity columns and sequences"
+msgstr ""
+
+#: basic_mapping.xml:855(para)
+msgid "For databases which support identity columns (DB2, MySQL, Sybase, MS SQL), you may use <literal>identity</literal> key generation. For databases that support sequences (DB2, Oracle, PostgreSQL, Interbase, McKoi, SAP DB) you may use <literal>sequence</literal> style key generation. Both these strategies require two SQL queries to insert a new object."
+msgstr ""
+
+#: basic_mapping.xml:873(para)
+msgid "For cross-platform development, the <literal>native</literal> strategy will choose from the <literal>identity</literal>, <literal>sequence</literal> and <literal>hilo</literal> strategies, dependant upon the capabilities of the underlying database."
+msgstr ""
+
+#: basic_mapping.xml:882(title)
+msgid "Assigned identifiers"
+msgstr ""
+
+#: basic_mapping.xml:883(para)
+msgid "If you want the application to assign identifiers (as opposed to having Hibernate generate them), you may use the <literal>assigned</literal> generator. This special generator will use the identifier value already assigned to the object's identifier property. This generator is used when the primary key is a natural key instead of a surrogate key. This is the default behavior if you do no specify a <literal><generator></literal> element."
+msgstr ""
+
+#: basic_mapping.xml:892(para)
+msgid "Choosing the <literal>assigned</literal> generator makes Hibernate use <literal>unsaved-value=\"undefined\"</literal>, forcing 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 ""
+
+#: basic_mapping.xml:902(title)
+msgid "Primary keys assigned by triggers"
+msgstr ""
+
+#: basic_mapping.xml:903(para)
+msgid "For legacy schemas only (Hibernate does not generate DDL with triggers)."
+msgstr ""
+
+#: basic_mapping.xml:913(para)
+msgid "In the above example, there is a unique valued property named <literal>socialSecurityNumber</literal> 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 ""
+
+#: basic_mapping.xml:925(title)
+msgid "Enhanced identifier generators"
+msgstr ""
+
+#: basic_mapping.xml:927(para)
+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 (not having 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 ""
+
+#: basic_mapping.xml:949(para)
+msgid "<literal>sequence_name</literal> (optional, defaults to <literal>hibernate_sequence</literal>): The name of the sequence (or table) to be used."
+msgstr ""
+
+#: basic_mapping.xml:955(para)
+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 typical named \"STARTS WITH\"."
+msgstr ""
+
+#: basic_mapping.xml:962(para)
+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 typical named \"INCREMENT BY\"."
+msgstr ""
+
+#: basic_mapping.xml:969(para)
+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 ""
+
+#: basic_mapping.xml:976(para)
+msgid "<literal>value_column</literal> (optional, defaults to <literal>next_val</literal>): Only relevant for table structures! The name of the column on the table which is used to hold the value."
+msgstr ""
+
+#: basic_mapping.xml:983(para)
+msgid "<literal>optimizer</literal> (optional, defaults to <literal>none</literal>): See <xref linkend=\"mapping-declaration-id-enhanced-optimizers\"/>"
+msgstr ""
+
+#: basic_mapping.xml:935(para)
+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> (because <literal>native</literal> (generally) chooses between <literal>identity</literal> and <literal>sequence</literal> which have largely different semantics which can cause subtle isssues in applications eyeing portability). <literal>org.hibernate.id.enhanced.SequenceStyleGenerator</literal> however achieves portability in a different manner. It chooses between using 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 emmulate with its!
table-based generators). This generator has a number of configuration parameters: <placeholder-1/>"
+msgstr ""
+
+#: basic_mapping.xml:1000(para)
+msgid "<literal>table_name</literal> (optional, defaults to <literal>hibernate_sequences</literal>): The name of the table to be used."
+msgstr ""
+
+#: basic_mapping.xml:1006(para)
+msgid "<literal>value_column_name</literal> (optional, defaults to <literal>next_val</literal>): The name of the column on the table which is used to hold the value."
+msgstr ""
+
+#: basic_mapping.xml:1012(para)
+msgid "<literal>segment_column_name</literal> (optional, defaults to <literal>sequence_name</literal>): The name of the column on the table which is used to hold the \"segement key\". This is the value which distinctly identifies which increment value to use."
+msgstr ""
+
+#: basic_mapping.xml:1019(para)
+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 ""
+
+#: basic_mapping.xml:1026(para)
+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 ""
+
+#: basic_mapping.xml:1032(para)
+msgid "<literal>initial_value</literal> (optional, defaults to <literal>1</literal>): The initial value to be retrieved from the table."
+msgstr ""
+
+#: basic_mapping.xml:1038(para)
+msgid "<literal>increment_size</literal> (optional, defaults to <literal>1</literal>): The value by which subsequent calls to the table should differ."
+msgstr ""
+
+#: basic_mapping.xml:1044(para)
+msgid "<literal>optimizer</literal> (optional, defaults to <literal/>): See <xref linkend=\"mapping-declaration-id-enhanced-optimizers\"/>"
+msgstr ""
+
+#: basic_mapping.xml:990(para)
+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 (although 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> utilizing the notion of pluggable optimiziers. 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: <placeholder-1/>"
+msgstr ""
+
+#: basic_mapping.xml:1054(title)
+msgid "Identifier generator optimization"
+msgstr ""
+
+#: basic_mapping.xml:1063(para)
+msgid "<literal>none</literal> (generally this is the default if no optimizer was specified): This says to not perform any optimizations, and hit the database each and every request."
+msgstr ""
+
+#: basic_mapping.xml:1069(para)
+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 ""
+
+#: basic_mapping.xml:1078(para)
+msgid "<literal>pooled</literal>: like was discussed for <literal>hilo</literal>, this optimizers 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. <literal>increment_size</literal> here refers to the values coming from the database."
+msgstr ""
+
+#: basic_mapping.xml:1055(para)
+msgid "For identifier generators which 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'd ideally want to 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 notion. <placeholder-1/>"
+msgstr ""
+
+#: basic_mapping.xml:1091(title)
+msgid "composite-id"
+msgstr ""
+
+#: basic_mapping.xml:1105(para)
+msgid "For a table with a composite key, you may map 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 ""
+
+#: basic_mapping.xml:1117(para)
+msgid "Your persistent class <emphasis>must</emphasis> override <literal>equals()</literal> and <literal>hashCode()</literal> to implement composite identifier equality. It must also implements <literal>Serializable</literal>."
+msgstr ""
+
+#: basic_mapping.xml:1123(para)
+msgid "Unfortunately, this approach to composite identifiers 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 ""
+
+#: basic_mapping.xml:1132(para)
+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 ""
+
+#: basic_mapping.xml:1143(para)
+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 disadvantage of this approach is quite obvious—code duplication."
+msgstr ""
+
+#: basic_mapping.xml:1152(para)
+msgid "The following attributes are used to specify a mapped composite identifier:"
+msgstr ""
+
+#: basic_mapping.xml:1158(para)
+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 ""
+
+#: basic_mapping.xml:1166(para)
+msgid "<literal>class</literal> (optional, but required for a mapped composite identifier): The class used as a composite identifier."
+msgstr ""
+
+#: basic_mapping.xml:1173(para)
+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 ""
+
+#: basic_mapping.xml:1181(para)
+msgid "<literal>name</literal> (optional, required for this approach): A property of component type that holds the composite identifier (see chapter 9)."
+msgstr ""
+
+#: basic_mapping.xml:1193(para)
+msgid "<literal>class</literal> (optional - defaults to the property type determined by reflection): The component class used as a composite identifier (see next section)."
+msgstr ""
+
+#: basic_mapping.xml:1200(para)
+msgid "This third approach, an <emphasis>identifier component</emphasis> is the one we recommend for almost all applications."
+msgstr ""
+
+#: basic_mapping.xml:1208(title)
+msgid "discriminator"
+msgstr ""
+
+#: basic_mapping.xml:1210(para)
+msgid "The <literal><discriminator></literal> element is required for polymorphic persistence using the table-per-class-hierarchy mapping strategy and 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 may 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 ""
+
+#: basic_mapping.xml:1237(para)
+msgid "<literal>column</literal> (optional - defaults to <literal>class</literal>) the name of the discriminator column."
+msgstr ""
+
+#: basic_mapping.xml:1243(para)
+msgid "<literal>type</literal> (optional - defaults to <literal>string</literal>) a name that indicates the Hibernate type"
+msgstr ""
+
+#: basic_mapping.xml:1249(para)
+msgid "<literal>force</literal> (optional - defaults to <literal>false</literal>) \"force\" Hibernate to specify allowed discriminator values even when retrieving all instances of the root class."
+msgstr ""
+
+#: basic_mapping.xml:1256(para)
+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. (Tells Hibernate to not include the column in SQL <literal>INSERT</literal>s.)"
+msgstr ""
+
+#: basic_mapping.xml:1264(para)
+msgid "<literal>formula</literal> (optional) an arbitrary SQL expression that is executed when a type has to be evaluated. Allows content-based discrimination."
+msgstr ""
+
+#: basic_mapping.xml:1272(para)
+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 ""
+
+#: basic_mapping.xml:1278(para)
+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 ""
+
+#: basic_mapping.xml:1284(para)
+msgid "Using the <literal>formula</literal> attribute you can declare an arbitrary SQL expression that will be used to evaluate the type of a row:"
+msgstr ""
+
+#: basic_mapping.xml:1296(title)
+msgid "version (optional)"
+msgstr ""
+
+#: basic_mapping.xml:1298(para)
+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)."
+msgstr ""
+
+#: basic_mapping.xml:1326(para)
+msgid "<literal>column</literal> (optional - defaults to the property name): The name of the column holding the version number."
+msgstr ""
+
+#: basic_mapping.xml:1332(para)
+msgid "<literal>name</literal>: The name of a property of the persistent class."
+msgstr ""
+
+#: basic_mapping.xml:1337(para)
+msgid "<literal>type</literal> (optional - defaults to <literal>integer</literal>): The type of the version number."
+msgstr ""
+
+#: basic_mapping.xml:1349(para)
+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 ""
+
+#: basic_mapping.xml:1358(para)
+msgid "<literal>generated</literal> (optional - defaults to <literal>never</literal>): Specifies that this version property value is actually generated by the database. See the discussion of <xref linkend=\"mapping-generated\">generated properties</xref>."
+msgstr ""
+
+#: basic_mapping.xml:1365(para)
+msgid "<literal>insert</literal> (optional - defaults to <literal>true</literal>): Specifies whether the version column should be included in SQL insert statements. May be set to <literal>false</literal> if and only if the database column is defined with a default value of <literal>0</literal>."
+msgstr ""
+
+#: basic_mapping.xml:1375(para)
+msgid "Version numbers may be of Hibernate type <literal>long</literal>, <literal>integer</literal>, <literal>short</literal>, <literal>timestamp</literal> or <literal>calendar</literal>."
+msgstr ""
+
+#: basic_mapping.xml:1380(para)
+msgid "A version or timestamp property should never be null for a detached instance, so Hibernate will detect any instance with a null version or timestamp as transient, no matter what other <literal>unsaved-value</literal> strategies are specified. <emphasis>Declaring a nullable version or timestamp property is an easy way to avoid any problems with transitive reattachment in Hibernate, especially useful for people using assigned identifiers or composite keys!</emphasis>"
+msgstr ""
+
+#: basic_mapping.xml:1391(title)
+msgid "timestamp (optional)"
+msgstr ""
+
+#: basic_mapping.xml:1393(para)
+msgid "The optional <literal><timestamp></literal> element indicates that the table contains timestamped data. This is intended as an alternative to versioning. Timestamps are by nature a less safe implementation of optimistic locking. However, sometimes the application might use the timestamps in other ways."
+msgstr ""
+
+#: basic_mapping.xml:1420(para)
+msgid "<literal>column</literal> (optional - defaults to the property name): The name of a column holding the timestamp."
+msgstr ""
+
+#: basic_mapping.xml:1426(para)
+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 ""
+
+#: basic_mapping.xml:1439(para)
+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 ""
+
+#: basic_mapping.xml:1448(para)
+msgid "<literal>source</literal> (optional - defaults to <literal>vm</literal>): From where should Hibernate retrieve the timestamp value? 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\", but will be safer for use in clustered environments. Note also, that not all <literal>Dialect</literal>s are known to support retrieving of the database's current timestamp, while others might be unsafe for usage in locking due to lack of precision (Oracle 8 for example)."
+msgstr ""
+
+#: basic_mapping.xml:1460(para)
+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 <xref linkend=\"mapping-generated\">generated properties</xref>."
+msgstr ""
+
+#: basic_mapping.xml:1469(para)
+msgid "Note that <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 ""
+
+#: basic_mapping.xml:1479(title)
+msgid "property"
+msgstr ""
+
+#: basic_mapping.xml:1481(para)
+msgid "The <literal><property></literal> element declares a persistent, JavaBean style property of the class."
+msgstr ""
+
+#: basic_mapping.xml:1525(para)
+msgid "<literal>name</literal>: the name of the property, with an initial lowercase letter."
+msgstr ""
+
+#: basic_mapping.xml:1531(para)
+msgid "<literal>column</literal> (optional - defaults to the property name): the name of the mapped database table column. This may also be specified by nested <literal><column></literal> element(s)."
+msgstr ""
+
+#: basic_mapping.xml:1538(para)
+msgid "<literal>type</literal> (optional): a name that indicates the Hibernate type."
+msgstr ""
+
+#: basic_mapping.xml:1543(para)
+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 colum(s) or by a trigger or other application."
+msgstr ""
+
+#: basic_mapping.xml:1552(para)
+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 ""
+
+#: basic_mapping.xml:1565(para)
+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 (requires build-time bytecode instrumentation)."
+msgstr ""
+
+#: basic_mapping.xml:1572(para)
+msgid "<literal>unique</literal> (optional): Enable the DDL generation of a unique constraint for the columns. Also, allow this to be the target of a <literal>property-ref</literal>."
+msgstr ""
+
+#: basic_mapping.xml:1579(para)
+msgid "<literal>not-null</literal> (optional): Enable the DDL generation of a nullability constraint for the columns."
+msgstr ""
+
+#: basic_mapping.xml:1585(para)
+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, determines if a version increment should occur when this property is dirty."
+msgstr ""
+
+#: basic_mapping.xml:1593(para)
+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 <xref linkend=\"mapping-generated\">generated properties</xref>."
+msgstr ""
+
+#: basic_mapping.xml:1602(para)
+msgid "<emphasis>typename</emphasis> could be:"
+msgstr ""
+
+#: basic_mapping.xml:1608(para)
+msgid "The name of a Hibernate basic type (eg. <literal>integer, string, character, date, timestamp, float, binary, serializable, object, blob</literal>)."
+msgstr ""
+
+#: basic_mapping.xml:1614(para)
+msgid "The name of a Java class with a default basic type (eg. <literal>int, float, char, java.lang.String, java.util.Date, java.lang.Integer, java.sql.Clob</literal>)."
+msgstr ""
+
+#: basic_mapping.xml:1620(para)
+msgid "The name of a serializable Java class."
+msgstr ""
+
+#: basic_mapping.xml:1625(para)
+msgid "The class name of a custom type (eg. <literal>com.illflow.type.MyCustomType</literal>)."
+msgstr ""
+
+#: basic_mapping.xml:1631(para)
+msgid "If you do not specify a type, Hibernate will use reflection upon the named property to take a guess at the correct Hibernate type. Hibernate will try to interpret the name of the return class of the property getter using rules 2, 3, 4 in that order. However, this is not always enough. In certain cases you will still 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 ""
+
+#: basic_mapping.xml:1641(para)
+msgid "The <literal>access</literal> attribute lets you control how Hibernate will access 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 may specify your own strategy for property access by naming a class that implements the interface <literal>org.hibernate.property.PropertyAccessor</literal>."
+msgstr ""
+
+#: basic_mapping.xml:1650(para)
+msgid "An especially powerful feature are derived properties. These properties are by definition read-only, the property value is computed at load time. You declare the computation as a SQL expression, this translates to a <literal>SELECT</literal> clause subquery in the SQL query that loads an instance:"
+msgstr ""
+
+#: basic_mapping.xml:1664(para)
+msgid "Note that you can reference the entities own table by not declaring an alias on a particular column (<literal>customerId</literal> in the given example). Also note that you can use the nested <literal><formula></literal> mapping element if you don't like to use the attribute."
+msgstr ""
+
+#: basic_mapping.xml:1674(title)
+msgid "many-to-one"
+msgstr ""
+
+#: basic_mapping.xml:1676(para)
+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 ""
+
+#: basic_mapping.xml:1729(para) basic_mapping.xml:1924(para) basic_mapping.xml:2139(para)
+msgid "<literal>name</literal>: The name of the property."
+msgstr ""
+
+#: basic_mapping.xml:1734(para) basic_mapping.xml:2703(para)
+msgid "<literal>column</literal> (optional): The name of the foreign key column. This may also be specified by nested <literal><column></literal> element(s)."
+msgstr ""
+
+#: basic_mapping.xml:1741(para) basic_mapping.xml:1929(para)
+msgid "<literal>class</literal> (optional - defaults to the property type determined by reflection): The name of the associated class."
+msgstr ""
+
+#: basic_mapping.xml:1747(para)
+msgid "<literal>cascade</literal> (optional): Specifies which operations should be cascaded from the parent object to the associated object."
+msgstr ""
+
+#: basic_mapping.xml:1753(para) basic_mapping.xml:1950(para)
+msgid "<literal>fetch</literal> (optional - defaults to <literal>select</literal>): Chooses between outer-join fetching or sequential select fetching."
+msgstr ""
+
+#: basic_mapping.xml:1759(para)
+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 some other property that maps to the same colum(s) or by a trigger or other application."
+msgstr ""
+
+#: basic_mapping.xml:1768(para)
+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 ""
+
+#: basic_mapping.xml:1781(para)
+msgid "<literal>unique</literal> (optional): Enable the DDL generation of a unique constraint for the foreign-key column. Also, allow this to be the target of a <literal>property-ref</literal>. This makes the association multiplicity effectively one to one."
+msgstr ""
+
+#: basic_mapping.xml:1789(para)
+msgid "<literal>not-null</literal> (optional): Enable the DDL generation of a nullability constraint for the foreign key columns."
+msgstr ""
+
+#: basic_mapping.xml:1795(para)
+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, dertermines if a version increment should occur when this property is dirty."
+msgstr ""
+
+#: basic_mapping.xml:1803(para)
+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 (requires build-time bytecode instrumentation). <literal>lazy=\"false\"</literal> specifies that the association will always be eagerly fetched."
+msgstr ""
+
+#: basic_mapping.xml:1813(para)
+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 ""
+
+#: basic_mapping.xml:1820(para) basic_mapping.xml:1988(para)
+msgid "<literal>entity-name</literal> (optional): The entity name of the associated class."
+msgstr ""
+
+#: basic_mapping.xml:1826(para)
+msgid "<literal>formula</literal> (optional): an SQL expression that defines the value for a <emphasis>computed</emphasis> foreign key."
+msgstr ""
+
+#: basic_mapping.xml:1833(para)
+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 the names of Hibernate's basic operations, <literal>persist, merge, delete, save-update, evict, replicate, lock, refresh</literal>, as well as the special values <literal>delete-orphan</literal> and <literal>all</literal> and comma-separated combinations of operation names, for example, <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 associations (many-to-one and one-to-one associations) do not support orphan delete."
+msgstr ""
+
+#: basic_mapping.xml:1846(para)
+msgid "A typical <literal>many-to-one</literal> declaration looks as simple as this:"
+msgstr ""
+
+#: basic_mapping.xml:1852(para)
+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 an ugly relational model. For example, suppose 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 ""
+
+#: basic_mapping.xml:1863(para)
+msgid "Then the mapping for <literal>OrderItem</literal> might use:"
+msgstr ""
+
+#: basic_mapping.xml:1869(para)
+msgid "This is certainly not encouraged, however."
+msgstr ""
+
+#: basic_mapping.xml:1873(para)
+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 ""
+
+#: basic_mapping.xml:1878(para)
+msgid "If the referenced unique key is the property of a component, you may specify a property path:"
+msgstr ""
+
+#: basic_mapping.xml:1887(title)
+msgid "one-to-one"
+msgstr ""
+
+#: basic_mapping.xml:1889(para)
+msgid "A one-to-one association to another persistent class is declared using a <literal>one-to-one</literal> element."
+msgstr ""
+
+#: basic_mapping.xml:1935(para)
+msgid "<literal>cascade</literal> (optional) specifies which operations should be cascaded from the parent object to the associated object."
+msgstr ""
+
+#: basic_mapping.xml:1941(para)
+msgid "<literal>constrained</literal> (optional) specifies that a foreign key constraint on the primary key of the mapped table 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 may be proxied (it is also used by the schema export tool)."
+msgstr ""
+
+#: basic_mapping.xml:1956(para)
+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 ""
+
+#: basic_mapping.xml:1969(para)
+msgid "<literal>formula</literal> (optional): Almost all one to one associations map to the primary key of the owning entity. In the rare case that this is not the case, you may specify a some other column, columns or expression to join on using an SQL formula. (See <literal>org.hibernate.test.onetooneformula</literal> for an example.)"
+msgstr ""
+
+#: basic_mapping.xml:1977(para)
+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 (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 eager fetch the association!</emphasis>"
+msgstr ""
+
+#: basic_mapping.xml:1995(para)
+msgid "There are two varieties of one-to-one association:"
+msgstr ""
+
+#: basic_mapping.xml:1999(para)
+msgid "primary key associations"
+msgstr ""
+
+#: basic_mapping.xml:2002(para)
+msgid "unique foreign key associations"
+msgstr ""
+
+#: basic_mapping.xml:2007(para)
+msgid "Primary key associations don't need an extra table column; if two rows are related by the association then the two table rows share the same primary key value. So if you want two objects to be related by a primary key association, you must make sure that they are assigned the same identifier value!"
+msgstr ""
+
+#: basic_mapping.xml:2014(para)
+msgid "For a primary key association, add the following mappings to <literal>Employee</literal> and <literal>Person</literal>, respectively."
+msgstr ""
+
+#: basic_mapping.xml:2022(para)
+msgid "Now we must ensure that the primary keys of related rows in the PERSON and EMPLOYEE tables are equal. We use a special Hibernate identifier generation strategy called <literal>foreign</literal>:"
+msgstr ""
+
+#: basic_mapping.xml:2040(para)
+msgid "A newly saved instance of <literal>Person</literal> is then assigned the same primary key value as the <literal>Employee</literal> instance refered with the <literal>employee</literal> property of that <literal>Person</literal>."
+msgstr ""
+
+#: basic_mapping.xml:2046(para)
+msgid "Alternatively, a foreign key with a unique constraint, from <literal>Employee</literal> to <literal>Person</literal>, may be expressed as:"
+msgstr ""
+
+#: basic_mapping.xml:2053(para)
+msgid "And this association may be made bidirectional by adding the following to the <literal>Person</literal> mapping:"
+msgstr ""
+
+#: basic_mapping.xml:2063(title)
+msgid "natural-id"
+msgstr ""
+
+#: basic_mapping.xml:2071(para)
+msgid "Even though we recommend the use of surrogate keys as primary keys, you should still try to identify natural keys for all entities. A natural key is a property or combination of properties that is unique and non-null. If it is also immutable, even better. 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 your mapping will be more self-documenting."
+msgstr ""
+
+#: basic_mapping.xml:2080(para)
+msgid "We strongly recommend that you implement <literal>equals()</literal> and <literal>hashCode()</literal> to compare the natural key properties of the entity."
+msgstr ""
+
+#: basic_mapping.xml:2085(para)
+msgid "This mapping is not intended for use with entities with natural primary keys."
+msgstr ""
+
+#: basic_mapping.xml:2091(para)
+msgid "<literal>mutable</literal> (optional, defaults to <literal>false</literal>): By default, natural identifier properties as assumed to be immutable (constant)."
+msgstr ""
+
+#: basic_mapping.xml:2101(title)
+msgid "component, dynamic-component"
+msgstr ""
+
+#: basic_mapping.xml:2103(para)
+msgid "The <literal><component></literal> element maps properties of a child object to columns of the table of a parent class. Components may, in turn, declare their own properties, components or collections. See \"Components\" below."
+msgstr ""
+
+#: basic_mapping.xml:2144(para)
+msgid "<literal>class</literal> (optional - defaults to the property type determined by reflection): The name of the component (child) class."
+msgstr ""
+
+#: basic_mapping.xml:2150(para) basic_mapping.xml:2250(para)
+msgid "<literal>insert</literal>: Do the mapped columns appear in SQL <literal>INSERT</literal>s?"
+msgstr ""
+
+#: basic_mapping.xml:2156(para) basic_mapping.xml:2256(para)
+msgid "<literal>update</literal>: Do the mapped columns appear in SQL <literal>UPDATE</literal>s?"
+msgstr ""
+
+#: basic_mapping.xml:2168(para)
+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 (requires build-time bytecode instrumentation)."
+msgstr ""
+
+#: basic_mapping.xml:2175(para)
+msgid "<literal>optimistic-lock</literal> (optional - defaults to <literal>true</literal>): Specifies that updates to this component do or do not require acquisition of the optimistic lock. In other words, determines if a version increment should occur when this property is dirty."
+msgstr ""
+
+#: basic_mapping.xml:2183(para) basic_mapping.xml:2270(para)
+msgid "<literal>unique</literal> (optional - defaults to <literal>false</literal>): Specifies that a unique constraint exists upon all mapped columns of the component."
+msgstr ""
+
+#: basic_mapping.xml:2192(para)
+msgid "The child <literal><property></literal> tags map properties of the child class to table columns."
+msgstr ""
+
+#: basic_mapping.xml:2197(para)
+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 ""
+
+#: basic_mapping.xml:2203(para)
+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\"/>."
+msgstr ""
+
+#: basic_mapping.xml:2212(title)
+msgid "properties"
+msgstr ""
+
+#: basic_mapping.xml:2214(para)
+msgid "The <literal><properties></literal> element allows the definition of a named, logical grouping of 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."
+msgstr ""
+
+#: basic_mapping.xml:2244(para)
+msgid "<literal>name</literal>: The logical name of the grouping - <emphasis>not</emphasis> an actual property name."
+msgstr ""
+
+#: basic_mapping.xml:2262(para)
+msgid "<literal>optimistic-lock</literal> (optional - defaults to <literal>true</literal>): Specifies that updates to these properties do or do not require acquisition of the optimistic lock. In other words, determines if a version increment should occur when these properties are dirty."
+msgstr ""
+
+#: basic_mapping.xml:2279(para)
+msgid "For example, if we have the following <literal><properties></literal> mapping:"
+msgstr ""
+
+#: basic_mapping.xml:2294(para)
+msgid "Then we might have some legacy data association which refers to this unique key of the <literal>Person</literal> table, instead of to the primary key:"
+msgstr ""
+
+#: basic_mapping.xml:2306(para)
+msgid "We don't recommend the use of this kind of thing outside the context of mapping legacy data."
+msgstr ""
+
+#: basic_mapping.xml:2314(title)
+msgid "subclass"
+msgstr ""
+
+#: basic_mapping.xml:2316(para)
+msgid "Finally, 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."
+msgstr ""
+
+#: basic_mapping.xml:2345(para) basic_mapping.xml:2422(para) basic_mapping.xml:2533(para)
+msgid "<literal>name</literal>: The fully qualified class name of the subclass."
+msgstr ""
+
+#: basic_mapping.xml:2350(para)
+msgid "<literal>discriminator-value</literal> (optional - defaults to the class name): A value that distiguishes individual subclasses."
+msgstr ""
+
+#: basic_mapping.xml:2356(para) basic_mapping.xml:2432(para) basic_mapping.xml:2543(para)
+msgid "<literal>proxy</literal> (optional): Specifies a class or interface to use for lazy initializing proxies."
+msgstr ""
+
+#: basic_mapping.xml:2362(para) basic_mapping.xml:2438(para) basic_mapping.xml:2549(para)
+msgid "<literal>lazy</literal> (optional, defaults to <literal>true</literal>): Setting <literal>lazy=\"false\"</literal> disables the use of lazy fetching."
+msgstr ""
+
+#: basic_mapping.xml:2370(para)
+msgid "Each subclass should declare 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 heirarchy must define a unique <literal>discriminator-value</literal>. If none is specified, the fully qualified Java class name is used."
+msgstr ""
+
+#: basic_mapping.xml:2378(para) basic_mapping.xml:2485(para) basic_mapping.xml:2561(para)
+msgid "For information about inheritance mappings, see <xref linkend=\"inheritance\"/>."
+msgstr ""
+
+#: basic_mapping.xml:2385(title)
+msgid "joined-subclass"
+msgstr ""
+
+#: basic_mapping.xml:2387(para)
+msgid "Alternatively, each subclass may be mapped to its own table (table-per-subclass mapping strategy). Inherited state is retrieved by joining with the table of the superclass. We use the <literal><joined-subclass></literal> element."
+msgstr ""
+
+#: basic_mapping.xml:2427(para) basic_mapping.xml:2538(para)
+msgid "<literal>table</literal>: The name of the subclass table."
+msgstr ""
+
+#: basic_mapping.xml:2446(para)
+msgid "No discriminator column is 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 be re-written as:"
+msgstr ""
+
+#: basic_mapping.xml:2492(title)
+msgid "union-subclass"
+msgstr ""
+
+#: basic_mapping.xml:2494(para)
+msgid "A third option is to map only the concrete classes of an inheritance hierarchy to tables, (the table-per-concrete-class strategy) where each table defines all persistent state of the class, including inherited state. In Hibernate, it is not absolutely necessary to explicitly map such inheritance hierarchies. You can simply 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."
+msgstr ""
+
+#: basic_mapping.xml:2557(para)
+msgid "No discriminator column or key column is required for this mapping strategy."
+msgstr ""
+
+#: basic_mapping.xml:2568(title)
+msgid "join