Subject: Grouper Developers Forum
- From: Tom Barton <>
- To: Grouper Dev <>, Grouper Users <>
- Subject: Grouper v1.1 RC3
- Date: Fri, 27 Oct 2006 10:12:35 -0500
Release Candidate 2 had a bug in the XMLExporter class which prevented users from converting a Grouper v1.0 database into a Grouper v1.1 database. This issue has been addressed in Release Candidate 3, available now on the wiki at <https://wiki.internet2.edu/confluence/display/GrouperWG/Grouper+Software+Download>.
Note that Grouper v1.1 works with a Grouper v1.0 database just as well as Grouper v1.0 does. However, we found that by reordering the columns in one key table (the grouper_memberships table) significant performance gains occurred across several types of operations. We also reorded the columns in a second table (grouper_members) to explore for additional gains, but found the change only marginal. But the database schema proper - the tables, their columns, indices, and relationships - did not change at all between the v1.0 and v1.1 releases, which is why Grouper v1.1 works with a v1.0 database. But to reap that performance gain, the columns in an existing Grouper database must be reordered. A wiki topic has been created to explain how (<https://wiki.internet2.edu/confluence/display/GrouperWG/Database+Conversion+v1.0+-+v1.1>).
- Grouper v1.1 RC3, Tom Barton, 10/27/2006
Archive powered by MHonArc 2.6.16.