Well only update and delete work the way I described wrt a temporary
table. inserts are handled completely differently.
On Tue, 2009-11-24 at 19:53 +0100, Adam Warski wrote:
> Hello,
>
> I don't exactly know how bulk operations work, and I didn't know that there's
> a temporary table with the
If you return a "lazy structure", we could avoid the overhead unless
the data is needed :)
On 24 nov. 09, at 20:52, Steve Ebersole wrote:
> I think it will just pass the table name. Too much overhead to
> materialize all the ids when the event may not even be used.
>
> On Tue, 2009-11-24 at 20
I think it will just pass the table name. Too much overhead to
materialize all the ids when the event may not even be used.
On Tue, 2009-11-24 at 20:21 +0100, Emmanuel Bernard wrote:
> Good idea,
> If we could have an event listener that indeed does provide the
> information lazily, we could de
Good idea,
If we could have an event listener that indeed does provide the
information lazily, we could definitely benefit from it. But that has
a cost so I think I would still keep it optional on the HSearch side.
On 24 nov. 09, at 19:53, Adam Warski wrote:
> Hello,
>
> I don't exactly know
Hello,
I don't exactly know how bulk operations work, and I didn't know that there's a
temporary table with the affected ids available.
But if so, then yes, such an event would solve the problem, in the way Steve
described. (And I got asked about bulk operations quite a lot of times, always
ans
How about a new event right at the moment after we have just collected
all the ids into the temp table?
For envers, this would allow you to save off the current state prior to
the update/delete.
For search, this would allow you to "circle back" after the operation
and re-index those matching id
This user use case is not compelling enough.
This query could be rewritten em.remove em.getReference(Product.class,
4) );
but generally speaking, what do you want to do? Fire a bunk event? I
think working around the issue is better handled when the actual bulk
query is executed as you have f
Message could not be delivered
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
