From: Rory Larson email@example.com
Sent: Friday, May 11, 2018 9:49 PM
To: Hyzer, Chris <firstname.lastname@example.org>; email@example.com
Subject: RE: Grouper name length limits?
This is only a demo for now, and certainly I can abbreviate if necessary. But having to do so seems to defeat the purpose of having a full name. The project is to build an institutional hierarchy from the top university level down to the bottom-level department or reference group eight or ten levels deep, and some offices/departments/programs tend to have rather lengthy names, since there is no common English word by which to call them. But I would imagine that political sensitivities might be ruffled if I start chopping the names of people’s favorite departments down to something reasonable.
It’s not a huge issue at the moment, but I did want to get a feel for where things stood on this. Is that a varchar-256 limitation that can’t be made bigger because it would double the size of the database?
I Created a 2.2 extension longer than 50… but yes looks like there is a full name constraint of 256... can you abbreviate somehow?
From: firstname.lastname@example.org [email@example.com] On Behalf Of Rory Larson
Sent: Friday, May 11, 2018 7:26 PM
Subject: [grouper-users] Grouper name length limits?
Using the UI for Grouper 2.2, I'm trying to mock up a fairly deep tree of administrative hierarchy, and it looks like I'm running into limits on name length. For an immediate folder name, it seems that the entry box cuts you off at 50 characters. For the fully scoped name, I seem to be hitting a limit of about 250 or 256 characters, beyond which it simply fails to create the folder and gives an error message.
I was wondering if anyone would care to comment on this. Is this an intentional constraint to meet a resource trade-off? Is it a limit that can be modified locally, or is it baked into Grouper? Will these limits continue into future versions of Grouper?