We recommend to use a different persistence provider.
我们建议使用不同的持久性提供者。
This property masks the persistence provider from having to deal with vendor specific SQL differences.
这个属性使持久性提供者不必处理特定于供应商的SQL差异。
Contains options that specify what action the SQL persistence provider should take when it receives an exception when trying to lock an instance.
包含一些选项，这些选项指定，如果SQL持久性提供程序在尝试锁定实例时收到异常，它应采取什么操作。
Contains options that specify whether the persistence provider should keep or delete the state information for an instance in the persistence store after the instance completes.
包含一些选项，这些选项指定持久性提供程序在实例完成之后是应将实例的状态信息保留在持久性存储中，还是应将该信息删除。
Until the persistence providers implement it, you'll need to use a provider-specific exception, such as Hibernate's StaleObjectStateException, for detecting an optimistic concurrency problem.
在持久性提供者执行它以前，您还需要使用特定于提供者的异常，如hibernate的StaleObjectStateException，来检测乐观并发问题。
It's been estimated that 75-80% of the SpecJEnterprise benchmark depends on the persistence layer (that is, JPA provider).
据估计，75- 80%的SpecJEnterprise基准测试依赖持久化层(即jpa提供者)。
The persistence.xml file denotes a particular JPA provider for the persistence unit along with provider specific properties.
xml文件则表示一个特殊的JPA提供器，它针对具有提供器的特定属性的持久化单元。
For example, the membership feature USES a provider to coordinate the persistence of membership data in a database.
例如，成员资格功能使用提供者，以协调资料库中成员资格资料的持续性。
For example, the membership feature USES a provider to coordinate the persistence of membership data in a database.
例如，成员资格功能使用提供者，以协调资料库中成员资格资料的持续性。
应用推荐