許多ORM框架實現了這種基本思想。
The ORM restriction might require you to accept yet another trade-off — maintainability and technology selection for better performance with transaction support.
爲了應對可能的這種情況，如果在此事務策略中使用對象關係映*(ORM)框架，則應確保使用了版本驗*功能。
It is powerful ORM framework, but it is overkill for such simple task as a sessions management.
Now you'll see how the "ORM" in GORM has the flexibility to deal with table and column names in your legacy databases that don't follow standard GORM naming conventions.
Gone are the days of writing your own object-relational mapping (ORM), logging, or testing framework.
爲此產生了一整套稱爲ORM的程序，用來緩解在數據庫和麪向對象的代碼之間來回轉移數據的痛苦。
To deal with this possibility, make sure you use versioning if you are using an object-relational mapping (ORM) framework with this transaction strategy.
手動編寫對象關係映*(ORM)、日誌或測試框架的時代已經一去不復返。
現在您將看到GORM的“ORM”如何能夠靈活處理遺留數據庫中不符合Grails標準命名約定的表名與列名。
Many of the ORM frameworks have implementations of this basic idea.
You can use many ORM tools to avoid code repetition.
