# The incident: cascade = ALL on a @ManyToOne to a shared parent
# Hibernate ORM 7.4.15.Final, H2, JDK 25

== Foreign keys on the project tables (ON DELETE rule as H2 reports it)
ProjectBad    : [FKC2MGHR59KQYACY2C4OQFD1XNP | NO ACTION]
ProjectBadDb  : [FKDTYHCRAYDD8XEEGIE4S62FQ3P | CASCADE]
ProjectGood   : [FKNLG47HDNK41TPFKBDSEGG8K9G | NO ACTION]

== 1. Testing: every project has its own user
-- remove(project 1); flush()
   sql> select pb1_0.id,pb1_0.owner_id,pb1_0.title from ProjectBad pb1_0 where pb1_0.id=?
   sql> delete from ProjectBad where id=?
   sql> delete from AppUser where id=?
raw rows: AppUser=0 ProjectBad=0  (the user is gone, nothing failed)

== 2. Production, plain schema: the user has two projects
-- remove(first project); flush()
   sql> select pb1_0.id,pb1_0.owner_id,pb1_0.title from ProjectBad pb1_0 where pb1_0.id=?
   sql> delete from ProjectBad where id=?
   sql> delete from AppUser where id=?
   threw: org.hibernate.exception.ConstraintViolationException <- org.h2.jdbc.JdbcSQLIntegrityConstraintViolationException
   cause: Referential integrity constraint violation: "FKC2MGHR59KQYACY2C4OQFD1XNP: PUBLIC.PROJECTBAD FOREIGN KEY(OWNER_ID) REFERENCES PUBLIC.APPUSER(ID) (CAST(2 AS BIGINT))"; SQL statement:
raw rows after rollback: AppUser=1 ProjectBad=2

== 3. Production, schema with ON DELETE CASCADE on the foreign key
before: ProjectBadDb=2
-- remove(first project); flush()
   sql> select pbd1_0.id,pbd1_0.owner_id,pbd1_0.title from ProjectBadDb pbd1_0 where pbd1_0.id=?
   sql> delete from ProjectBadDb where id=?
   sql> delete from AppUser where id=?
raw rows: ProjectBadDb=0  (both projects gone, no error)

== 4. The fix: ProjectGood, no cascade
-- remove(first project); flush()
   sql> select pg1_0.id,pg1_0.owner_id,pg1_0.title from ProjectGood pg1_0 where pg1_0.id=?
   sql> delete from ProjectGood where id=?
raw rows: ProjectGood=1 AppUser=1 new user(s) kept
