Test that an index over the @CaseInsensitive copy serves the lookup on each store
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 40/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- postgresql, python
- Domain
- databases, testing-qa
Research direction
Start from the golden statements and index DDL added in #364, which pin the ignore-case lookup over the __drivine.lower.<prop> copy, and from the reference EXPLAIN checks in drivine4j #149. For each store (Neo4j, Memgraph, FalkorDB, Postgres, Oracle), add a test that runs the lookup's plan and asserts the index over the copy is used, starting with Postgres since it's the easiest to run locally. Done means each engine's plan check passes and fails if the index is dropped; Oracle should check that the labelled-index read is used.
Written by the indexing model from the issue text.
Description
Follow-up from the review of #364 (Port of liberation-data/drivine4j#149).
drivine4j #149 has a test per engine that asks the store's plan (EXPLAIN) whether an ignore-case lookup uses the index over the __drivine.lower.<prop> copy ("an index over the copy serves the lookup"). This port pins the lookup statements and the index DDL in the golden statements, but no test asks the engine whether it actually uses the index, so a change that stops the store from using it would pass.
Port drivine4j's plan checks for Neo4j, Memgraph, FalkorDB, Postgres and Oracle. On Oracle, check that the labelled-index read is used.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 1h 53m
- Merged PRs (30d)
- 157
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from liberation-data/drivine-python
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
liberation-data/drivine-python#363 ·
Maintainers usually reply within 1 day
-
Docs: drivine4j doesn't read the flat DATABASE_* variables, as 02-connecting.md and design.md sayOpendocumentation
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
liberation-data/drivine-python#361 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
liberation-data/drivine-python#250 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
liberation-data/drivine-python#209 ·
Maintainers usually reply within 1 day
-
CI: three Oracle-only tests in test_cypher_compiled.py never run, as -k oracle doesn't select themOpen
Difficulty 1/5 Under an hour Newbie friendliness 88/100
liberation-data/drivine-python#178 ·
Maintainers usually reply within 1 day
All issues in liberation-data/drivine-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
elviskahoro/sdk-python-attio#144 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
RenyiELBO raises TypeError when model has no sample sitesPossibly taken @alibb007 claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day