grouper-users - Re: [grouper-users] grouper-2.2.2 and legacy attributes
Subject: Grouper Users - Open Discussion List
List archive
- From: Shilen Patel <>
- To: Francesco Malvezzi <>, Grouper Users <>
- Subject: Re: [grouper-users] grouper-2.2.2 and legacy attributes
- Date: Thu, 3 Dec 2015 12:37:39 +0000
- Accept-language: en-US
- Authentication-results: spf=none (sender IP is ) ;
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:23
Hi,
Yes, that's by design. Those tables were just created to facilitate the
upgrade and aren't maintained anymore. The last upgrade step says this:
"The legacy attributes were backed up in separate tables. After
verifying that everything is okay, you can drop those backed up tables
by setting ddlutils.dropLegacyAttributes = true in grouper.properties,
running gsh -registry -deep and then executing the SQL file."
If you want to query the db for these attributes, take a look at the
views.
grouper_attr_asn_group_v
grouper_aval_asn_asn_group_v
Thanks!
- Shilen
On 12/3/15, 4:14 AM, "Francesco Malvezzi"
<>
wrote:
>Hi all,
>
>after running:
>
>postGrouper2_2Upgrade.gsh
>
>the grouper_attributes_legacy, grouper_fields_legacy,
>grouper_types_legacy DB tables were populated with the legacy data.
>
>But now, if I add attributes to a new group, the new attributes do not
>show up there.
>
>Is it by design that attributes now go to different tables, or am I
>missing to run a sync task?
>
>I would like to be able to query attributes and types from the grouper
>DB, do you have a ready example query to start from?
>
>thank you,
>
>Francesco
- [grouper-users] grouper-2.2.2 and legacy attributes, Francesco Malvezzi, 12/03/2015
- Re: [grouper-users] grouper-2.2.2 and legacy attributes, Shilen Patel, 12/03/2015
- Re: [grouper-users] grouper-2.2.2 and legacy attributes, Francesco Malvezzi, 12/10/2015
- Re: [grouper-users] grouper-2.2.2 and legacy attributes, Shilen Patel, 12/03/2015
Archive powered by MHonArc 2.6.16.