This repository has been archived by the owner on Mar 11, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 86
Introduce number column for area and iteration and allow searching it #2287
Merged
Merged
Changes from 4 commits
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
4264d00
Began human friendly number sequence
kwk 12aeabb
Writing tests
kwk c294902
Fixup
kwk bd2a0d7
Finish migration scripts and tests
kwk b46ef60
test for iteration and area
kwk 9e282da
update golden files
kwk c3015fe
added postgres.conf
kwk 819903b
fixup
kwk a969660
Add concurrent create test
kwk 7963eee
Merge remote-tracking branch 'upstream/master' into human-friendly-nu…
kwk 1f66c9a
Format code
kwk afa5820
fix TestHumanFriendlyNumber_Equal
kwk bb94130
Fix TestWorkItem_Equal
kwk 8fe8ffe
Run equal tests in parallel and address https://app.codacy.com/app/kw…
kwk 169056f
Add index over (space_id,number) for areas and iterations
kwk dea67a3
Add BeforeUpdate callback
kwk 3b94546
Address https://github.com/fabric8-services/fabric8-wit/pull/2287/fil…
kwk f7ce028
Fixup
kwk b97c28e
See https://github.com/fabric8-services/fabric8-wit/pull/2287#discuss…
kwk d1e3265
butt lifting
kwk 73f1611
add search by iteration.number and area.number
kwk File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should alter table to add unique constraint instead of creating a unique index? Looks like this is the preferred approach for PostgreSQL: https://www.postgresql.org/docs/9.4/static/indexes-unique.html
ALTER TABLE iterations ADD UNIQUE (space_id, number)
or
ALTER TABLE iterations ADD CONSTRAINT iterations_space_id UNIQUE (space_id, number);
The doc above also states that only b-tree indexes can be declared as unique. Maybe we don't need to explicitly specify
USING BTREE
...?It probably doesn't hurt, and i don't think adding the index manually has any sort of impact - not sure why it's 'preferred.' What do you think Konrad?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've changed it to the preferred syntax in b97c28e.