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

Database Transactions #190

Open
Timu57 opened this issue Apr 13, 2021 · 1 comment
Open

Database Transactions #190

Timu57 opened this issue Apr 13, 2021 · 1 comment

Comments

@Timu57
Copy link
Member

Timu57 commented Apr 13, 2021

As pointed out by @daussho in #177 a database transaction feature with automatic rollback would be awesome.

Interesting articles regarding database transactions:

https://en.wikipedia.org/wiki/Database_transaction
https://en.wikipedia.org/wiki/ACID

https://en.wikipedia.org/wiki/Software_transactional_memory

@REDAL
Copy link

REDAL commented Aug 24, 2021

@Timu57 @rakibtg

Did you did further reading about this idea ?!

how about, making temporary files of the query, then verifying if everything went good, just renaming the files with the next id

for example, when trying to make 2 writing in 2 different tables, that are related, just make a temporary file table1.x(id).temp
and make the second writing, table2.x(id).temp, if both operations were successful, then rename the files

table1/256
table2/317

what do you think of this practice

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