Efficiently storing entities (eg. orderline in Order) without ORM

[Maciej Hadam]

Hi,

What are the ways to efficiently store enitities without
ORM(Hibernate, JPA).
As is it written in WIKI, repository could be used with different
store than relational database. In that scenario we loose the "dirty
checking" Hibernate feature, and the entities have to be redundantly
overwritten

And second scenario.
What if we want to use iBatis or JDBC with relational database.

Maybe the Unit of Work pattern is the solution?
What are yours opinions?

Thanks for response.

[Sławomir Sobótka]

I'm wondering about ratio of unnecessary updates...

If in app layer we usually:

1. Aggregate = repo.load()
2. Aggreate.doSth()
3. repo.save(Aggreagate)

Than we can assume that Aggreagta actually changed itself (We don't
have so much luxury to know which column actually change - like
dynamic in Hibernate).
Problem is when dealing with large aggregates (smell) and we do not
know what has changed..../
...hmm why You don't want to use Hibernate in domain model, anyway?:P

[Maciej Hadam]

Hibernate has much more "magic" than iBatis which I currently use.
It's not an easy decision to switch to ORM because lack of "UnitOfWork mechanism".
So, as you suggested, maybe the best way is to refactor the domain model to minimize the time of large aggregates storing operation.

2012/2/2 Sławomir Sobótka <sso...@gmail.com>