-
Notifications
You must be signed in to change notification settings - Fork 87
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
Document setting up full text search #100
Comments
Would a simple migrations.RunSQL("ALTER TABLE judge_problem ADD FULLTEXT(code, name, description);") Added to a new migration not just do the trick? |
RIP anyone who uses SQLite for basic local development then. |
Oop true, a RunPython which checks the database configuration and then runs the SQL using |
You should use the schema editor, but sure, PRs welcome. |
This is already not possible due to https://github.com/DMOJ/online-judge/blob/27f5a0e2e308e73a9fb1bf4ac264c1cbc6d1677a/judge/migrations/0089_submission_to_contest.py#L19 running an INNER JOIN in a format which SQLITE does not accept. |
Adds a FULLTEXT index to the `Problem` model as needed by the builtin search. Includes migration and tests (skipped for non-MySQL databases). see DMOJ/docs#100
The database schema generated through the migrations do not support FTS. The indexes must be created manually:
The text was updated successfully, but these errors were encountered: