Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

upgrade database version to beta2 #1842

Merged
merged 3 commits into from Dec 6, 2013
Merged

Conversation

mtbc
Copy link
Member

@mtbc mtbc commented Nov 27, 2013

There are no more model changes going into beta2, those planned are postponed to beta3.

@joshmoore, @pwalczysko: One may wish to exclude this PR until we are ready to purge gretzky's database.

As part of testing, one may wish to verify that the system works okay after an upgrade from 4.4 via sql/psql/OMERO5.0DEV__6/OMERO4.4__0.sql then sql/psql/OMERO5.0__0/OMERO5.0DEV__6.sql. Also it should work okay with a database created from OMERO5.0__0.sql generated by bin/omero db script. Update: see #1842 (comment).

--no-rebase

@joshmoore
Copy link
Member

Thanks, @mtbc, excluding now (which you can do yourself these days with ...

(exclude comment removed on Dec. 4, 2013)

@joshmoore
Copy link
Member

@mtbc: could this be created via a git mv on DEV6?

@mtbc
Copy link
Member Author

mtbc commented Dec 2, 2013

It could. I'd assumed we wanted to keep the DEV6 scripts given that we had actually released beta1, but perhaps we will not want to preserve the SQL for the betas in that way?

@joshmoore
Copy link
Member

The scripts to OMERO5__0 from both OMERO4__0 and OMERO5DEV__6 should certainly be kept in this directory, but from OMERO4__0 to OMERO5DEV__6 can be removed.

@pwalczysko : could you let us know when an appropriate time to include this would be? We would need to either start from a fresh DB or perform a DB upgrade. Thanks.

upgrade script from beta1 already exists
@mtbc
Copy link
Member Author

mtbc commented Dec 3, 2013

@joshmoore: Do you want the OMERO5.0DEV__6.sql script's work to be done also by OMERO4.4__0.sql or should I include a README saying to run both if upgrading from 4.4? (Or the from-4.4 script could end by saying, now run the other one.)

@pwalczysko
Copy link
Member

@mtbc @joshmoore Would it be too late to have the DB dropped after the last Workshop, this means after ca 15.00 on Thursday 5th December (this Thurs) ?

@mtbc
Copy link
Member Author

mtbc commented Dec 3, 2013

Well, I'm not here on Friday nor over the following week, so as long as I don't need to be picking up any pieces ... (-:

@joshmoore
Copy link
Member

@pwalczysko : can certainly be done. Let's discuss tomorrow.

@mtbc: there should be a single upgrade script for OMERO4.4__0 users.

@pwalczysko
Copy link
Member

Seems like my dragging might cause some unnecessary pressures for Mark. I am happy for the DB to be dropped immediately. (my reasons for holding off till Thursday were merely a presence of the images for FLIMfit demo - but I can import the same images to Howe)

@joshmoore
Copy link
Member

Exclude comment removed for next re-build.

@joshmoore
Copy link
Member

Note: deploying this from a manual build on omero4-demo

@jburel
Copy link
Member

jburel commented Dec 5, 2013

removing exclude so it can be part of the build

@joshmoore
Copy link
Member

This was successfully deployed with PURGE_DATA on gretzky. Merging; with @mtbc away, if anything needs fixing, it'll happen in another PR.

joshmoore added a commit that referenced this pull request Dec 6, 2013
upgrade database version to beta2
@joshmoore joshmoore merged commit 8a049a1 into ome:develop Dec 6, 2013
@mtbc mtbc deleted the db-version-beta2 branch December 16, 2013 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants