HHH-3987 - prep 3.3.2 release
git-svn-id: https://svn.jboss.org/repos/hibernate/core/branches/Branch_3_3@16913 1b8cb986-b30d-0410-93ca-fae66ebed9b2
This commit is contained in:
parent
725b2e6f26
commit
f980ce8558
|
@ -32,6 +32,11 @@
|
|||
<extensions>true</extensions>
|
||||
|
||||
<dependencies>
|
||||
<dependency>
|
||||
<groupId>net.sf.docbook</groupId>
|
||||
<artifactId>docbook</artifactId>
|
||||
<version>1.72.0</version>
|
||||
</dependency>
|
||||
<dependency>
|
||||
<groupId>org.hibernate</groupId>
|
||||
<artifactId>hibernate-jdocbook-style</artifactId>
|
||||
|
|
|
@ -846,7 +846,7 @@ public class EventManager {
|
|||
Here, we are using a Hibernate Query Language (HQL) query to load all existing
|
||||
<literal>Event</literal> objects from the database. Hibernate will generate the
|
||||
appropriate SQL, send it to the database and populate <literal>Event</literal> objects
|
||||
with the data. You can create more complex queries with HQL. See <xref linkend="query-hql"/>
|
||||
with the data. You can create more complex queries with HQL. See <xref linkend="queryhql"/>
|
||||
for more information.
|
||||
</para>
|
||||
|
||||
|
|
|
@ -883,7 +883,7 @@ msgstr "Recuperación por unión externa (outer join)"
|
|||
#: inheritance_mapping.xml:314
|
||||
#, no-c-format
|
||||
msgid "table per class-hierarchy"
|
||||
msgstr "<entry>tabla por jerarquía de clases</entry>"
|
||||
msgstr "tabla por jerarquía de clases"
|
||||
|
||||
#. Tag: literal
|
||||
#: inheritance_mapping.xml:315 inheritance_mapping.xml:326
|
||||
|
|
|
@ -6,7 +6,7 @@ msgid ""
|
|||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
|
||||
"POT-Creation-Date: 2009-06-16 18:47+0000\n"
|
||||
"POT-Creation-Date: 2009-06-23 18:41+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
|
||||
|
@ -15,19 +15,19 @@ msgstr ""
|
|||
"Content-Transfer-Encoding: 8bit\n"
|
||||
|
||||
#. Tag: title
|
||||
#: Hibernate_Reference.xml:34
|
||||
#: Hibernate_Reference.xml:35
|
||||
#, no-c-format
|
||||
msgid "HIBERNATE - Relational Persistence for Idiomatic Java"
|
||||
msgstr ""
|
||||
|
||||
#. Tag: subtitle
|
||||
#: Hibernate_Reference.xml:35
|
||||
#: Hibernate_Reference.xml:36
|
||||
#, no-c-format
|
||||
msgid "Hibernate Reference Documentation"
|
||||
msgstr ""
|
||||
|
||||
#. Tag: holder
|
||||
#: Hibernate_Reference.xml:49
|
||||
#: Hibernate_Reference.xml:51
|
||||
#, no-c-format
|
||||
msgid "©rightHolder;"
|
||||
msgstr ""
|
||||
|
|
|
@ -6,7 +6,7 @@ msgid ""
|
|||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
|
||||
"POT-Creation-Date: 2009-06-16 18:47+0000\n"
|
||||
"POT-Creation-Date: 2009-06-23 18:41+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
|
||||
|
|
|
@ -6,7 +6,7 @@ msgid ""
|
|||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
|
||||
"POT-Creation-Date: 2009-06-16 18:47+0000\n"
|
||||
"POT-Creation-Date: 2009-06-23 18:41+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
|
||||
|
@ -71,7 +71,7 @@ msgstr ""
|
|||
#. Tag: para
|
||||
#: portability.xml:85
|
||||
#, no-c-format
|
||||
msgid "The cool part about these resolvers is that users can also register their own custom resolvers which will be processed ahead of the built-in Hibernate ones. This might be useful in a number of different situations: it allows easy integration for auto-detection of dialects beyond those shipped with HIbernate itself; it allows you to specify to use a custom dialect when a particular database is recognized; etc. To register one or more resolvers, simply specify them (seperated by commas, tabs or spaces) using the 'hibernate.dialect_resolvers' configuration setting (see the <constant>DIALECT_RESOLVERS</constant> constant on <classname>org.hibernate.cfgEnvironment</classname>)."
|
||||
msgid "The cool part about these resolvers is that users can also register their own custom resolvers which will be processed ahead of the built-in Hibernate ones. This might be useful in a number of different situations: it allows easy integration for auto-detection of dialects beyond those shipped with HIbernate itself; it allows you to specify to use a custom dialect when a particular database is recognized; etc. To register one or more resolvers, simply specify them (seperated by commas, tabs or spaces) using the 'hibernate.dialect_resolvers' configuration setting (see the <constant>DIALECT_RESOLVERS</constant> constant on <classname>org.hibernate.cfg.Environment</classname>)."
|
||||
msgstr ""
|
||||
|
||||
#. Tag: title
|
||||
|
|
|
@ -6,7 +6,7 @@ msgid ""
|
|||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
|
||||
"POT-Creation-Date: 2009-06-16 18:47+0000\n"
|
||||
"POT-Creation-Date: 2009-06-23 18:41+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
|
||||
|
|
|
@ -6,7 +6,7 @@ msgid ""
|
|||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
|
||||
"POT-Creation-Date: 2009-06-10 21:02+0000\n"
|
||||
"POT-Creation-Date: 2009-06-23 18:41+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
|
||||
|
@ -775,7 +775,7 @@ msgstr ""
|
|||
#. Tag: para
|
||||
#: tutorial.xml:609
|
||||
#, no-c-format
|
||||
msgid "Here, we are using a Hibernate Query Language (HQL) query to load all existing <literal>Event</literal> objects from the database. Hibernate will generate the appropriate SQL, send it to the database and populate <literal>Event</literal> objects with the data. You can create more complex queries with HQL. See <xref linkend=\"query-hql\"/> for more information."
|
||||
msgid "Here, we are using a Hibernate Query Language (HQL) query to load all existing <literal>Event</literal> objects from the database. Hibernate will generate the appropriate SQL, send it to the database and populate <literal>Event</literal> objects with the data. You can create more complex queries with HQL. See <xref linkend=\"queryhql\"/> for more information."
|
||||
msgstr ""
|
||||
|
||||
#. Tag: para
|
||||
|
|
Loading…
Reference in New Issue