I'm thinking about just dropping this (the agnostic part) as it is not
really getting any traction with or looks from the non-ORM folks.
On Mon 16 Dec 2013 07:55:36 AM CST, Emmanuel Bernard wrote:
> In the old (4.2) Persisters / Loaders, the ResultSet API was pretty pervasive
> and passed form me
In the old (4.2) Persisters / Loaders, the ResultSet API was pretty pervasive
and passed form methods to methods.
With the Operation approach, that cannot be the case anymore. But if
that can be done, that's better for OGM.
Also, that's a bit out of my league, but I wonder if that operation
design
The Operations are store specific. So there would be a specific
Operation for performing a JDBC query and either extracting the results
(normal use) or accessing the ResultSet (ScrollableResults use).
There would be some other Operation impl(s) for doing the same against
no-sql stores. Oper
When I reviewed your work earlier last week, I had the feeling that we
would need to replace JdbcSession with something totally different. OGM
Loader / Persisters would then use that different contract.
The idea of a generic DataStoreSession is attractive.
But something I am not clear on is how t
