21–28 of 28 posts
Check out https://morph.is/v0.8/ if you haven't seen it, decentralized encrypted file storage and email, exciting stuff.
43 exclamation points on the front page. He has the hype cranked up pretty high. Still, it's nice to see all of these P2P efforts.
Earlier quoted context omitted.
I'm using upserts... The reason I'm using upserts is basically just lazyness because I didn't feel like refactoring the source code to work around requiring upserts. Also, I'm not very confident in C++ so I did not want to take on that task.
You can fix this with basic SQL IF record EXISTS then UPDATE else INSERT
Check out https://morph.is/v0.8/ if you haven't seen it, decentralized encrypted file storage and email, exciting stuff.
> Transactions are FREE (the fee is always zero) How would you deal with DDoS attacks? Taking down a ledger like this could be easy...
Cloudflare doesn't have to charge a fee for every http request, although transaction fees do seem like the elegant solution.
Earlier quoted context omitted.
You can fix this with basic SQL IF record EXISTS then UPDATE else INSERT
No. Conccurrency makes it way harder than that.
I think all database applications should be written like this at least until performance starts being an issue.
Earlier quoted context omitted.
No. Conccurrency makes it way harder than that.
In PostgreSQL, you can set the SERIALIZABLE isolation level for the whole database, put a retry loop around all database transactions and completely stop worrying about concurrency issues. I think all database applications should be written like this at least until performance starts being an issue.
Yet Another problem is that you need to enforce all sessions potentially involved in a data race need to use serializable; that can be easy or hard, depending on the scenario.
Earlier quoted context omitted.
No. Conccurrency makes it way harder than that.
In PostgreSQL, you can set the SERIALIZABLE isolation level for the whole database, put a retry loop around all database transactions and completely stop worrying about concurrency issues. I think all database applications should be written like this at least until performance starts being an issue.
Increasing the transaction isolation level shouldn't be done out of laziness.