> you sort of imply Slice does that while Shards does not.
I do not. If my words carry that implication, my sincere apologies. (I
will post this clarification in Serverside as well)
As I said, I am inspired by Hibernate Shards to work on Slice.
> for iii, it's more than Shards does not care at all and lets JTA do it's job
What happens when no JTA transaction manager in the environment? e.g.
in JPA parlance, a persistence unit with transaction-
> Other question, do you deal with group by, having and aggregation?
Not yet. Slice is at version 0.4.0. Unique result aggregation can be
accomplished with the current approach of merging results from
different sources, but sorting /group by / having all are in
conceptually difficult domain right now. How about Shards on this
On Jan 9, 5:54 pm, Emmanuel Bernard <o...@emmanuelbernard.com> wrote: