|
| cc:
|
| Subject: RE: [Hibernate] Mass Deletes
|
>--|
I got in on this t
> |
> | cc:
>
Title: RE: [Hibernate] Mass Deletes
I don't understand the drawbacks with the select-then-delete alternative.
Doesn't it just mean one additional statement to the database?
///Odd Moller
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: den 4 au
I got in on this thread late, but if I understand what people are talking about, the
select-then-delete model doesn't work well on large datasets. This is one of the
drawbacks to
Entity Beans for our organization. Trying doing that model for 10K rows and you
quickly see how
much that extra statem
c: [EMAIL PROTECTED]
|
| Subject: Re:
EMAIL PROTECTED]
|
| Subject: Re: [Hibernate] Mass Deletes
|
>--|
[EMAIL PROTECTED] wr
[EMAIL PROTECTED] wrote:
Many users have asked for
session.delete("from Foo foo where foo.count=0");
to issue a single SQL DELETE. This is certainly not possible for objects
with collections or cascades (though it might not matter if we ignore
Lifecycle callback; not sure). For other clas
|
| cc:
|
|
| cc:
|
| Subject
