Skip to Content.
Sympa Menu

grouper-users - RE: [grouper-users] Stem display_name column length

Subject: Grouper Users - Open Discussion List

List archive

RE: [grouper-users] Stem display_name column length

Chronological Thread 
  • From: "Black, Carey M." <>
  • To: Sean Mason <>, Grouper Users <>
  • Subject: RE: [grouper-users] Stem display_name column length
  • Date: Mon, 1 Jun 2020 19:38:49 +0000
  • Arc-authentication-results: i=1; 1; spf=pass; dmarc=pass action=none; dkim=pass; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=8DGUHmHIEPMKRXlA/BlAikgCI1sJep+06iZRF5vgOMw=; b=i4K1CASCyHY+RCV9mJEoj0BwIhce0d69z3ofvd5lRFrW2MMVa8+xxVU4LmPBdRQr5W2byn8vvOBCw9eElPJGoX9tOGsn6vq1tKHeB/4vd/iF8UKhSBcgBkZfd4foFnzIgsdqGXPd38yYN1ZXGAnVych1i3YHxhfbqgIu//BAbVE8MGw9Owd8HLcvJ/NdKV/k/1oAFHS1Ns4rnDXQ63nbsJdssUBpWARPB4/ilORh+xDgICaphH093UfNxIEUhnaiTYEyCixxj4zy+Mu4qaSJ7KKgRcZ4x4OrXC/Mazb0jRTMLM9q4ckoKfkuV4uwq6mTab+M18Rsp0f6Z+qBIeaTJA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=dlx4zDcCsC9Gn0LXJ4p1d9sOp6PudZwT93PGk2AcEtPp96p9P1Bz55PSEW8NVT3jPXPsYWIjS7pHv5621FPkTjpzi+R3k+IQIT0LZQpG7EuhIauWlXGBgV9IxzBSRjIWdWN6CBUxxA8djhh/ZrBaWB9DhmcahWTkbEyKfLb/0MoXS5tSRrBDg4KBq8jW2GKOJn9kHkzWoho/Sx6JKI4HDvMjGBr0wXQLlqCMpA1vLAvXb5gR35/S6E2u0dm/0kkFfcfZgmRgs3Q2qNmlN2jKDgfqQaOV1PmyKAmH52JnQmuafEVAC81I/sZoRS2GQ24eZixGCsSdcNFPTCtrxxsV7w==



NOTE: I wonder how this will “work” with the current v2.5 “ddl auto update” tooling too.


Meaning making any change from the “expected” could lead to issues when you move forward to the next container.

I suggest that any advancement in the container be used with caution.



I wonder if this “plan” is dealt with in the “auto ddl world” ?



Carey Matthew


From: Sean Mason <>
Sent: Monday, June 1, 2020 3:24 PM
To: Black, Carey M. <>; Grouper Users <>
Subject: RE: Stem display_name column length


That does indeed help, an increase in size to the schema and adding grouper.stemName.maxSize = <larger number here> to has cleared the issue.


Thank you for your help!



From: Black, Carey M. <>
Sent: Monday, June 1, 2020 3:03 PM
To: Sean Mason <>; Grouper Users <>
Subject: RE: Stem display_name column length




I found this:


So it looks like there is a planned way to do this.





Carey Matthew


From: <> On Behalf Of Sean Mason
Sent: Monday, June 1, 2020 9:25 AM
To: Grouper Users <>
Subject: [grouper-users] Stem display_name column length


Hi There,


I’ve been working on upgrading our Grouper v2.4 instance to 2.5 and things are going very well now that I’ve (somewhat) wrapped my head around Docker.  The system has really been a star in our IAM system renewal efforts.


One thing I have noticed that I’ve missed in our installation (this is not a problem resulting from the upgrade) is that the maximum length of the display_name field for grouper_stems is 255 characters.  We have some HR org data that (believe it or not) exceeds this length.


Is it safe for me to extend the length of that field in the schema?  If not is it possible the length of the field could be made to match the length of the display_name field in the grouper_groups table in an upcoming version?


Thank you,


Archive powered by MHonArc 2.6.19.

Top of Page