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

Upgrading to full-text on existing project crashes #416

Closed
dcporter opened this issue Jun 7, 2017 · 1 comment
Closed

Upgrading to full-text on existing project crashes #416

dcporter opened this issue Jun 7, 2017 · 1 comment

Comments

@dcporter
Copy link

dcporter commented Jun 7, 2017

Any existing project that takes the new full-text search update (#414) crashes because table exports_full_text_search_index was never created — the database looked initialized, so the whole setup phase was skipped. That makes this a breaking change, though I assume/hope it's pretty easy to check for that table specifically?

@trotzig
Copy link
Collaborator

trotzig commented Jun 7, 2017

Ah, great catch! I'll just bump the cache db filename before the release, that will "invalidate" (abandon) the old cache and create a new.

@trotzig trotzig closed this as completed in a06d3cc Jun 7, 2017
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

No branches or pull requests

2 participants