ight
> span multiple physical transactions.
>
> On Wed, Oct 25, 2017 at 10:37 AM Jonathan Halliday
> mailto:jonathan.halli...@redhat.com>> wrote:
>
>
> right, a lot of JTA works on the 'tx bound to thread' approach and it's
> a right pain in async
right, a lot of JTA works on the 'tx bound to thread' approach and it's
a right pain in async I/O thread pooled environments like vert.x That's
one of the reasons why sticking a get/put api on the Transaction
instance abstraction instead may make more sense, though I'm guessing
your Synchroni
factor it all to stick to
> the standard APIs - however I wonder if it will still work for a JDBC
> transaction.
>
> Either way I'll take the fact that the standard API exposes such a
> functionality as a sign that this could be sensible to expose.
>
> Thanks,
> Sanne
The javax.transaction version of that interface already functions as a
per-transaction hashmap, with put/get operations available. If you can
use it directly, then just pick a suitable lookup key - FQCN or even the
sync impl .class itself, since the key is Object type. If not then at
least ret
So I'm tinkering with the cassandra OGM backend, looking particularly at
@ElementCollection since cassandra has native collection types, use of
which would sidestep the current limitations on List's bag semantics at
the same time as improving performance.
The ORM core we sit on assumes that su
yup, looks like the new columns added as part of OGM-717 don't work with
cassandra. Which kinda begs the question - how did the branch get into
that state? Is the CI skipping tests?
Jonathan.
On 15/05/15 16:58, Emmanuel Bernard wrote:
> Hey Jonathan,
>
> I investigated a bit the Cassandra fa
for method level POJO usage declarations.
>
> Right, I would not like that either. Also exclusions in the POM won't
> apply when e.g. running all tests of a module in your IDE. The mechanism
> should solely based on the OGM test runner.
>
>
>
> 2015-04-15 15:53 GMT+
ork.
>
> Can you name an example of a test affected by this?
Basket.java: @OneToMany List from ManyToOneTest
>
>
>
> 2015-04-15 13:41 GMT+02:00 Jonathan Halliday
> mailto:jonathan.halli...@redhat.com>>:
>
>
> In the course of developing the cassandra
In the course of developing the cassandra backend for OGM I've hit an
issue with some of the backendtck tests.
These tests are in core and reused by each backend. It's possible to
exclude tests at class or method level per backend, which prevents
irrelevant tests from running for a given backe
The first part of the cassandra backend work is ready for review. I've
backed out the incomplete association support, leaving the basic
framework for the backend module with enough functionality to support
entities that don't have relations. It's still larger than an average
PR, but the module
10 matches
Mail list logo
