MariusVolkhart / MariusVolkhart/squiggle-sql
Possibility to avoid duplicate selection, criteria and order statments in SelectQuery
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
```
It would be nice to avoid duplicates (equals) in the SelectQuery.
So one could just add e.g. criteria in an automatic processing and the
SelectQuery would not add an already existing criterion.
This could be easy enhanced by using e.g. a LinkedHashSet instead of the
List and by adding the missing equals and hashCode methods.
```
Original issue reported on code.google.com by `dbac...@gmail.com` on 7 Oct 2009 at 11:37
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by locating SelectQuery and its handling of selections, criteria, and order statements. Review how duplicate entries are currently stored and define completion as each equal selection, criterion, or order statement appearing only once while preserving insertion order; no tests or files are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- database
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100