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

Remove version history model and table #1285

Merged
merged 2 commits into from
May 25, 2016

Conversation

sonalkr132
Copy link
Member

Attempt - II

My previous PR was roasted #1277:

PG::DependentObjectsStillExist: ERROR: cannot drop table version_histories because other objects depend on it

Hopefully this will work 🙏 👷

@simi
Copy link
Member

simi commented May 24, 2016

Last use instance of version history removed at: 9207533
@sonalkr132
Copy link
Member Author

@simi thanks. I have updated it.

What do people think about using png instead of svg? With svg, everything gets smushed together and I am seeing columns types like string ∗ U (in place of string *).
svg:
https://github.com/sonalkr132/rubygems.org/blob/force_r-version_history/doc/erd.svg

png:
erd

@simi
Copy link
Member

simi commented May 24, 2016

I can see properly rendered svg on your link, but it wasn't updated for a while.
I have no idea what's preferred here now. Do we need Doorkeeper and LogTicket in erd scheme?

If we need to keep erd updated, we can add it to specs (I can contribute this).

@dwradcliffe
Copy link
Member

Yes let's keep it updated. Png is fine with me if it renders fine/better.


David Radcliffe

On Tue, May 24, 2016 at 9:05 AM, Josef Šimánek notifications@github.com
wrote:

I can see properly rendered svg on your lin, but it wasn't updated for a
while.
I have no idea what's preferred here now. Do we need Doorkeeper and
LogTicket in erd scheme?

If we need to keep erd updated, we can add it to specs (I can contribute
this).


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#1285 (comment)

@sonalkr132
Copy link
Member Author

sonalkr132 commented May 24, 2016

@simi this is what svg looks on my computer.

screenshot from 2016-05-24 18-42-49

EDIT: link

@simi
Copy link
Member

simi commented May 24, 2016

Weird, browser and image viewer is ok with that. I think we can open new issue for this, since it is not related to this PR.

snimek z 2016-05-24 15-20-37

@dwradcliffe
Copy link
Member

Ohhh! The problem is there is another table! The error message even says that, I just didn't notice. There is a version_histories_import table which is linked to the version_histories table. I have tested this on staging and it works. I'm going to merge this because I've already run this but we still need to remove the other table. @sonalkr132 can you send a new PR to remove the version_histories_import table?

@dwradcliffe dwradcliffe merged commit efe8b8f into rubygems:master May 25, 2016
@dwradcliffe dwradcliffe temporarily deployed to staging May 25, 2016 18:28 Inactive
@sonalkr132 sonalkr132 deleted the force_r-version_history branch May 25, 2016 19:21
@sonalkr132
Copy link
Member Author

we are putting the table to peace 💀 manual way.

@dwradcliffe dwradcliffe temporarily deployed to production May 27, 2016 20:21 Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants