Skip to content
New issue

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

Ability to configure cards to enforce creation of unique tiles #4375

Closed
adamlodge opened this issue Dec 20, 2018 · 6 comments
Closed

Ability to configure cards to enforce creation of unique tiles #4375

adamlodge opened this issue Dec 20, 2018 · 6 comments
Assignees
Labels
Type: Bug Something isn't working Type: Enhancement

Comments

@adamlodge
Copy link
Collaborator

At present, it is possible on any card with cardinality of n to save tiles containing the same values over and over again. I would like to be able to configure a card in the card designer to define the set of nodes that must (in combination) be unique to save a tile to the database. This will impose a uniqueness integrity constraint that prevents entry of duplicate tiles.

@adamlodge adamlodge added sfport issue whose resolution may be supported by sfport project Type: Enhancement labels Dec 20, 2018
@chiatt chiatt removed the sfport issue whose resolution may be supported by sfport project label Mar 15, 2019
@chiatt chiatt self-assigned this Mar 15, 2019
chiatt added a commit that referenced this issue Mar 22, 2019
chiatt added a commit that referenced this issue Mar 28, 2019
chiatt added a commit that referenced this issue Mar 28, 2019
@chiatt chiatt assigned adamlodge and unassigned chiatt Mar 29, 2019
@adamlodge
Copy link
Collaborator Author

meets reqt

@adamlodge
Copy link
Collaborator Author

I noticed a UI bug where this config apprears many times in the card design UI

Screen Shot 2019-04-03 at 11.45.25 AM.png

@chiatt
Copy link
Member

chiatt commented Apr 24, 2019

@adamlodge In the latest we shouldn't be creating these extra constraint records. However, once these extra constraint records are created they will need to be removed from the app using the django shell or the database.

@adamlodge
Copy link
Collaborator Author

The unique constraint appears to work, but Arches is throwing the wrong error message when the constraint is violated.

Screen Shot 2019-12-23 at 1.08.13 PM.png

@chiatt
Copy link
Member

chiatt commented Dec 24, 2019

@adamlodge Can you take another look at this? I fixed the issued and updated it on qa.archesproject.org

@adamlodge
Copy link
Collaborator Author

meets reqt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Something isn't working Type: Enhancement
Projects
None yet
Development

No branches or pull requests

2 participants