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

Component fields upgrade #122

Closed
indpurvesh opened this issue Apr 13, 2024 · 0 comments · Fixed by #200
Closed

Component fields upgrade #122

indpurvesh opened this issue Apr 13, 2024 · 0 comments · Fixed by #200
Assignees
Labels
backend enhancement New feature or request

Comments

@indpurvesh
Copy link
Member

Currently, we do store the component fields as a separate table and use surrealdb edge content to link the component with fields table record. Seems like there is not bigger advantage of linking to a fields table so we should simply store the components fields into an components table fields column.

@indpurvesh indpurvesh added enhancement New feature or request backend labels Apr 13, 2024
@indpurvesh indpurvesh self-assigned this Jul 26, 2024
@indpurvesh indpurvesh linked a pull request Jul 27, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend enhancement New feature or request
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant