Single transactions

Multiple transactions

Begin transaction failed

Prev

Transaction not started.

Transaction already started.

The first would be using transactions.

Unable to commit transaction

Unable to rollback transaction

Will any transactions be adequately logged?

Unable to begin transaction

There's kind of 2 main ways to approach this problem.

Could not commit transaction

Could not connect

Could not begin transaction

Could not rollback transaction

Atomicity refers to the notion that all parts of a transaction succeed or fail together.

You can do some selects, you can do updates, you can do inserts.

Could not start transaction

Finally, we have durability.

Because then that score changing here should be 0, but it could be 1 if these aren't handled properly.

And I'll talk about what a proof of work protocols are in a separate video in more detail

So we'll never run a query that gets a links updated score but can't also get the user's updated karma.

And then you commit that transaction.

J. ROSS BROWNE'S ETCHlNGS OF A WHALlNG CRUlZE. 1846.

And the nodes are (?) appending new transaction blocks to that chain they're gonna take anything (?) that hasn't yet been processed amp amp start incorporate it into the transaction chain that was broadcasted out by the node who came up with the proof of work correctly now this transaction block chain, really, what we're gonna be doing in the context of Bitcoin is the nodes are only going to consider the transaction block chain that reflects the greatest amount of work ??? contents

Now, because each transaction block contains information about previous transaction, really what you end up having is not just a single block, you ultimately have what you can think of as a chain of transactions.

Atomicity, Consistency, Isolation, Durability.

High

Shit.

You know what he'll do?

And so they have to find a way and they use algorithms to do this to break up that big thing into a million little transactions.

That's too expensive

The pitch is high. Ball one.

He is tall, but his brother is much taller.

Ken is tall, but I'm not.

If you're crappy, say you're crappy!

It's high risk, extremely high risk.

And my answer was you can either use transactions in the datastore, which I don't fully understand, because I'm new to a datastore, or you can use memcache, which is one of the 101 uses of memcache, it has this global lock.

Good? Yeah, No, I'm great, you know, it's totally great.

Be quiet and just take a look at this!

The waves are high.

With who?

So, I'll label this for you in a second.

Higher.