Grouper Users - Open Discussion List

[Jim Fox <>]

I did do that.  Same result.  no flats, no pit loads.

Jim


On Mon, 4 Jun 2012, Chris Hyzer wrote:

> Date: Mon, 4 Jun 2012 14:03:16 -0700
> From: Chris Hyzer 
> <>
> To: Jim Fox 
> <>
> Cc: Shilen Patel 
> <>,
>     grouper users list 
> <>
> Subject: RE: [grouper-users] upgrade 1.6 to 2.1
>
> Can you try it on the 1.6 to 2.1 upgrade?  :)
>
> I think ddlutils is having trouble finding the tables since it doesn't know 
> the schema and it uses jdbc metadata, not sure though...
>
> Thanks,
> Chris
>
> -----Original Message-----
> From: Jim Fox 
> [mailto:]
> Sent: Monday, June 04, 2012 4:56 PM
> To: Chris Hyzer
> Cc: Shilen Patel; grouper users list
> Subject: RE: [grouper-users] upgrade 1.6 to 2.1
>
>
> If tried two ways: one with the line commented out and one with
>
>  ddlutils.schema = public
>
> I think I used the latter on the 1.6 to 1.7 upgrade.
>
> Jim
>
>
> On Mon, 4 Jun 2012, Chris Hyzer wrote:
>
> > Date: Mon, 4 Jun 2012 13:46:35 -0700
> > From: Chris Hyzer 
> > <>
> > To: Jim Fox 
> > <>,
> >  Shilen Patel 
> > <>
> > Cc: grouper users list 
> > <>
> > Subject: RE: [grouper-users] upgrade 1.6 to 2.1
> >
> > You might want to uncomment this in the grouper.properties:
> >
> > ddlutils.schema = whatever_schema
> >
> > for the schema in postgres.  Unlike Oracle and Mysql, the postgres schema is 
> > different than the userid right?
> >
> > Thanks,
> > Chris
> >
> > Ps. I was just about to ask for grouper_ddl contents too but Shilen beat me 
> > to it :)
> >
> > -----Original Message-----
> > From: 
> >
> >  
> > [mailto:]
> >  On Behalf Of Jim Fox
> > Sent: Monday, June 04, 2012 4:30 PM
> > To: Shilen Patel
> > Cc: grouper users list
> > Subject: Re: [grouper-users] upgrade 1.6 to 2.1
> >
> >
> >
> > The test 1.6 database is a copy of my production system (v1.6).
> > I ran the 'gsh -registry -check' on it.  The resulting sql file
> > can be found at:
> >
> >    http://urizen4.cac.washington.edu/grouperDdl_20120604_11_09_36_938.sql.txt
> >
> >
> > I am using postgres.  My hybernate properties has
> >
> >   hibernate.connection.url = jdbc:postgresql://localhost/gws1dev
> >   hibernate.dialect =
> >   hibernate.connection.driver_class =
> >    (those are the autodetect options)
> >
> > Jim
> >
> >
> >
> > On Mon, 4 Jun 2012, Shilen Patel wrote:
> >
> > > Date: Mon, 4 Jun 2012 13:14:20 -0700
> > > From: Shilen Patel 
> > > <>
> > > To: Jim Fox 
> > > <>,
> > >     grouper users list 
> > > <>
> > > Subject: Re: [grouper-users] upgrade 1.6 to 2.1
> > >
> > > The upgrade should take care of populating those table.  If you want to
> > > send me your upgrade script and let me know what type of database you're
> > > running (postgres?), I can take a look at what's wrong.
> > >
> > > Thanks!
> > >
> > > -- Shilen
> > >
> > >
> > > On 6/4/12 3:57 PM, "Jim Fox" 
> > > <>
> > >  wrote:
> > >
> > > > When I did a test upgrade of 1.6 to 1.7 (when the pit tables were added)
> > > > the conversion sql script had entries like these:
> > > >
> > > >    drop table grouper_flat_memberships cascade;
> > > >    drop table grouper_flat_groups cascade;
> > > >    drop table grouper_flat_stems cascade;
> > > >    drop table grouper_flat_attribute_def cascade;
> > > >
> > > >    insert into grouper_pit_fields ...
> > > >    insert into grouper_pit_stems ...
> > > >    ...
> > > >
> > > >
> > > > When I try a conversion of a test 1.6 to 2.1 I don't see those entries.
> > > > My 1.6 DB has the flat tables and does not have the pit tables.
> > > >
> > > > Is there another way the tables are being populated nowadays?
> > > >
> > > > Jim