« first day (3666 days earlier)      last day (1187 days later) » 

9:32 AM
Dia dhaoibh go léir a chairde - Morning all. Just had a nice 1hr 20 walk and am sitting down to some recorded political analysis programmes... wish I could invent a utility to skip over Covid-19 (and other Irish-related, as opposed to intl.) stories - I mean it's important and all that, but I'm becoming a wee bit overloaded... If I see another whining opposition party hack or another excuse-making Govt. rep., I'm liable to thrown the telly into the canal...
 
9:50 AM
@Vérace if you want to pass the time with something different: iq.com/play/slxk4ry5to
 
@ypercubeᵀᴹ I'm more of a documentary, history, politics, economics, nature man than dramas... do you have anything in that vein? Unless, of course, if it's totally mindless (and mind-numbing) violence when I can be persuaded to switch off the brain for a while... :-)
 
it's extreme violence - black and white fighting on a board ;)
If you want real violence, (kungfu style and sword fighting) this might be better: iq.com/play/g5k80a7vs8
 
10:54 AM
@ypercubeᵀᴹ Not too much into the kung-foo stuff - I prefer firearm violence in thrillers. As a child, I did enjoy the Water Margin where the noble and honest Lin Chung was being pursued by the evil Kao Chiu! Never came across anything better in that genre, although Crouching Tiger, Hidden Dragon wasn't bad. Some others have been OK, but it's not stuff that I'd avidly pursue.
 
11:42 AM
the tiger - dragon was good, I remember it
 
 
2 hours later…
1:41 PM
Fellow Heapers - I answered the question below this afternoon - but it's a very wide (not to mention tricky) topic (transaction isolation and serializable...). As I mention in my answer, I have purchased Martin Kleppmann's book, but I haven't got through all of it yet.
1
Q: Which isolation levels can cause a serialization failure?

learn9909The quote below from Wikipedia (here) says that READ COMMITTED doesn't cause serialization failure! Can you please explain the reason? Which isolation levels cause serialization failure? Under multiversion concurrency control, at the SERIALIZABLE isolation level, both SELECT queries see a snapsh...

So I just want to make sure that I haven't given any bum steers - I'd be grateful if anyone could take a look and (perhaps) point out any errors, clarify any of the points or suggest anything further to add that may be missing?
In particular, am I correct in saying: "On most modern RDBMS's, if you don't explicitly specify a BEGIN TRANSACTION or an isolation level, the default is that a) a transaction is started for you automatically beneath the hood and b) that transaction is read-committed - which normally doesn't matter much since it's one query.".
In particular the "doesn't matter much" bit - are there any cases where a single query transaction under an R-C isolation level would not work under an S isolation level?
 
 
6 hours later…
7:45 PM
@MaxVernon - ah, boo!!! You edited the best bit of my comment! :-(
 
@Vérace sorry - I needed to make it less offensive. I know it wasn't meant literally but non-english speakers probably wouldn't.
 
8:43 PM
@MaxVernon I know it wasn't meant literally - no, no, I absolutely did. In fact, I think that shooting would be too good - make it something slow and painful! :-) No, really, I can excuse grunt devs using it - I know I made mistakes with it in the beginning of my SQL journey - I just couldn't understand how those who wrote a db product could allow it to provide incorrect answers...
... nah, it's really just the MySQL devs that deserve the wall!... I mean, fair enough, if you're messing with transaction isolation... but what MySQL did was truly appalling! :-) I'm starting to have more respect for closed source db's that do the right thing rather than F/LOSS ones which don't!
 

« first day (3666 days earlier)      last day (1187 days later) »