Hi,
I have:
context.deleteObjects(themeDataObject);
context.commitChanges();
and with full logging I can see that commitChanges() invokes the following:
19:11:19,390 INFO QueryLogger:421 - --- will run 1 query.
19:11:19,421 INFO QueryLogger:377 - --- transaction started.
19:11:19,453 INFO QueryLogger:315 - SELECT t0.clazz, t0.dataDigest,
t0.id, t0.contentType, t0.data, t0.provider, t0.specification, t0.theme
FROM image t0 WHERE t0.theme = ? [bind: 200] - prepared in 16 ms.
19:11:19,500 INFO QueryLogger:360 - === returned 0 rows. - took 63 ms.
19:11:19,515 INFO QueryLogger:386 - +++ transaction committed.
It does this because I've got it cascade set to DENY if any images are
associated with a theme being deleted. I expect that once it sees that
the delete is safe it should delete the theme from the DB, but i never
does. How do I find out why the theme is not being removed? Is there
extra logging I can enable? It looks like it's failing silently. The
theme being deleted has a COMMITED persistence state.
Thanks,
Gili
-- http://www.desktopbeautifier.com/
This archive was generated by hypermail 2.0.0 : Thu Sep 08 2005 - 19:16:33 EDT