Hi Andrus,
I was curious why this issue was rejected.
In case of the delete DENY rule, isn't it more useful to report
*which* objects prevented deletion rather than the *number* of objects?
As for the second part of the patch, I ran into conditions where I
wasn't sure why a certain object was being deleted. Sometimes cascade
delete leads to complex deletion patterns and it is useful for Cayenne
to explain what is going on. Users only see this debug information if
they enable the appropriate log4j flag so it shouldn't cause any clutter.
Did you dislike a specific aspect of the patch?
Thank you,
Gili
jira-norepl..bjectstyle.org wrote:
> Message:
>
> The following issue has been closed.
>
> ---------------------------------------------------------------------
> View the issue:
>
> http://objectstyle.org/jira/secure/ViewIssue.jspa?key=CAY-377
>
>
> Here is an overview of the issue:
> ---------------------------------------------------------------------
> Key: CAY-377
> Summary: Better logging for delete cascading
> Type: Improvement
>
> Status: Closed
> Priority: Minor
> Resolution: WON'T FIX
>
> Project: Cayenne
> Components: Cayenne Core Library
> Versions:
> 1.2 [DEV]
>
> Assignee: Andrus Adamchik
> Reporter: Gili Tzabari
>
> Created: Thu, 15 Sep 2005 5:58 PM
> Updated: Fri, 16 Sep 2005 11:44 PM
>
> Description:
> Add logging which shows which objects delete cascading deletes (i.e.
who causes who to get deleted)
>
>
> ---------------------------------------------------------------------
> JIRA INFORMATION:
> This message is automatically generated by JIRA.
>
> If you think it was sent incorrectly contact one of the administrators:
> http://objectstyle.org/jira/secure/Administrators.jspa
>
> If you want more information on JIRA, or have a bug to report see:
> http://www.atlassian.com/software/jira
>
>
-- http://www.desktopbeautifier.com/
This archive was generated by hypermail 2.0.0 : Mon Sep 19 2005 - 13:10:08 EDT