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

Add a self referential column #5

Open
silentninja opened this issue Aug 17, 2022 · 3 comments
Open

Add a self referential column #5

silentninja opened this issue Aug 17, 2022 · 3 comments
Labels
status: ready Ready for implementation type: enhancement New feature or request work: backend Related to Python, Django, and simple SQL
Milestone

Comments

@silentninja
Copy link

Problem

There isn't a way to test self-referencing column features with the current dataset. Can a column with self reference reference be added?

@silentninja silentninja added type: enhancement New feature or request work: backend Related to Python, Django, and simple SQL status: draft Details need to be clarified before work can begin labels Aug 17, 2022
@kgodey
Copy link
Contributor

kgodey commented Aug 17, 2022

I think it would also be good to add a table with two FK references to a different table (e.g. imagine a Package table that has columns for from address and to address that are both FKs to an Address table)

@kgodey kgodey added this to the Cycle 4: Live Demo milestone Aug 17, 2022
@silentninja silentninja changed the title Circular reference Add a self referential column Aug 17, 2022
@mathemancer
Copy link
Contributor

mathemancer commented Aug 18, 2022

@kgodey do you think we should extend the library data set, or do something different? N.b., we already have an academics data set with both features mentioned in the Mathesar testing resources directory. We could simulate a larger version of that if we want.

@kgodey
Copy link
Contributor

kgodey commented Aug 18, 2022

@mathemancer I think we should have a separate data set so we don't contaminate the demo data set. I don't have a preference on extending the library data set or creating a new one. I think whatever is fastest to implement is better.

@kgodey kgodey modified the milestones: Cycle 4: Demo Video, Cycle 5: Live Demo Sep 14, 2022
@kgodey kgodey added status: ready Ready for implementation and removed status: draft Details need to be clarified before work can begin status: ready Ready for implementation labels Sep 19, 2022
@kgodey kgodey modified the milestones: Cycle 5: Live Demo, Backlog Jan 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: ready Ready for implementation type: enhancement New feature or request work: backend Related to Python, Django, and simple SQL
Projects
No open projects
Development

No branches or pull requests

3 participants