Skip to Content.
Sympa Menu

grouper-users - [grouper-users] Re: Obliterate stem problem?

Subject: Grouper Users - Open Discussion List

List archive

[grouper-users] Re: Obliterate stem problem?

Chronological Thread 
  • From: Earl Lewis <>
  • To: Chris Hyzer <>, "<>" <>
  • Subject: [grouper-users] Re: Obliterate stem problem?
  • Date: Thu, 30 May 2013 21:16:31 +0000
  • Accept-language: en-US
  • Authentication-results:; dkim=neutral (message not signed) header.i=none

I wouldn't want Grouper to assume too much of anything I don't think. I'd just like to see a warning that some groups won't be able to be removed because of referencing groups. If you throw the warning then you can let the user decide how to react to it. 

Actually, if you build the test/warning mechanism then you could run the same test silently, unless it has an error, prior to doing a live run. When you throw a specific enough error for the user to know what's going on then they can decide what action to take before proceeding.

801-581-3635 (office)
801-554-3596 (mobile)

On 5/30/13 1:15 PM, "Chris Hyzer" <> wrote:

Hmmm, good point…   seems like readonly should give you a heads up, and readwrite should not even start until you address those issues.  I don’t think there is an easy way for Grouper to assume what you want to have happen to those groups…  thoughts?





From: []On Behalf Of Earl Lewis
Sent: Thursday, May 30, 2013 2:46 PM
To: <>
Subject: [grouper-users] Obliterate stem problem?


I tried running obliterateStem today, both in test mode and in live mode. When I ran it as a test, with obliterateStem("stem:id:path", true, false) it dutifully told me that it "Would be done deleting group: this:and:that" all the way down the stem I specified. However, when I ran it in live mode it choked on some large groups far down the list, after about 30-40 mins. of processing. 


The reason for the failure was that there was a composite group in another stem referencing the group trying to be deleted. So there was an integrity constraint violation in the database and processing failed. Test mode failed to reveal this fact and so I just went ahead assuming everything was going to work. 


Is this something that the test mode could/should detect and report? It would certainly be nice if it would because then you'd have a heads up that there's some maintenance to do before you attempt to run it for real. I'd be glad to submit this as a bug if it's something that really ought to be fixed. Let me know what you think.



801-581-3635 (office)

801-554-3596 (mobile)

Archive powered by MHonArc 2.6.16.

Top of Page