Grouper Users - Open Discussion List

[GAIL JOY DUNMIRE <>]

Per the suggestion below, we changed the subject_id value in accordance to the change to the subject source view for subject_id in the sources.xml. We did a direct database update to make the grouper_members table match the new subject source.

Prior to the above changes, a USDU() command completed without errors. After the change, the same command exited with this error:

// Error: Problem in HibernateSession: HibernateSession (2d6b0fd0): new, readonly, READONLY_NEW, notActiveTransaction, session (11b8c95b),
Exception in uniqueResult: (class edu.internet2.middleware.grouper.Member), ByHqlStatic, query:

'from Member as m where      m.subjectIdDb       = :sid    and  m.subjectSourceIdDb = :source and  m.subjectTypeId   = :type',

cacheable: true, cacheRegion: edu.internet2.middleware.grouper.internal.dao.hib3.Hib3MemberDAO.FindBySubject,

tx type: null, tx type: nullBind var[0]: 'Param (class java.lang.String): 'sid'->'',

Bind var[1]: 'Param (class java.lang.String): 'type'->'person'Bind var[2]: 'Param (class java.lang.String): 'source'->'psuperson',

Looking up the new subject id  '' in the interface, it is in the correct group.

Is there something else we need to change?

Thanks,

Gail

---

From: "Chris Hyzer" <>
To: "kumi hagimoto" <>,
Sent: Wednesday, October 28, 2015 7:55:42 AM
Subject: RE: [grouper-users] Changing a userName(subjectId)

I think you can just change the subject_id field in the database table grouper_members for that record.  The reason for memberChangeSubject is there will be a foreign key problem if the new subject exists.  Shilen, let me know if you disagree here.  Kumi, if this is what you want to do, you can do that directly in the DB or I can give you GSH to do this...  note, if the old subject is still being resolved and used after you make the change, it will create a new grouper_members record for the old subject again.

Thanks,
Chris