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

Save and SaveorUpdate #530

Open
arya-hemanshu opened this issue Mar 14, 2018 · 2 comments
Open

Save and SaveorUpdate #530

arya-hemanshu opened this issue Mar 14, 2018 · 2 comments

Comments

@arya-hemanshu
Copy link
Contributor

Description

Save and update requires to check in the database whether the entry exists or not,
if exists it updates else adds, but that increase overhead and compute time as it will have to check for every single value.
A temporary new method called saveWithoutUpdate has been added to overcome this but it would only work if there are no duplicate records, if there are duplicate records it will ignore it.

Need a better approach to handle this issue, so that it is fast and also keeps the same functionality at the same time.

Error log

None

@lorenaqendro
Copy link
Contributor

I'm a sad issue :( I would love to have tags and belong to a milestone. Please help me! :D

@lorenaqendro
Copy link
Contributor

Harmonise this behaviour for all the entities in the datastore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants