|
|
|
|
|
|
by hparadiz
6 hours ago
|
|
|
Feel like I've solved this non problem like 20 times. If your framework is holding your records in a collection and you keep track of phantoms that have been edited but not saved as they are edited then all this becomes a non issue. That way you do Collection->SaveTransaction or Collection->Save() and the collection does all the db commit, roll back nonsense. Anyway the examples I don't even know if I could call that an ORM. Use a better one. |
|
|