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

Update load commands to update existing data instead of flushing data #43

Open
JackMorganNZ opened this issue Mar 1, 2017 · 4 comments
Labels
backend Related to the software powering the website
Milestone

Comments

@JackMorganNZ
Copy link
Member

Currently the loadtopics and loadresources commands require the database to delete (flush) all entries and then recreate them. It should instead update existing entries, create new ones, and delete old ones. This is required when users want to create a permanent connection to a resource, topic, etc.

@JackMorganNZ JackMorganNZ added the backend Related to the software powering the website label Mar 1, 2017
@JackMorganNZ JackMorganNZ added this to the Initial Deployment milestone Mar 1, 2017
@hayleycodes hayleycodes removed their assignment Mar 5, 2017
@JackMorganNZ JackMorganNZ self-assigned this Mar 5, 2017
@JackMorganNZ JackMorganNZ modified the milestones: Initial Deployment, 2.0 Release Apr 28, 2017
@hayleycodes hayleycodes removed their assignment May 2, 2017
@JackMorganNZ
Copy link
Member Author

Moving to future milestone as not required for release.

@JackMorganNZ JackMorganNZ modified the milestones: Future, 2.0 Release May 20, 2017
@JackMorganNZ
Copy link
Member Author

@hayleyavw Do we wish to close this issue? As we are not planning on enabling user accounts for CS Unplugged.

@hayleycodes
Copy link
Contributor

Might as well stay open for external contributors, it's not on our priority list but it should be done at some point shouldn't it? Our current solution of deleting it all then creating everything all over again is not particularly elegant.

@JackMorganNZ
Copy link
Member Author

At the current point of this project, and with the planned features, it never needs to be implemented. Therefore I believe it should be closed, especially as it's a large amount of work for someone to do that wouldn't be utilised.

dhlambert pushed a commit to dhlambert/cs-unplugged that referenced this issue Mar 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Related to the software powering the website
Development

No branches or pull requests

2 participants