/uploads
is a directory in your account. You can sync file uploads across users by transferring files using the drop
command. If you really need to do this a lot, you could each make your /uploads
folder world-writeable and allow your teammates to copy files over.
But at this point, I imagine most of those files are test files, so it might be easier just to delete them and the database entities.
I'm happy to consult with the team on these questions.
Probably because the connection object is the singleton thing (object) that unites all the database transactions going to/from a particular app.
MySQL also uses the connection object for transactions and commit()
.
Sure. The first three are variations on a theme:
Isolation levels is from Relational Databases. There are certain anomalies that can happen, and which you might choose to allow in order to gain speed (concurrency). I have more information about this in the relational version of this course
Let's take just one example: "repeatable read". If you read the same data twice, do you always get the same value, or do you get an updated value? At the highest levels of transaction, once a value is read, you'll always get the same value. In practice in our applications, we rarely read a value more than once, so this doesn't affect us. But we could think about situations where it might. Maybe over a session?