📄 performance.po
字号:
#: index.docbook:614, index.docbook:621, index.docbook:628, index.docbook:784,#: index.docbook:785, index.docbook:786, index.docbook:791, index.docbook:792,#: index.docbook:793, index.docbook:798, index.docbook:799, index.docbook:800,#: index.docbook:805, index.docbook:806, index.docbook:812, index.docbook:815msgid "<entry>yes</entry>"msgstr "<entry>si</entry>"#: index.docbook:617, index.docbook:790msgid "EHCache"msgstr "EHCache"#: index.docbook:618msgid "org.hibernate.cache.EhCacheProvider"msgstr "org.hibernate.cache.EhCacheProvider"#: index.docbook:619, index.docbook:626msgid "memory, disk"msgstr "memoria, disco"#: index.docbook:624, index.docbook:797msgid "OSCache"msgstr "OSCache"#: index.docbook:625msgid "org.hibernate.cache.OSCacheProvider"msgstr "org.hibernate.cache.OSCacheProvider"#: index.docbook:631, index.docbook:804msgid "SwarmCache"msgstr "SwarmCache"#: index.docbook:632msgid "org.hibernate.cache.SwarmCacheProvider"msgstr "org.hibernate.cache.SwarmCacheProvider"#: index.docbook:633msgid "clustered (ip multicast)"msgstr "clusterizado (ip multicast)"#: index.docbook:634msgid "yes (clustered invalidation)"msgstr "sí (invalidación en cluster)"#: index.docbook:638, index.docbook:811msgid "JBoss TreeCache"msgstr "TreeCache de JBoss"#: index.docbook:639msgid "org.hibernate.cache.TreeCacheProvider"msgstr "org.hibernate.cache.TreeCacheProvider"#: index.docbook:640msgid "clustered (ip multicast), transactional"msgstr "clusterizado (ip multicast), transaccional"#: index.docbook:641msgid "yes (replication)"msgstr "sí (replicación)"#: index.docbook:642msgid "yes (clock sync req.)"msgstr "sí (requiere sincronización de reloj)"#: index.docbook:649msgid "Cache mappings"msgstr "Mapeos de caché"#: index.docbook:651msgid """The <literal><cache></literal> element of a class or collection ""mapping has the following form:"msgstr """El elemento <literal><cache></literal> de una mapeo de clase o ""colección tiene la siguiente forma:"#: index.docbook:662msgid """<![CDATA[<cache \n"" usage=\"transactional|read-write|nonstrict-read-write|read-only\"\n"" region=\"RegionName\"\n"" include=\"all|non-lazy\"\n""/>]]>"msgstr """<![CDATA[<cache \n"" usage=\"transactional|read-write|nonstrict-read-write|read-only\"\n""/>]]>"#: index.docbook:665msgid """<literal>usage</literal> (required) specifies the caching strategy: ""<literal>transactional</literal>, <literal>read-write</literal>, ""<literal>nonstrict-read-write</literal> or <literal>read-only</literal>"msgstr """<literal>usage</literal> especifica la estrategia de caching: ""<literal>transactional</literal>, <literal>read-write</literal>, ""<literal>nonstrict-read-write</literal> o <literal>read-only</literal>"#: index.docbook:674msgid """<literal>region</literal> (optional, defaults to the class or collection ""role name) specifies the name of the second level cache region"msgstr """<literal>region</literal> (optional, defaults to the class or collection ""role name) specifies the name of the second level cache region"#: index.docbook:681msgid """<literal>include</literal> (optional, defaults to <literal>all</literal>) ""<literal>non-lazy</literal> specifies that properties of the entity mapped ""with <literal>lazy=\"true\"</literal> may not be cached when attribute-level ""lazy fetching is enabled"msgstr """<literal>include</literal> (optional, defaults to <literal>all</literal>) ""<literal>non-lazy</literal> specifies that properties of the entity mapped ""with <literal>lazy=\"true\"</literal> may not be cached when attribute-level ""lazy fetching is enabled"#: index.docbook:691msgid """Alternatively (preferrably?), you may specify <literal><class-cache></""literal> and <literal><collection-cache></literal> elements in ""<literal>hibernate.cfg.xml</literal>."msgstr """Alternativamente (¿preferiblemente?), puedes especificar los ""elementos <literal><class-cache></literal> y <literal><collection-""cache></literal> en <literal>hibernate.cfg.xml</literal>."#: index.docbook:696msgid """The <literal>usage</literal> attribute specifies a <emphasis>cache ""concurrency strategy</emphasis>."msgstr """El atributo <literal>usage</literal> especifica una <emphasis>estrategia de ""concurrencia al caché</emphasis>."#: index.docbook:703msgid "Strategy: read only"msgstr "Estrategia: sólo lectura (read only)"#: index.docbook:705msgid """If your application needs to read but never modify instances of a persistent ""class, a <literal>read-only</literal> cache may be used. This is the ""simplest and best performing strategy. It's even perfectly safe for use in a ""cluster."msgstr """Si tu aplicación necesita leer pero nunca modificar las instancias de ""una clase persistente, puede usarse un caché <literal>read-only</""literal>. Esta es la mejor y más simple estrategia. Es incluso ""perfectamente segura de usar en un cluster."#: index.docbook:711msgid """<![CDATA[<class name=\"eg.Immutable\" mutable=\"false\">\n"" <cache usage=\"read-only\"/>\n"" ....\n""</class>]]>"msgstr """<![CDATA[<class name=\"eg.Immutable\" mutable=\"false\">\n"" <cache usage=\"read-only\"/>\n"" ....\n""</class>]]>"#: index.docbook:717msgid "Strategy: read/write"msgstr "Estrategia: lectura/escritura (read/write)"#: index.docbook:719msgid """If the application needs to update data, a <literal>read-write</literal> ""cache might be appropriate. This cache strategy should never be used if ""serializable transaction isolation level is required. If the cache is used ""in a JTA environment, you must specify the property <literal>hibernate.""transaction.manager_lookup_class</literal>, naming a strategy for obtaining ""the JTA <literal>TransactionManager</literal>. In other environments, you ""should ensure that the transaction is completed when <literal>Session.close()""</literal> or <literal>Session.disconnect()</literal> is called. If you wish ""to use this strategy in a cluster, you should ensure that the underlying ""cache implementation supports locking. The built-in cache providers do ""<emphasis>not</emphasis>."msgstr """Si la aplicación necesita actualizar datos, un caché ""<literal>read-write</literal> podría ser apropiado. Esta estrategia ""de caché nunca debe ser usada si se requiere nivel de aislamiento ""serializable de transacciones. Si el caché es usado en un entorno ""JTA, debes especificar la propiedad <literal>hibernate.transaction.""manager_lookup_class</literal>, mencionando una estrategia para obtener el ""<literal>TransactionManager</literal> de JTA. En otros entornos, debes ""asegurarte que la transacción esté completada cuando se llame ""a <literal>Session.close()</literal> o <literal>Session.disconnect()</""literal>. Si deseas usar esta estrategia en un cluster, debes asegurarte que ""la implementación de caché subyacente soporta bloqueos. Los ""provedores de caché internos predeterminados <emphasis>no</emphasis> ""no lo soportan."#: index.docbook:730msgid """<![CDATA[<class name=\"eg.Cat\" .... >\n"" <cache usage=\"read-write\"/>\n"" ....\n"" <set name=\"kittens\" ... >\n"" <cache usage=\"read-write\"/>\n"" ....\n"" </set>\n""</class>]]>"msgstr """<![CDATA[<class name=\"eg.Cat\" .... >\n"" <cache usage=\"read-write\"/>\n"" ....\n"" <set name=\"kittens\" ... >\n"" <cache usage=\"read-write\"/>\n"" ....\n"" </set>\n""</class>]]>"#: index.docbook:735msgid "Strategy: nonstrict read/write"msgstr "Estrategia: lectura/escritura no estricta (nonstrict read/write)"#: index.docbook:737msgid """If the application only occasionally needs to update data (ie. if it is ""extremely unlikely that two transactions would try to update the same item ""simultaneously) and strict transaction isolation is not required, a ""<literal>nonstrict-read-write</literal> cache might be appropriate. If the ""cache is used in a JTA environment, you must specify <literal>hibernate.""transaction.manager_lookup_class</literal>. In other environments, you ""should ensure that the transaction is completed when <literal>Session.close()""</literal> or <literal>Session.disconnect()</literal> is called."msgstr """Si la aplicación necesita sólo ocasionalmente actualizar datos ""(es decir, es extremadamente inprobable que dos transacciones intenten ""actualizar el mismo ítem simultáneamente) y no se requiere de ""un aislamiento de transacciones estricto, un caché <literal>nonstrict-""read-write</literal> podría ser apropiado. Si se usa el caché ""en un entorno JTA, debes especificar <literal>hibernate.transaction.""manager_lookup_class</literal>. En otros entornos, debes asegurarte que la ""transacción se haya completado cuando se llame a <literal>Session.""close()</literal> o <literal>Session.disconnect()</literal>."#: index.docbook:749msgid "Strategy: transactional"msgstr "Estrategia: transaccional"#: index.docbook:751msgid """The <literal>transactional</literal> cache strategy provides support for ""fully transactional cache providers such as JBoss TreeCache. Such a cache ""may only be used in a JTA environment and you must specify ""<literal>hibernate.transaction.manager_lookup_class</literal>."msgstr """La estrategia de caché <literal>transactional</literal> brinda ""soporte a provedores de cachés completamente transaccionales como ""TreeCache de JBoss. Un caché así, puede sólo ser usado ""en un entorno JTA y debes especificar <literal>hibernate.transaction.""manager_lookup_class</literal>."#: index.docbook:759msgid """None of the cache providers support all of the cache concurrency strategies. ""The following table shows which providers are compatible with which ""concurrency strategies."msgstr """Ninguno de los provedores de caché soporta todas las estrategias de ""concurrencia al caché. La siguiente tabla muestra qué ""provedores son compatibles con qué estrategias de concurrencia."#: index.docbook:765msgid "Cache Concurrency Strategy Support"msgstr "Soporte a Estrategia de Concurrencia a Caché"#: index.docbook:775msgid "read-only"msgstr "read-only"#: index.docbook:776msgid "nonstrict-read-write"msgstr "nonstrict-read-write"#: index.docbook:777msgid "read-write"msgstr "read-write"#: index.docbook:778msgid "transactional"msgstr "transactional"#: index.docbook:824msgid "Managing the caches"msgstr "Gestionando los cachés"#: index.docbook:826msgid """Whenever you pass an object to <literal>save()</literal>, <literal>update()</""literal> or <literal>saveOrUpdate()</literal> and whenever you retrieve an ""object using <literal>load()</literal>, <literal>get()</literal>, ""<literal>list()</literal>, <literal>iterate()</literal> or <literal>scroll()""</literal>, that object is added to the internal cache of the ""<literal>Session</literal>."msgstr """Siempre que pases un objeto a <literal>save()</literal>, <literal>update()</""literal> o <literal>saveOrUpdate()</literal> y siempre qu
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -