On Tue, Mar 26, 2019 at 10:17 AM Sanne Grinovero
wrote:
>
> Why should we not?
>
There is a very compelling reason for that. I'll have to leave it at that.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/li
On Tue, 26 Mar 2019 at 15:08, Steve Ebersole wrote:
>
> On Tue, Mar 26, 2019 at 9:57 AM Sanne Grinovero wrote:
>>
>> One question: could we benefit from "cascade delete" rules defined in
>> the table structure?
>>
>>
>> If Hibernate ORM was able parse the cascading rules from existing
>> schemas,
On Tue, Mar 26, 2019 at 9:57 AM Sanne Grinovero wrote:
> One question: could we benefit from "cascade delete" rules defined in
> the table structure?
> If Hibernate ORM was able parse the cascading rules from existing
> schemas, and possibly generate them for new schemas, you could have an
> en
Hi Steve,
this does sound amazing, I think it's certainly worth trying to have
the most efficient strategy chosen on a per-entity base.
One question: could we benefit from "cascade delete" rules defined in
the table structure?
If Hibernate ORM was able parse the cascading rules from existing
sch
https://hibernate.zulipchat.com/#narrow/stream/132094-hibernate-orm-dev/topic/6.2E0.20-.20multi-table.20mutation
On Tue, Mar 26, 2019 at 8:25 AM Steve Ebersole wrote:
> While working on 6 I discovered that we maybe do not do the best job in
> regards to "bulk update/delete" queries against multi
