Skip to Content.
Sympa Menu

grouper-dev - Re: [grouper-dev] shrinking down uuid cols (for new deployments or columns)

Subject: Grouper Developers Forum

List archive

Re: [grouper-dev] shrinking down uuid cols (for new deployments or columns)

Chronological Thread 
  • From: Tom Barton <>
  • To: Chris Hyzer <>
  • Cc: "" <>
  • Subject: Re: [grouper-dev] shrinking down uuid cols (for new deployments or columns)
  • Date: Fri, 25 Sep 2009 08:30:11 -0500

Does this imply that an upgrade from v1.4.2 to v1.5.0 must include an export and reimport step, at least for MySql sites?


Chris Hyzer wrote:
How does this sound to people?

UUID length in the DB for grouper cols has been varchar 128.
Not sure why this was chosen originally since we use standard 32 char uuids
(and sometimes with some dashes).

Anyways, this is a problem for 2 reasons:

1. Mysql cant have a combined index size of 1024 (maybe less in some versions)
2. If you are doing in-memory databases, sometimes it treats varchars as chars

In the table where we have an index larger than 1024, if we make the uuid's
smaller, it fixes the issue. Shilen, TomZ and I have been discussing making
those cols smaller (they are all new cols for v1.5). However, I think we
should make all uuid's smaller. The DDLutils currently will ignore existing
columns which are a different size than they should be. So if we change the
definitions so that they are all size 40 (32 + 4 dashes + a little lee-way),
then if you have an existing schema it will leave it the way it is, and if
you are making a new schema, then it will make it size 40. If you are
importing from old to new, there shouldnt be any existing IDs larger than 40
so you will be all good.




Archive powered by MHonArc 2.6.16.

Top of Page