3 ms·
Do you think possibly they could make it optional and not turned on by default? Like maybe by requiring completely different keywords for concurrent vs non-con
by daveguy 3y ago
Do you think possibly they could make it optional and not turned on by default?
Like maybe by requiring completely different keywords for concurrent vs non-concurrent?
- Groxx 3y agoI get the sarcasm, but I also run into many, many, many product-team-management and company-wide-infra-decision-making types that mandate concurrency when it is available, and slam it through regardless of the cost. With teams dominated by freshly-graduated-from-college engs. And loads of times that I've seen existing systems hit a performance bottleneck, and the solution was to relax consistency because it speeds up and the existing tests pass. Putting a loaded gun within reach of millions of people is less safe than not doing that.
- valenterry 3y agoSee it positive! I've known too many cases where NoSQL databases where forced upon developers because of HA and concurrency/performance. Now I can at least say "wait, there is concurrency in SQLite if we need it. No problem".
- Groxx 3y agoDefinitely agreed there. More SQLite is more good in my book.