We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When querying on Slack for CW puzzles, languages aren't taken into account in the Django queries.
The q query will be a dictionary with a languages key that holds a Python list. The structure is like this:
q
languages
{'languages': ['fortran', 'cobol', 'raku'], 'source': 'codewars', 'difficulty': 3}
The relevant data is stored as JSONB in Postgres. An example raw SQL query is:
SELECT original_raw_data ->> 'languages' FROM puzzles_puzzle WHERE source='Codewars' LIMIT 1; -- ["javascript", "haskell", "python", "rust"]
The Django query should return a puzzle that includes all of the languages that in listed in the q query.
See the notes that will be in apps/puzzles/puzzles.py.
apps/puzzles/puzzles.py
The text was updated successfully, but these errors were encountered:
Check out 9:20 in this video for how to do queries on JSON fields: https://www.youtube.com/watch?v=LbdUpY1I1zg
Sorry, something went wrong.
If it requires raw queries, this SO answer might help: https://dba.stackexchange.com/a/162595
No branches or pull requests
When querying on Slack for CW puzzles, languages aren't taken into account in the Django queries.
The
q
query will be a dictionary with alanguages
key that holds a Python list. The structure is like this:The relevant data is stored as JSONB in Postgres. An example raw SQL query is:
The Django query should return a puzzle that includes all of the languages that in listed in the
q
query.See the notes that will be in
apps/puzzles/puzzles.py
.The text was updated successfully, but these errors were encountered: