Merge lp:~jml/pkgme-devportal/uniqueness-constraint into lp:pkgme-devportal
Proposed by
Jonathan Lange
Status: | Rejected |
---|---|
Rejected by: | James Westby |
Proposed branch: | lp:~jml/pkgme-devportal/uniqueness-constraint |
Merge into: | lp:pkgme-devportal |
Diff against target: |
39 lines (+10/-4) 2 files modified
db/patch-00001.sql (+7/-0) devportalbinary/tests/test_database.py (+3/-4) |
To merge this branch: | bzr merge lp:~jml/pkgme-devportal/uniqueness-constraint |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
James Westby | Needs Information | ||
Review via email: mp+120206@code.launchpad.net |
Commit message
Relax the uniqueness constraint to include architecture.
Description of the change
This relaxes the uniqueness constraint so that when we rollout a patch
that populates architecture, we will be able to add the same dependency
for multiple architectures.
Oh, I'm not convinced that landing this is a good idea, so please don't Approve it without discussing with me.
To post a comment you must log in.
Unmerged revisions
- 84. By Jonathan Lange
-
Flakes
- 83. By Jonathan Lange
-
Update the uniqueness constraints. Change the expected behaviour for double inserts.
Hi,
1. If this is going in the patch-00001.sql file then we want to land it before applying that patch?
2. What makes you think this isn't a good idea.
3. Perhaps we want a XFAIL test for now?
4. In fact I'm not sure why the test passes? Is NULL always considered unique?
Thanks,
James