Grouper Developers Forum

[Chris Hyzer <>]

OK, thanks, I changed the upgrade instructions to look out for this in 
postgres.  Postgres and hsql and the SQL standard seem pretty limited in this 
respect compared to mysql and oracle.  I don't know of a good solution.

- If we add "cascade" to the drop view statements, that might drop 
institution views built on Grouper views, and dropping someone's code isn't a 
good idea
- If we do "create or replace" on the create statement, then if the column 
signatures change, it wont work.

If anyone has ideas let me know.

In the meantime I edited the upgrade instructions to explain this.

Thanks,
Chris

-----Original Message-----
From: Jim Fox 
[mailto:]
 
Sent: Wednesday, June 30, 2010 2:01 PM
To: Chris Hyzer
Cc: 

Subject: RE: [grouper-dev] after 1.6.0 getting db error


>
> So this is the grouper_memberships_all_v, you should see a column: owner_id
>

For some reason I already had a view 'grouper_memberships_lw_v' in my 
database.  When I ran the ddl script to upgrade to 1.6.0 the drop view of
grouper_memberships_all_v failed because of the reference to it in 
grouper_memberships_lw_v.  So I guess the create didn't work either.

I saw the error from the run, and thought I had rerun the necessary 
commands that failed.  Guess I missed something.

I recreated all the affected views and everything is fine now.

Jim