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

Migration strategy for having changes to analytics table updated in projects already using the gem #32

Open
akshaymohite opened this issue Jun 26, 2019 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@akshaymohite
Copy link
Contributor

Conversation from Slack.

Akshay [3:50 PM]

  • @here currently, we create required table specterr_analytics on the fly.
  • if it exists, we don’t.
  • what should we do if columns are changed?
  • for e.g. let’s say we want to remove line_no column

Kapil [3:52 PM]

  • I think, in create table we have to add it. by dropping existing tables.

Akshay [3:52 PM]

  • for now, it’s fine
  • in future, let’s say people already have this table
  • in short, we don’t have migration strategy as of now

We need to come up with a migration strategy for having changes to analytics table updated in projects already using the gem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

No branches or pull requests

1 participant